CVE-2026-90052 Linux CVE debrief

Who should care

Linux kernel developers and maintainers, as well as users of systems that utilize the dm-integrity module, should assess their exposure and apply patches as necessary. This includes reviewing the system's configuration, identifying potential vulnerabilities, and implementing necessary mitigations. Additionally, users should monitor their systems for potential exploitation attempts and verify the integrity of their systems.

Why it matters

This vulnerability in the Linux kernel's dm-integrity module requires attention from developers and users to prevent potential buffer overflows and system instability. Patching and monitoring are essential to mitigate this issue.

• Potential buffer overflow leading to system crashes or instability
• Possible exploitation attempts require monitoring and patching
• Verification of system integrity and patch application is necessary

Technical summary

The Linux kernel's dm-integrity module is vulnerable to a buffer overflow when computing checksums for discarded blocks. This occurs when the tag size is smaller than the digest size, causing the checksum of the last block to be written past the end of the buffer. The vulnerability was introduced by a commit that replaced forgeable discard filler with a keyed sector marker. To fix this, the buffer size is adjusted by subtracting extra_space when computing max_blocks, similar to the approach used for writes. This adjustment ensures that the checksum computation stays within the buffer bounds, preventing the buffer overflow.

Defensive priority

High

Recommended defensive actions

• Review and apply the provided patches to the Linux kernel
• Update the dm-integrity module to prevent buffer overflows
• Monitor systems for potential exploitation attempts
• Verify the integrity of the system and apply patches as necessary
• Conduct a thorough review of the system's exposure and assess the potential impact
• Consider implementing compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details about the vulnerability, including its description and CVSS score of 7.8. However, the exact scope of affected systems and versions is not specified. The vulnerability was resolved by subtracting extra_space from the buffer size when computing max_blocks, similar to how it is done for writes. This fix prevents the buffer overflow by ensuring that the checksum computation does not exceed the buffer bounds.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.