LiveActive security incident?Get immediate response
CVE Record

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 BLK_INTEGRITY_CSUM_NONE check to cover any case when the metadata is larger than just the PI tuple.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A Linux kernel block-layer bug could leave part of a storage integrity metadata buffer uninitialized. Under specific write-integrity configurations, leftover kernel memory could later be read by userspace or by someone with physical access to the storage device.

Executive priority

Treat as a targeted information-disclosure risk for Linux storage environments. It is not supported as actively exploited in the supplied sources, but patch during normal kernel maintenance and prioritize systems handling sensitive data on integrity-enabled storage.

Technical view

The issue is in auto-generated integrity buffers for block writes. When protection information is generated and metadata is larger than the PI tuple, the opaque metadata remainder was not zeroed. The kernel fix generalizes zeroing so non-PI metadata is initialized before submission.

Likely exposure

Exposure appears limited to Linux systems using block devices with integrity metadata where metadata exceeds the PI tuple size. The bundle lists Linux kernel affected version data, but the flattened version details are ambiguous; validate against vendor kernel advisories and the cited stable commits.

Exploitation context

The provided sources do not show active exploitation, public exploit code, KEV listing, CVSS, or CWE mapping. The practical impact is information disclosure, not direct code execution or privilege escalation based on the supplied evidence.

Researcher notes

Focus analysis on blk-integrity auto-generated write buffers and metadata layouts where PI tuple size is nonzero but smaller than total metadata size. Evidence supports uninitialized memory disclosure; exploitability depends on block device integrity configuration and readback access.

Mitigation direction

  • Update to a vendor-supported kernel containing the cited stable fixes.
  • Review Linux distribution advisories for exact affected and fixed package versions.
  • Prioritize systems using block integrity metadata or direct storage access paths.
  • Restrict physical access to storage media and decommissioned disks.
  • Monitor the CVE record for severity or affected-version updates.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and storage nodes.
  • Check whether vendor kernels include the referenced stable commits.
  • Identify systems using block integrity metadata with larger-than-PI metadata.
  • Confirm distribution security scanners recognize CVE-2026-23007.
  • Track CVE updates because severity data is currently missing.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23007 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc546d6f438338017480d105ab597292da67f6f6a, c546d6f438338017480d105ab597292da67f6f6aunaffected
LinuxLinux6.11, 0, 6.18.7, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.