Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 765bf0a5880777c04ae98fc2a9f3b995737b3a64, ca22c566b89164f6e670af56ecc45f47ef3df819, d6072557b90e0c557df319a56f4a9dc482706d2c.

Low priority for now. Upgrade to Linux Linux 765bf0a5880777c04ae98fc2a9f3b995737b3a64, ca22c566b89164f6e670af56ecc45f47ef3df819, d6072557b90e0c557df319a56f4a9dc482706d2c or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—Proof of concept Fix available
Published
Jan 25, 2026
Updated
Oct 21, 2026
EPSS
0.2% · 10th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-23007

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel6.11.1 and later · before 6.18.7
  • linux linux kernel6.11
  • linux linux kernel6.19

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.11affected
    • c546d6f438338017480d105ab597292da67f6f6a and later · before 765bf0a5880777c04ae98fc2a9f3b995737b3a64affected · git
    • c546d6f438338017480d105ab597292da67f6f6a and later · before d6072557b90e0c557df319a56f4a9dc482706d2caffected · git
    • c546d6f438338017480d105ab597292da67f6f6a and later · before ca22c566b89164f6e670af56ecc45f47ef3df819affected · git
    • before 6.11not affected · semver
    • 6.12.114 and later · up to and including 6.12.*not affected · semver
    • 6.18.7 and later · up to and including 6.18.*not affected · semver
    • 6.19 and laternot affected · original_commit_for_fix

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-docbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-headersbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-zfcpdump-develbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10kernel-zfcpdump-devel-matchedbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10perfbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:10python3-perfbefore 6.12.0-211.59.1.el10_26.12.0-211.59.1.el10_2
AlmaLinux:9kernelbefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64kbefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-corebefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-debugbefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-687.51.1.el9_85.14.0-687.51.1.el9_8

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-23004Jan 25, 2026 · dst: fix races in rt6_uncached_list_del() and rt_del_uncached_list()
    18Monitor
  • ← EarlierCVE-2026-23005Jan 25, 2026 · x86/fpu: Clear XSTATE_BV[i] in guest XSAVE state whenever XFD[i]=1
    22Monitor
  • Later →CVE-2026-23010Jan 25, 2026 · ipv6: Fix use-after-free in inet6_addr_del().
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux765bf0a5880777c04ae98fc2a9f3b995737b3a64Vendor (CNA)
Linux Linuxca22c566b89164f6e670af56ecc45f47ef3df819Vendor (CNA)
Linux Linuxd6072557b90e0c557df319a56f4a9dc482706d2cVendor (CNA)
almalinux:kernel5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-modules5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-modules-core5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-modules-extra5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-abi-stablelists5.14.0-687.51.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.18.8-1 · Debian:14Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-687.51.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:kernel0:5.14.0-687.51.1.el9_8 · Rocky Linux:9Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:12026-08-05

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+191 d
  3. TodayNov 1, 2026+279 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-50302432 days apartHID: core: zero-initialize the report bufferKEV
    52Plan
  • CVE-2026-52989150 days apartnvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers
    39Monitor
  • CVE-2026-53225151 days apartsctp: fix uninit-value in __sctp_rcv_asconf_lookup()
    36Monitor
  • CVE-2024-47685461 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()
    36Monitor
  • CVE-2026-53170151 days apartaccel/ethosu: reject DMA commands with uninitialized length
    35Monitor
  • CVE-2026-43139101 days apartxfrm6: fix uninitialized saddr in xfrm6_get_saddr()
    34Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-908 · Use of Uninitialized Resource

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records