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-90250bpf, cgroup: Fix storage null-ptr-deref after replacing prog

Description

In the Linux kernel, the following vulnerability has been resolved: bpf, cgroup: Fix storage null-ptr-deref after replacing prog Syzkaller reported a storage null-ptr-deref issue after replacing prog. This occurs in the following scenario: 1. prog A, an empty prog, is attached to a cgrp. 2. prog B uses BPF_MAP_TYPE_PERCPU_CGROUP_STORAGE and calls the bpf_get_local_storage helper. 3. link_update is called to replace prog A with prog B. The reason is that __cgroup_bpf_replace fails to alloc and assign the required cgrp storage for the incoming replacement prog. Consequently, the new prog inherits an uninit storage, leading to null-ptr-deref panic when kick the new prog. Fix this by rejecting a link update if new_prog's cgroup storage is incompatible with link->prog.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 43 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.21% · top 89% of all CVEs (18 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 0c991ebc8c69d29b7fc44db17075c5aa5253e2ab – < 85785e7e2ebddcaa5c3b31bd3bcd83ae648985d4
    • affected 0c991ebc8c69d29b7fc44db17075c5aa5253e2ab – < 16c8321ee40c420f8e02e09515a5126682ddf4ea
    • affected 0c991ebc8c69d29b7fc44db17075c5aa5253e2ab – < a033c950f6731be88a7da98604ed78f302f15b80
    • affected 0c991ebc8c69d29b7fc44db17075c5aa5253e2ab – < 1ab3da12061d7ccb099f7e925fa2d865967a316a
    • affected 0c991ebc8c69d29b7fc44db17075c5aa5253e2ab – < 12feca126831556dc7fabe5a3ba28fbd328768b6
    • affected 0c991ebc8c69d29b7fc44db17075c5aa5253e2ab – < 3f562c537e9ecf4bc5e206cfffc2cc047f1b7e94
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .