I3C registration hang via recursive bus locking
Published Jan 11, 2025 · Updated May 11, 2026
Improper locking in the Linux kernel I3C core from 5.0 allows local users to hang the I3C device-registration path. During i3c_master_register(), i3c_device_uevent() calls i3c_device_get_info(), which tries to reacquire the i3cbus lock already held by registration. The hang requires the I3C registration path and interrupts its completion; no confidentiality or integrity effect is reported.
Summary
What happened
Improper locking in the Linux kernel I3C core from 5.0 allows local users to hang the I3C device-registration path. During i3c_master_register(), i3c_device_uevent() calls i3c_device_get_info(), which tries to reacquire the i3cbus lock already held by registration. The hang requires the I3C registration path and interrupts its completion; no confidentiality or integrity effect is reported.
The record
- CVE
- CVE-2024-43098
- Published
- Jan 11, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-667, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 11, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <1f51ae217d09c361ede900b94735a6d2df6c0344
- Affected versionversion=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <2d98fa2a50b8058de52ada168fa5dbabb574711b
- Affected versionversion=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <5ac1dd51aaa0ce8b5421d1137e857955a4b6f55e
- Affected versionversion=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <6cf7b65f7029914dc0cd7db86fac9ee5159008c6
- Affected versionversion=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <816187b1833908941286e71b0041059a4acd52ed
- Affected versionversion=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <9a2173660ee53d5699744f02e6ab7bf89fcd0b1a
- Affected versionversion=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <ffe19e363c6f8b992ba835a361542568dea17409
- Affected versionversion=5.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo