CVE-2026-90313bpf, cgroup: Fix invalid storage access after __cgroup_bpf_attach failed
- —Not scoredno CVSS score yet
- 0.21%Exploitation in 30 daysEPSS · top 89% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: bpf, cgroup: Fix invalid storage access after __cgroup_bpf_attach failed A potential invalid storage access issue can occur after replacing a cgroup bpf prog. This occurs in the following scenario: 1. prog1 with storage is attached to a cgroup in multi-attach mode. 2. prog1 is replaced with prog2 using BPF_F_REPLACE in multi-attach mode, but fails midway (e.g. in bpf_trampoline_link_cgroup_shim or update_effective_progs). 3. A new prog3 is attached to the cgroup in multi-attach mode. The reason is that __cgroup_bpf_attach overwrites pl->storage with the new storage prior to attachment completion. When attachment fails midway, the cleanup path calls bpf_cgroup_storages_free(new_storage) to free the newly allocated storage, but fails to restore pl->storage back to old_storage. Consequently, the still-active prog1 holds invalid or dangling storage pointers, leading to an invalid memory access when prog1 executes and calls bpf_get_local_storage. Additionally, original pl->flags and cgrp->bpf.flags[atype] are left unrestored. Fix this by saving old_pl_flags, old_storage, and old_flags prior to the update, and properly restoring all of them in the cleanup path on error.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 43 days later
· 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 (17 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 – < 217b257d2c39e8dc32d691e8952f3cd921a80233
- affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 – < e26db0d636e4c24a6b16683ea95cf5077c64d74b
- affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 – < aaca16e042527f7efe48b50799bc662f1a191ce1
- affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 – < 86ead176301109b78e1d14c0e9d0d9ff9723c769
- affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 – < 2c2218560b6e28a63ff7834ba26d09ff8efdee39
- affected 7d9c3427894fe70d1347b4820476bf37736d2ff0 – < 6655c409707ec8ce9ce0850ffe4fe02331fd4d9c
- affected 5.9
- unaffected < 5.9
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.157 – ≤ 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
- https://git.kernel.org/stable/c/217b257d2c39e8dc32d691e8952f3cd921a80233 (opens in a new tab)
- https://git.kernel.org/stable/c/e26db0d636e4c24a6b16683ea95cf5077c64d74b (opens in a new tab)
- https://git.kernel.org/stable/c/aaca16e042527f7efe48b50799bc662f1a191ce1 (opens in a new tab)
- https://git.kernel.org/stable/c/86ead176301109b78e1d14c0e9d0d9ff9723c769 (opens in a new tab)
- https://git.kernel.org/stable/c/2c2218560b6e28a63ff7834ba26d09ff8efdee39 (opens in a new tab)
- https://git.kernel.org/stable/c/6655c409707ec8ce9ce0850ffe4fe02331fd4d9c (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-81974 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-90313)Record last updated .