can: bcm: add locking for bcm_op runtime updates
- 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.4.294, 5.10.238, 5.15.185, 6.1.141, 6.6.93, 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: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: can: bcm: add locking for bcm_op runtime updates The CAN broadcast manager (CAN BCM) can send a sequence of CAN frames via hrtimer. The content and also the length of the sequence can be changed resp reduced at runtime where the 'currframe' counter is then set to zero. Although this appeared to be a safe operation the updates of 'currframe' can be triggered from user space and hrtimer context in bcm_can_tx(). Anderson Nascimento created a proof of concept that triggered a KASAN slab-out-of-bounds read access which can be prevented with a spin_lock_bh. At the rework of bcm_can_tx() the 'count' variable has been moved into the protected section as this variable can be modified from both contexts too.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in 8f1c022541bf5a923c8d6fa483112c15250f30a4; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in 7595de7bc56e0e52b74e56c90f7e247bf626d628; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in fbd8fdc2b218e979cfe422b139b8f74c12419d1f; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in 2a437b86ac5a9893c902f30ef66815bf13587bf6; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in 76c84c3728178b2d38d5604e399dfe8b0752645e; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in cc55dd28c20a6611e30596019b3b2f636819a4c0; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in c4e8a172501e677ebd8ea9d9161d97dc4df56fbd; From ffd980f976e7fd666c2e61bf8ab35107efd11828 · fixed in c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7
- Linux Linux
2.6.25
- KernelLinux
From 2.6.25 · fixed in 5.4.294; From 5.5.0 · fixed in 5.10.238; From 5.11.0 · fixed in 5.15.185; From 5.16.0 · fixed in 6.1.141; From 6.2.0 · fixed in 6.6.93; From 6.7.0 · fixed in 6.12.31; From 6.13.0 · fixed in 6.14.9
References 8
git.kernel.org
- stable/c/8f1c022541bf5a923c8d6fa483112c15250f30a4
- stable/c/7595de7bc56e0e52b74e56c90f7e247bf626d628
- stable/c/fbd8fdc2b218e979cfe422b139b8f74c12419d1f
- stable/c/2a437b86ac5a9893c902f30ef66815bf13587bf6
- stable/c/76c84c3728178b2d38d5604e399dfe8b0752645e
- stable/c/cc55dd28c20a6611e30596019b3b2f636819a4c0
- stable/c/c4e8a172501e677ebd8ea9d9161d97dc4df56fbd
- stable/c/c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7