Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98034bpf: Mark NULL kptr stores precise

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Mark NULL kptr stores precise check_map_kptr_access() permits a scalar store into an untrusted kptr field only when the register is known to contain zero. Unlike other verifier checks whose outcome depends on a scalar value, it does not mark that register precise. A state checkpoint reached with an imprecise zero can therefore prune a second path that reaches the store with an arbitrary nonzero scalar. The program can write attacker-controlled bits into the kptr field and load them back as a PTR_TO_BTF_ID. Call mark_chain_precision() before accepting a known-zero register. This forces state equivalence to compare its scalar range and makes the verifier visit and reject a path carrying a nonzero value.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 26 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 61df10c7799e27807ad5e459eec9d77cddf8bf45 – < 86a3171c90bfc35a54e9d83cd197ca0d72d2f4e4
    • affected 61df10c7799e27807ad5e459eec9d77cddf8bf45 – < b8b98d3d37908402ff63515fa4d7574235436ea8
    • affected 61df10c7799e27807ad5e459eec9d77cddf8bf45 – < bb667eb575c906f24c707986541a99424c5b07ea
    • affected 61df10c7799e27807ad5e459eec9d77cddf8bf45 – < 86168208737bdd267d92d855d453d1d2f840df19
    • affected 61df10c7799e27807ad5e459eec9d77cddf8bf45 – < ecdc5043794c9184aa8e6c814603899479c46b35
    • affected b5a8069835e5236824a84281592d29f859b33153
    • affected 5.18.18 – < 5.19
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98034 badge
[![CVE-2026-98034](https://cveledger.app/badge/CVE-2026-98034.svg)](https://cveledger.app/cve/CVE-2026-98034)

Record last updated .