Strix
64.3K

CVE-2026-90393

Unknown

Last modified

CVE-2026-90393 is a vulnerability of currently unknown severity. 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..

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 7f045a49fee04b5662cbdeaf0838f9322ae8c63a, < d462b5481d77ce7df8a5ff89a699386f00c9214d; >= 7f045a49fee04b5662cbdeaf0838f9322ae8c63a, < bdddf3e1493ee973619c154a57071ce67f78598b; >= 7f045a49fee04b5662cbdeaf0838f9322ae8c63a, < 79a66fd997d4eecf17302d613194879eb32e0986; >= 7f045a49fee04b5662cbdeaf0838f9322ae8c63a, < f4ce6803df4095777191d800bebc50219b615ca0; >= 7f045a49fee04b5662cbdeaf0838f9322ae8c63a, < 277168cb9d153ce8e9c3f9275670e32ae61b41d6; >= 7f045a49fee04b5662cbdeaf0838f9322ae8c63a, < bda86e9f31b9a296b6e64a51c91dc776fc9f613e; >= 7f045a49fee04b5662cbdeaf0838f9322ae8c63a, < 923f559e95b89b33c7e1793b3d8f7f4ec9b2e4b7; >= 7f045a49fee04b5662cbdeaf0838f9322ae8c63a, < 5c5997836381010fc5907b36bc17d3b19407e933
LinuxLinux5.8

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-90393?
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.
How severe is CVE-2026-90393?
Severity scoring for CVE-2026-90393 is pending analysis.
How do I fix CVE-2026-90393?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-90393?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST