Answer in brief
CVE-2026-23007 records a Unknown severity vulnerability in block: zero non-PI portion of auto integrity buffer. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c546d6f438338017480d105ab597292da67f6f6a <765bf0a5880777c04ae98fc2a9f3b995737b3a64 || >=c546d6f438338017480d105ab597292da67f6f6a <d6072557b90e0c557df319a56f4a9dc482706d2c || >=c546d6f438338017480d105ab597292da67f6f6a <ca22c566b89164f6e670af56ecc45f47ef3df819 | 765bf0a5880777c04ae98fc2a9f3b995737b3a64, d6072557b90e0c557df319a56f4a9dc482706d2c, ca22c566b89164f6e670af56ecc45f47ef3df819 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Jan 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 21, 2026
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 BLK_INTEGRITY_CSUM_NONE check to cover any case when the metadata is larger than just the PI tuple.
Quoted source text, attributed separately from HOL analysis.