Invalid memory access via BPF link-update race
Published Sep 17, 2026 · Updated Sep 17, 2026
Use-after-free in Linux BPF allows local users to trigger invalid kernel memory access via concurrent network-namespace link updates. The bpf_netns_link_update_prog function checks link->prog before taking netns_bpf_mutex, allowing another thread to replace and free the program before its type is read. Reaching the race requires access to update the same BPF link from two threads; the upstream disclosure does not establish a reliable privilege-escalation outcome.
Summary
What happened
Use-after-free in Linux BPF allows local users to trigger invalid kernel memory access via concurrent network-namespace link updates. The bpf_netns_link_update_prog function checks link->prog before taking netns_bpf_mutex, allowing another thread to replace and free the program before its type is read. Reaching the race requires access to update the same BPF link from two threads; the upstream disclosure does not establish a reliable privilege-escalation outcome.
The record
- CVE
- CVE-2026-90393
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.8
- Affected versionversion=7f045a49fee04b5662cbdeaf0838f9322ae8c63a <277168cb9d153ce8e9c3f9275670e32ae61b41d6
- Affected versionversion=7f045a49fee04b5662cbdeaf0838f9322ae8c63a <5c5997836381010fc5907b36bc17d3b19407e933
- Affected versionversion=7f045a49fee04b5662cbdeaf0838f9322ae8c63a <79a66fd997d4eecf17302d613194879eb32e0986
- Affected versionversion=7f045a49fee04b5662cbdeaf0838f9322ae8c63a <923f559e95b89b33c7e1793b3d8f7f4ec9b2e4b7
- Affected versionversion=7f045a49fee04b5662cbdeaf0838f9322ae8c63a <bda86e9f31b9a296b6e64a51c91dc776fc9f613e
- Affected versionversion=7f045a49fee04b5662cbdeaf0838f9322ae8c63a <bdddf3e1493ee973619c154a57071ce67f78598b
- Affected versionversion=7f045a49fee04b5662cbdeaf0838f9322ae8c63a <d462b5481d77ce7df8a5ff89a699386f00c9214d
- Affected versionversion=7f045a49fee04b5662cbdeaf0838f9322ae8c63a <f4ce6803df4095777191d800bebc50219b615ca0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started