can: bcm: extend bcm_tx_lock usage for data and timer 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.10.265, 5.15.216, 6.1.183, 6.6.148, 6.12.101, and 4 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: extend bcm_tx_lock usage for data and timer updates Stage new CAN frame content for an existing tx op into a kmalloc()'d buffer and validate it there, mirroring the approach already used in bcm_rx_setup(). Only copy the validated data into op->frames while holding op->bcm_tx_lock, so bcm_can_tx() and bcm_tx_timeout_handler() can no longer observe a partially updated or unvalidated frame. Add a missing error path for memcpy_from_msg() when copying CAN frame data from userspace. Also move the kt_ival1/kt_ival2/ival1/ival2 updates in bcm_tx_setup() under op->bcm_tx_lock, and read kt_ival1/kt_ival2/count under the same lock in bcm_tx_set_expiry() and bcm_tx_timeout_handler(), closing the torn 64-bit ktime_t read on 32-bit platforms.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 7595de7bc56e0e52b74e56c90f7e247bf626d628 · fixed in a538b072ee074c9b41b9d9c15a6861a963e30755; From fbd8fdc2b218e979cfe422b139b8f74c12419d1f · fixed in 63422347b4c782f429748b2a09cd3cf3b77e6abd; From 2a437b86ac5a9893c902f30ef66815bf13587bf6 · fixed in 37917e432e50b7de2b64230974380132a30f7270; From 76c84c3728178b2d38d5604e399dfe8b0752645e · fixed in 52f06e7603780de100233713ddaf971d422e10ef; From cc55dd28c20a6611e30596019b3b2f636819a4c0 · fixed in 972fd66bb08fdef1090abe43196ca8da07216d13; From c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 · fixed in bd46f55dec608daa44b45dcf3328517630ad8e40; From c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 · fixed in 337f966c00662d81ad82cf5a4bbb150b2e32c0d4; From c2aba69d0c36a496ab4f2e81e9c2b271f2693fd7 · fixed in 12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc; From 5.10.238 · fixed in 5.10.265; From 5.15.185 · fixed in 5.15.216; From 6.1.141 · fixed in 6.1.183; From 6.6.93 · fixed in 6.6.148; From 6.12.31 · fixed in 6.12.101; From 5.4.294 · fixed in 5.5; From 6.14.9 · fixed in 6.15
- Linux Linux
6.15
- KernelLinux
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.15.0 · fixed in 7.1.5
References 8
git.kernel.org
- stable/c/a538b072ee074c9b41b9d9c15a6861a963e30755
- stable/c/63422347b4c782f429748b2a09cd3cf3b77e6abd
- stable/c/37917e432e50b7de2b64230974380132a30f7270
- stable/c/52f06e7603780de100233713ddaf971d422e10ef
- stable/c/972fd66bb08fdef1090abe43196ca8da07216d13
- stable/c/bd46f55dec608daa44b45dcf3328517630ad8e40
- stable/c/337f966c00662d81ad82cf5a4bbb150b2e32c0d4
- stable/c/12ce799f7ab1e05bd8fbf79e46f403bfe5597ebc