6 matches found
SUSE CVE-2025-40028
In the Linux kernel, the following vulnerability has been resolved: binder: fix double-free in dbitmap A process might fail to allocate a new bitmap when trying to expand its proc-dmap. In that case, dbitmapgrow fails and frees the old bitmap via dbitmapfree. However, the driver calls dbitmapfree...
CVE-2025-40028
In the Linux kernel, the following vulnerability has been resolved: binder: fix double-free in dbitmap A process might fail to allocate a new bitmap when trying to expand its proc-dmap. In that case, dbitmapgrow fails and frees the old bitmap via dbitmapfree. However, the driver calls dbitmapfree...
EUVD-2025-36439
In the Linux kernel, the following vulnerability has been resolved: binder: fix double-free in dbitmap A process might fail to allocate a new bitmap when trying to expand its proc-dmap. In that case, dbitmapgrow fails and frees the old bitmap via dbitmapfree. However, the driver calls dbitmapfree...
UBUNTU-CVE-2025-40028
In the Linux kernel, the following vulnerability has been resolved: binder: fix double-free in dbitmap A process might fail to allocate a new bitmap when trying to expand its proc-dmap. In that case, dbitmapgrow fails and frees the old bitmap via dbitmapfree. However, the driver calls dbitmapfree...
CVE-2025-40028
CVE-2025-40028 : In the Linux kernel, a double-free can occur in the Binder driver’s dbitmap path when expanding proc->dmap; dbitmap_grow() frees the old bitmap via dbitmap_free(), and the driver later frees it again on process termination. The fixed mitigation is to set proc->map to NULL i...
Linux Distros Unpatched Vulnerability : CVE-2025-40028
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - binder: fix double-free in dbitmap A process might fail to allocate a new bitmap when trying to expand its proc-dmap. In that case, dbitmapgrow fails and frees...