CVE-2026-89573
Linux · Kernel
A buffer over-read vulnerability exists in the Linux kernel dm-cache implementation, allowing a local authenticated attacker to trigger memory corruption via crafted metadata.
Executive summary
A high-severity memory corruption vulnerability in the Linux kernel dm-cache module may allow a local attacker to achieve elevated privileges or system crashes.
Vulnerability
The dm-cache component fails to validate that the value size of an array block matches the expected size of the caller, leading to an out-of-bounds memory access. This flaw requires a local attacker with sufficient privileges to provide crafted metadata to trigger the incorrect memory stride.
Business impact
Successful exploitation of this vulnerability could allow a local attacker to compromise the integrity and availability of the host system. Given the CVSS score of 7.8, this flaw poses a significant risk to data confidentiality and system stability, particularly in multi-tenant environments or systems where local users have elevated access.
Remediation
Immediate Action: Update the Linux kernel to the versions specified in the OSV enrichment (e.g., 6.12.109, 6.18.50, or 7.2.4) or the latest stable release provided by your distribution vendor.
Proactive Monitoring: Monitor system logs for kernel oops or segmentation faults related to the dm-cache or device mapper modules.
Compensating Controls: Restrict access to administrative or disk-management functions to only trusted users, as the vulnerability requires the ability to manipulate device mapper metadata.
Exploitation status
Public Exploit Available: No (exploit_available: false)
Analyst recommendation
While local exploitation requirements reduce the immediate risk compared to remote vulnerabilities, the potential for kernel-level impact warrants prompt attention. Administrators should prioritize patching the kernel across all impacted environments to eliminate the risk of memory corruption and potential privilege escalation.
More Linux CVEs all →
History
CVE Brief tracked this CVE 2 days before it had a CVSS score.
- Disclosed CVE record published
- Collected by CVE Brief No CVSS score yet; tracked as early warning
- CVSS score assigned 7.8 (3.1)
- Analyst report written