CVE-2026-90393bpf: Fix potential UAF in bpf_netns_link_update_prog
- —Not scoredno CVSS score yet
- 0.23%Exploitation in 30 daysEPSS · top 86% 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: Fix potential UAF in bpf_netns_link_update_prog In bpf_netns_link_update_prog, the checks for old_prog and prog type are currently performed locklessly before acquiring netns_bpf_mutex. This creates a race condition that can lead to a UAF issue. If two threads concurrently execute BPF_LINK_UPDATE on the same netns link, the following execution path can trigger a UAF: CPU0 CPU1 bpf_netns_link_update_prog if (old_prog && old_prog != link->prog) return -EPERM; bpf_netns_link_update_prog if (old_prog && old_prog != link->prog) ... old_prog = xchg(&link->prog, new_prog); bpf_prog_put(old_prog); if (new_prog->type != link->prog->type) <-- trigger UAF Fix this by moving the old_prog and prog->type checks inside the netns_bpf_mutex critical section. Meanwhile, use guard() to simplify lock management and avoid all the goto jumping.
Timeline
ID reserved
By Linux
- 6 days later
· 6 days later
Published
- 32 days later
· 32 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.23% · top 86% 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 7f045a49fee04b5662cbdeaf0838f9322ae8c63a – < d462b5481d77ce7df8a5ff89a699386f00c9214d
- affected 7f045a49fee04b5662cbdeaf0838f9322ae8c63a – < bdddf3e1493ee973619c154a57071ce67f78598b
- affected 7f045a49fee04b5662cbdeaf0838f9322ae8c63a – < 79a66fd997d4eecf17302d613194879eb32e0986
- affected 7f045a49fee04b5662cbdeaf0838f9322ae8c63a – < f4ce6803df4095777191d800bebc50219b615ca0
- affected 7f045a49fee04b5662cbdeaf0838f9322ae8c63a – < 277168cb9d153ce8e9c3f9275670e32ae61b41d6
- affected 7f045a49fee04b5662cbdeaf0838f9322ae8c63a – < bda86e9f31b9a296b6e64a51c91dc776fc9f613e
- affected 7f045a49fee04b5662cbdeaf0838f9322ae8c63a – < 923f559e95b89b33c7e1793b3d8f7f4ec9b2e4b7
- affected 7f045a49fee04b5662cbdeaf0838f9322ae8c63a – < 5c5997836381010fc5907b36bc17d3b19407e933
- affected 5.8
- unaffected < 5.8
- unaffected 5.10.270 – ≤ 5.10.*
- unaffected 5.15.221 – ≤ 5.15.*
- unaffected 6.1.188 – ≤ 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
References8
- https://git.kernel.org/stable/c/d462b5481d77ce7df8a5ff89a699386f00c9214d (opens in a new tab)
- https://git.kernel.org/stable/c/bdddf3e1493ee973619c154a57071ce67f78598b (opens in a new tab)
- https://git.kernel.org/stable/c/79a66fd997d4eecf17302d613194879eb32e0986 (opens in a new tab)
- https://git.kernel.org/stable/c/f4ce6803df4095777191d800bebc50219b615ca0 (opens in a new tab)
- https://git.kernel.org/stable/c/277168cb9d153ce8e9c3f9275670e32ae61b41d6 (opens in a new tab)
- https://git.kernel.org/stable/c/bda86e9f31b9a296b6e64a51c91dc776fc9f613e (opens in a new tab)
- https://git.kernel.org/stable/c/923f559e95b89b33c7e1793b3d8f7f4ec9b2e4b7 (opens in a new tab)
- https://git.kernel.org/stable/c/5c5997836381010fc5907b36bc17d3b19407e933 (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-82054 (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-90393)Record last updated .