wireguard: netlink: check for dangling peer via is_dead instead of empty list
- 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.215, 5.15.154, 6.1.84, 6.6.24, 6.7.12, and 1 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
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: wireguard: netlink: check for dangling peer via is_dead instead of empty list If all peers are removed via wg_peer_remove_all(), rather than setting peer_list to empty, the peer is added to a temporary list with a head on the stack of wg_peer_remove_all(). If a netlink dump is resumed and the cursored peer is one that has been removed via wg_peer_remove_all(), it will iterate from that peer and then attempt to dump freed peers. Fix this by instead checking peer->is_dead, which was explictly created for this purpose. Also move up the device_update_lock lockdep assertion, since reading is_dead relies on that. It can be reproduced by a small script like: echo "Setting config..." ip link add dev wg0 type wireguard wg setconf wg0 /big-config ( while true; do echo "Showing config..." wg showconf wg0 > /dev/null done ) & sleep 4 wg setconf wg0 <(printf "[Peer]\nPublicKey=$(wg genkey)\n") Resulting in: BUG: KASAN: slab-use-after-free in __lock_acquire+0x182a/0x1b20 Read of size 8 at addr ffff88811956ec70 by task wg/59 CPU: 2 PID: 59 Comm: wg Not tainted 6.8.0-rc2-debug+ #5 Call Trace: <TASK> dump_stack_lvl+0x47/0x70 print_address_description.constprop.0+0x2c/0x380 print_report+0xab/0x250 kasan_report+0xba/0xf0 __lock_acquire+0x182a/0x1b20 lock_acquire+0x191/0x4b0 down_read+0x80/0x440 get_peer+0x140/0xcb0 wg_get_device_dump+0x471/0x1130
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From e7096c131e5161fa3b8e52a650d7719d2857adfd · fixed in f52be46e3e6ecefc2539119784324f0cbc09620a; From e7096c131e5161fa3b8e52a650d7719d2857adfd · fixed in 710a177f347282eea162aec8712beb1f42d5ad87; From e7096c131e5161fa3b8e52a650d7719d2857adfd · fixed in b7cea3a9af0853fdbb1b16633a458f991dde6aac; From e7096c131e5161fa3b8e52a650d7719d2857adfd · fixed in 13d107794304306164481d31ce33f8fdb25a9c04; From e7096c131e5161fa3b8e52a650d7719d2857adfd · fixed in 7bedfe4cfa38771840a355970e4437cd52d4046b; From e7096c131e5161fa3b8e52a650d7719d2857adfd · fixed in 302b2dfc013baca3dea7ceda383930d9297d231d; From e7096c131e5161fa3b8e52a650d7719d2857adfd · fixed in 55b6c738673871c9b0edae05d0c97995c1ff08c4
- Linux Linux
5.6
- KernelLinux
From 5.6.0 · fixed in 5.10.215; From 5.11.0 · fixed in 5.15.154; From 5.16.0 · fixed in 6.1.84; From 6.2.0 · fixed in 6.6.24; From 6.7.0 · fixed in 6.7.12; From 6.8.0 · fixed in 6.8.3
References 7
git.kernel.org
- stable/c/f52be46e3e6ecefc2539119784324f0cbc09620a
- stable/c/710a177f347282eea162aec8712beb1f42d5ad87
- stable/c/b7cea3a9af0853fdbb1b16633a458f991dde6aac
- stable/c/13d107794304306164481d31ce33f8fdb25a9c04
- stable/c/7bedfe4cfa38771840a355970e4437cd52d4046b
- stable/c/302b2dfc013baca3dea7ceda383930d9297d231d
- stable/c/55b6c738673871c9b0edae05d0c97995c1ff08c4