CVE-2026-90052
Linux · Kernel
A buffer overflow vulnerability exists in the Linux kernel dm-integrity component due to improper handling of checksum buffer sizes during keyed discard operations.
Executive summary
A memory corruption vulnerability in the Linux kernel dm-integrity module could allow a local attacker with low privileges to achieve privilege escalation or system instability.
Vulnerability
The vulnerability is a heap-based buffer overflow occurring when the tag size is smaller than the digest size in the dm-integrity driver. This allows data to be written past the bounds of the allocated buffer, which can be triggered by a local attacker with low privileges.
Business impact
The CVSS score of 7.8 indicates a high severity risk. Successful exploitation could lead to full system compromise, including unauthorized access to sensitive data or a complete denial of service through kernel panic. Given that this resides within the core kernel, the potential for widespread impact on enterprise Linux environments is significant.
Remediation
Immediate Action: Update your Linux kernel to version 7.3-rc2 or later, or apply the relevant stable branch patches provided in the upstream git references.
Proactive Monitoring: Monitor system logs for kernel oops messages or unexpected reboots that may indicate memory corruption events.
Compensating Controls: Restrict local access to the system to trusted users only, as the vulnerability requires local access to the kernel interface to trigger.
Exploitation status
Public Exploit Available: No (exploit_available: false)
Analyst recommendation
The risk posed by this buffer overflow is substantial due to its potential for privilege escalation within the kernel. System administrators should prioritize testing and deploying the identified kernel patches across all affected server and workstation environments to prevent local attackers from exploiting this memory safety flaw.
More Linux CVEs all →
History
CVE Brief tracked this CVE 4 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) from cvelistV5
- Analyst report written