bpf: Fix potential UAF in bpf_netns_link_update_prog
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.270, 5.15.221, 6.1.188, 6.6.157, 6.12.110, and 2 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 7f045a49fee04b5662cbdeaf0838f9322ae8c63a · fixed in d462b5481d77ce7df8a5ff89a699386f00c9214d; From 7f045a49fee04b5662cbdeaf0838f9322ae8c63a · fixed in bdddf3e1493ee973619c154a57071ce67f78598b; From 7f045a49fee04b5662cbdeaf0838f9322ae8c63a · fixed in 79a66fd997d4eecf17302d613194879eb32e0986; From 7f045a49fee04b5662cbdeaf0838f9322ae8c63a · fixed in f4ce6803df4095777191d800bebc50219b615ca0; From 7f045a49fee04b5662cbdeaf0838f9322ae8c63a · fixed in 277168cb9d153ce8e9c3f9275670e32ae61b41d6; From 7f045a49fee04b5662cbdeaf0838f9322ae8c63a · fixed in bda86e9f31b9a296b6e64a51c91dc776fc9f613e; From 7f045a49fee04b5662cbdeaf0838f9322ae8c63a · fixed in 923f559e95b89b33c7e1793b3d8f7f4ec9b2e4b7; From 7f045a49fee04b5662cbdeaf0838f9322ae8c63a · fixed in 5c5997836381010fc5907b36bc17d3b19407e933
- Linux Linux
5.8
- KernelLinux
From 5.8.0 · fixed in 5.10.270; From 5.11.0 · fixed in 5.15.221; From 5.16.0 · fixed in 6.1.188; From 6.2.0 · fixed in 6.6.157; From 6.7.0 · fixed in 6.12.110; From 6.13.0 · fixed in 6.18.52; From 6.19.0 · fixed in 7.2.6
References 8
git.kernel.org
- stable/c/d462b5481d77ce7df8a5ff89a699386f00c9214d
- stable/c/bdddf3e1493ee973619c154a57071ce67f78598b
- stable/c/79a66fd997d4eecf17302d613194879eb32e0986
- stable/c/f4ce6803df4095777191d800bebc50219b615ca0
- stable/c/277168cb9d153ce8e9c3f9275670e32ae61b41d6
- stable/c/bda86e9f31b9a296b6e64a51c91dc776fc9f613e
- stable/c/923f559e95b89b33c7e1793b3d8f7f4ec9b2e4b7
- stable/c/5c5997836381010fc5907b36bc17d3b19407e933