can: bcm: add missing device refcount for CAN filter removal
- 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.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, 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
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: can: bcm: add missing device refcount for CAN filter removal sashiko-bot remarked a problem with a concurrent device unregistration in isotp.c which also is present in the bcm.c code. A former fix for raw.c commit c275a176e4b6 ("can: raw: add missing refcount for memory leak fix") introduced a netdevice_tracker which solves the issue for bcm.c too. bcm_release(), bcm_delete_rx_op() and bcm_notifier() relied on dev_get_by_index(ifindex) to re-find the device for an rx_op before unregistering its filter. If a concurrent NETDEV_UNREGISTER has already unlisted the device from the ifindex table, that lookup fails and can_rx_unregister() is silently skipped, leaving a stale CAN filter pointing at the soon-to-be-freed bcm_op/socket. Hold a netdev_hold()/netdev_put() tracked reference on op->rx_reg_dev from the moment the rx filter is registered in bcm_rx_setup() until it is unregistered in bcm_rx_unreg(), and use that reference directly in bcm_release() and bcm_delete_rx_op() instead of re-looking the device up by ifindex.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in bd5232663524e94cc5aad861dca11e3db8e2ab6f; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in ee8b36d0faca08f35b889b6e9aa850695e5b8ba9; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in dcaee869913c7210cd47ed0a8f27349d7bdcdb7b; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in 84aa4807816e405c1bf87114fc63e06d244281ef; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in 633bda66fbf309f5de5e1ad6defe8e6b1d77a20f; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in b024c21c9066f6957b7d4a8f2037e4b000c5e041; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in 04d23061bbf18d5d81022eb21e9d32e99d24468d; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in d59948293ea34b6337ce2b5febab8510de70048c
- Linux Linux
2.6.25
- KernelLinux
From 2.6.25 · fixed in 5.10.265; From 5.11.0 · fixed in 5.15.216; From 5.16.0 · fixed in 6.1.183; From 6.2.0 · fixed in 6.6.148; From 6.7.0 · fixed in 6.12.101; From 6.13.0 · fixed in 6.18.42; From 6.19.0 · fixed in 7.1.5
References 8
git.kernel.org
- stable/c/bd5232663524e94cc5aad861dca11e3db8e2ab6f
- stable/c/ee8b36d0faca08f35b889b6e9aa850695e5b8ba9
- stable/c/dcaee869913c7210cd47ed0a8f27349d7bdcdb7b
- stable/c/84aa4807816e405c1bf87114fc63e06d244281ef
- stable/c/633bda66fbf309f5de5e1ad6defe8e6b1d77a20f
- stable/c/b024c21c9066f6957b7d4a8f2037e4b000c5e041
- stable/c/04d23061bbf18d5d81022eb21e9d32e99d24468d
- stable/c/d59948293ea34b6337ce2b5febab8510de70048c