CVE-2026-23007: block: zero non-PI portion of auto integrity buffer
In the Linux kernel, the following vulnerability has been resolved:
block: zero non-PI portion of auto integrity buffer
The auto-generated integrity buffer for writes needs to be fully initialized before being passed to the underlying block device, otherwise the uninitialized memory can be read back by userspace or anyone with physical access to the storage device. If protection information is generated, that portion of the integrity buffer is already initialized. The integrity data is also zeroed if PI generation is disabled via sysfs or the PI tuple size is 0. However, this misses the case where PI is generated and the PI tuple size is nonzero, but the metadata size is larger than the PI tuple. In this case, the remainder ("opaque") of the metadata is left uninitialized. Generalize the BLKINTEGRITYCSUMNONE check to cover any case when the metadata is larger than just the PI tuple.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2026-23007?
CVE-2026-23007 is classified as a medium severity vulnerability in the Linux kernel.
How do I fix CVE-2026-23007?
To fix CVE-2026-23007, ensure that your Linux kernel is updated to a version that contains the patch addressing this issue.
What are the consequences of CVE-2026-23007 exploitation?
Exploitation of CVE-2026-23007 may lead to data corruption and unintended behavior in the block device operations.
Which versions of the Linux kernel are affected by CVE-2026-23007?
CVE-2026-23007 affects specific versions of the Linux kernel that have not implemented the fix for the integrity buffer initialization.
Is CVE-2026-23007 related to data integrity issues?
Yes, CVE-2026-23007 is related to data integrity issues as it involves the non-PI portion of the auto integrity buffer not being properly initialized.