Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-23002: lib/buildid: use __kernel_read() for sleepable context

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.17% (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 568aeb3476c770a3863c755dd2a199c212434286, 777a8560fd29738350c5094d4166fe5499452409, b11dfb7708f212b96c7973a474014c071aa02e05.

Low priority for now. Upgrade to Linux Linux 568aeb3476c770a3863c755dd2a199c212434286, 777a8560fd29738350c5094d4166fe5499452409, b11dfb7708f212b96c7973a474014c071aa02e05 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: lib/buildid: use __kernel_read() for sleepable context Prevent a "BUG: unable to handle kernel NULL pointer dereference in filemap_read_folio". For the sleepable context, convert freader to use __kernel_read() instead of direct page cache access via read_cache_folio(). This simplifies the faultable code path by using the standard kernel file reading interface which handles all the complexity of reading file data. At the moment we are not changing the code for non-sleepable context which uses filemap_get_folio() and only succeeds if the target folios are already in memory and up-to-date. The reason is to keep the patch simple and easier to backport to stable kernels. Syzbot repro does not crash the kernel anymore and the selftests run successfully. In the follow up we will make __kernel_read() with IOCB_NOWAIT work for non-sleepable contexts. In addition, I would like to replace the secretmem check with a more generic approach and will add fstest for the buildid code.

MediumCVSS 5.5 · v3.1—Proof of concept Fix available
Published
Jan 25, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 7th 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.1%

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-23002

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.12.1 and later · before 6.12.67
  • linux linux kernel6.13 and later · before 6.18.7
  • linux linux kernel6.12
  • 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.12affected
    • ad41251c290dfe3c01472c94d2439a59de23fe97 and later · before b11dfb7708f212b96c7973a474014c071aa02e05affected · git
    • ad41251c290dfe3c01472c94d2439a59de23fe97 and later · before 568aeb3476c770a3863c755dd2a199c212434286affected · git
    • ad41251c290dfe3c01472c94d2439a59de23fe97 and later · before 777a8560fd29738350c5094d4166fe5499452409affected · git
    • before 6.12not affected · semver
    • 6.12.67 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:9kernelbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64kbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-corebefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-debugbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-develbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-corebefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-cross-headersbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-debugbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-debug-corebefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-debug-develbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-687.31.1.el9_85.14.0-687.31.1.el9_8
AlmaLinux:9kernel-debug-modules-corebefore 5.14.0-687.31.1.el9_85.14.0-687.31.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-22994Jan 23, 2026 · bpf: Fix reference count leak in bpf_prog_test_run_xdp()
    22Monitor
  • ← EarlierCVE-2026-23000Jan 25, 2026 · net/mlx5e: Fix crash on profile change rollback failure
    22Monitor
  • Later →CVE-2026-23006Jan 25, 2026 · ASoC: tlv320adcx140: fix null pointer
    22Monitor

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 Linux568aeb3476c770a3863c755dd2a199c212434286Vendor (CNA)
Linux Linux777a8560fd29738350c5094d4166fe5499452409Vendor (CNA)
Linux Linuxb11dfb7708f212b96c7973a474014c071aa02e05Vendor (CNA)
almalinux:kernel5.14.0-687.31.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.31.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.31.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.31.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.31.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.31.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.31.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.31.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.31.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.31.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.31.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.31.1.el9_8 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.69-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-687.31.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-687.31.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-687.31.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-687.31.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-687.31.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-687.31.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-687.31.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-687.31.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-687.31.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-687.31.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-687.31.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-687.31.1.el9_8 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
rocky linux:kernel0:5.14.0-687.31.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+192 d
  3. TodayNov 3, 2026+282 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.

No nightly-computed relations.

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-476 · NULL Pointer Dereference

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