CVE-2026-90393

bpf: Fix potential UAF in bpf_netns_link_update_prog

N/A
Published: September 17, 2026 at 04:09 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.87f045a49fee04b5662cbdeaf0838f9322ae8c63a
Vendor states this is fixed in 277168cb9d153ce8e9c3f9275670e32ae61b41d6 (fixed)
Vendor states this is fixed in 5c5997836381010fc5907b36bc17d3b19407e933 (fixed)
Vendor states this is fixed in 79a66fd997d4eecf17302d613194879eb32e0986 (fixed)
Vendor states this is fixed in 923f559e95b89b33c7e1793b3d8f7f4ec9b2e4b7 (fixed)
Vendor states this is fixed in bda86e9f31b9a296b6e64a51c91dc776fc9f613e (fixed)
Vendor states this is fixed in bdddf3e1493ee973619c154a57071ce67f78598b (fixed)
Vendor states this is fixed in d462b5481d77ce7df8a5ff89a699386f00c9214d (fixed)
Vendor states this is fixed in f4ce6803df4095777191d800bebc50219b615ca0 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.8 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card