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

bpf: reject direct access to nullable PTR_TO_BUF pointers

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: reject direct access to nullable PTR_TO_BUF pointers check_mem_access() matches PTR_TO_BUF via base_type() which strips PTR_MAYBE_NULL, allowing direct dereference without a null check. Map iterator ctx->key and ctx->value are PTR_TO_BUF | PTR_MAYBE_NULL. On stop callbacks these are NULL, causing a kernel NULL dereference. Add a type_may_be_null() guard to the PTR_TO_BUF branch, matching the existing PTR_TO_BTF_ID pattern.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 6 months 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

CVSS scores of CVE-2026-43333, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (11 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected b453361384c2db1c703dacb806d5fd36aec4ceca – < 10bc4a4dcded509c5d5c67d497900c3922c604cd
    • affected 20b2aff4bc15bda809f994761d5719827d66c0b4 – < 21a10c06ffae24cb01fd174a7ab7736001d2ea56
    • affected 20b2aff4bc15bda809f994761d5719827d66c0b4 – < 8755066f7bd0f4ac46a29d1708c7b20894539252
    • affected 20b2aff4bc15bda809f994761d5719827d66c0b4 – < 70abd9d118da2f56beb4ec22e3a29becae373535
    • affected 20b2aff4bc15bda809f994761d5719827d66c0b4 – < 63276547debc4d8a73eefb2c5273b2a905c961b0
    • affected 20b2aff4bc15bda809f994761d5719827d66c0b4 – < 4f6c99dc0420f1a3d671c1b8ab8a7ac84d9cba09
    • affected 20b2aff4bc15bda809f994761d5719827d66c0b4 – < b0db1accbc7395657c2b79db59fa9fae0d6656f3
    • affected e982070f8970bb62e69ed7c9cafff886ed200349
    • affected 5.15.37 – < 5.15.203
    • affected 5.16.11 – < 5.17
  • Linux · Linux

    • affected 5.17
    • unaffected < 5.17
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.134 – ≤ 6.6.*
    • unaffected 6.12.81 – ≤ 6.12.*
    • unaffected 6.18.22 – ≤ 6.18.*
    • unaffected 6.19.12 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .