net: bcmgenet: stop Tx NAPI before disabling the queues
- 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 6.18.55, 7.2.9
- 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: net: bcmgenet: stop Tx NAPI before disabling the queues bcmgenet_netif_stop() and the Wake-on-LAN branch of bcmgenet_suspend() both disable the Tx queues first and stop Tx NAPI several steps later. A completion in flight calls netif_tx_wake_queue() in between, and nothing stops the queue again, so a transmit can reach the rings after they have been freed. Close is safe because dev_deactivate_many() stops the qdisc first. bcmgenet_suspend() does not, so stop Tx NAPI before the queues on both paths. KASAN on a Raspberry Pi CM4, driven from an MTU change because suspend freezes user space before the callback runs: BUG: KASAN: use-after-free in bcmgenet_xmit+0x17f8/0x2258 Write of size 8 at addr ffffff8055844a68 by task ksoftirqd/0/14 bcmgenet_xmit+0x17f8/0x2258 dev_hard_start_xmit+0x13c/0x588 sch_direct_xmit+0x108/0x340 __dev_queue_xmit+0x1190/0x3848
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 254f3239dd070e469f45c3ca8b6ac38e47d6c730 · fixed in 63bcc2fee6419963e45e7c2cd698fa862409601d; From 254f3239dd070e469f45c3ca8b6ac38e47d6c730 · fixed in f329d42423089904758f2685cda295de9bf99441; From 254f3239dd070e469f45c3ca8b6ac38e47d6c730 · fixed in 7e87508b5c4d81210d0a736ed01962e52f5c4c56
- Linux Linux
6.15
- KernelLinux
From 6.15.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9