VulnerabilityPublished 25 Jan 2026Updated 21 Oct 2026

CVE-2026-23007: Linux kernel · block: zero non-PI portion of auto integrity buffer

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in d6072557b90e0c557df319a56f4a9dc482706d2c : update Linux kernel when convenient.

Data as of 26 Oct 2026, 17:16 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS: 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in d6072557b90e0c557df319a56f4a9dc482706d2c, ca22c566b89164f6e670af56ecc45f47ef3df819, 765bf0a5880777c04ae98fc2a9f3b995737b3a64

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to d6072557b90e0c557df319a56f4a9dc482706d2c, ca22c566b89164f6e670af56ecc45f47ef3df819 or 765bf0a5880777c04ae98fc2a9f3b995737b3a64.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ c546d6f438338017480d105ab597292da67f6f6a, < d6072557b90e0c557df319a56f4a9dc482706d2c	Fixed in d6072557b90e0c557df319a56f4a9dc482706d2c
LinuxLinux	Affected ≥ c546d6f438338017480d105ab597292da67f6f6a, < ca22c566b89164f6e670af56ecc45f47ef3df819	Fixed in ca22c566b89164f6e670af56ecc45f47ef3df819
LinuxLinux	Affected ≥ c546d6f438338017480d105ab597292da67f6f6a, < 765bf0a5880777c04ae98fc2a9f3b995737b3a64	Fixed in 765bf0a5880777c04ae98fc2a9f3b995737b3a64
LinuxLinux	Affected =6.11	Fixed in–

Description

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.

References

Community reviews

Loading reviews…