CVE-2023-52638: can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock
First published: Wed Apr 03 2024(Updated: )
In the Linux kernel, the following vulnerability has been resolved: can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock The following 3 locks would race against each other, causing the deadlock situation in the Syzbot bug report: - j1939_socks_lock - active_session_list_lock - sk_session_queue_lock A reasonable fix is to change j1939_socks_lock to an rwlock, since in the rare situations where a write lock is required for the linked list that j1939_socks_lock is protecting, the code does not attempt to acquire any more locks. This would break the circular lock dependency, where, for example, the current thread already locks j1939_socks_lock and attempts to acquire sk_session_queue_lock, and at the same time, another thread attempts to acquire j1939_socks_lock while holding sk_session_queue_lock. NOTE: This patch along does not fix the unregister_netdevice bug reported by Syzbot; instead, it solves a deadlock situation to prepare for one or more further patches to actually fix the Syzbot bug, which appears to be a reference counting problem within the j1939 codebase. [mkl: remove unrelated newline change]
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/kernel | <5.15.149 | 5.15.149 |
| redhat/kernel | <6.1.79 | 6.1.79 |
| redhat/kernel | <6.6.18 | 6.6.18 |
| redhat/kernel | <6.7.6 | 6.7.6 |
| redhat/kernel | <6.8 | 6.8 |
| debian/linux | <=5.10.223-1<=5.10.226-1 | 6.1.115-1 6.1.119-1 6.12.5-1 6.12.6-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://git.kernel.org/stable/c/03358aba991668d3bb2c65b3c82aa32c36851170
- https://git.kernel.org/stable/c/26dfe112ec2e95fe0099681f6aec33da13c2dd8e
- https://git.kernel.org/stable/c/559b6322f9480bff68cfa98d108991e945a4f284
- https://git.kernel.org/stable/c/6cdedc18ba7b9dacc36466e27e3267d201948c8d
- https://git.kernel.org/stable/c/aedda066d717a0b4335d7e0a00b2e3a61e40afcf
- https://launchpad.net/bugs/cve/CVE-2023-52638
- https://access.redhat.com/security/cve/CVE-2023-52638
- https://lore.kernel.org/linux-cve-announce/2024040334-CVE-2023-52638-26a6@gregkh/T
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=2273083
- https://access.redhat.com/errata/RHSA-2024:4533
- https://access.redhat.com/errata/RHSA-2024:4554
- https://access.redhat.com/errata/RHSA-2024:4583
- https://bugzilla.redhat.com/show_bug.cgi?id=2273082
- https://git.kernel.org/linus/6cdedc18ba7b9dacc36466e27e3267d201948c8d
- https://security-tracker.debian.org/tracker/CVE-2023-52638
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-52638
- https://nvd.nist.gov/vuln/detail/CVE-2023-52638
- https://ubuntu.com/security/CVE-2023-52638
- agent/title
- agent/type
- collector/nvd-api
- source/NVD
- agent/author
- agent/remedy
- agent/first-publish-date
- collector/launchpad-cve
- source/Launchpad
- agent/severity
- agent/references
- agent/tags
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2023-52638
- agent/software-canonical-lookup
- collector/nvd-cve
- collector/usn-cve
- source/Ubuntu
- agent/description
- agent/event
- collector/security-tracker-debian
- source/Debian
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/trending
- package-manager/redhat
- package-manager/debian