CVE-2024-43098: i3c: Use i3cdev->desc->info instead of calling i3c_device_get_info() to avoid deadlock
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1f51ae217d09c361ede900b94735a6d2df6c0344, 2d98fa2a50b8058de52ada168fa5dbabb574711b, 5ac1dd51aaa0ce8b5421d1137e857955a4b6f55e; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1.
Low priority for now. Upgrade to Linux Linux 1f51ae217d09c361ede900b94735a6d2df6c0344, 2d98fa2a50b8058de52ada168fa5dbabb574711b, 5ac1dd51aaa0ce8b5421d1137e857955a4b6f55e; azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 6.6.76.1-1; azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 6.6.76.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: i3c: Use i3cdev->desc->info instead of calling i3c_device_get_info() to avoid deadlock A deadlock may happen since the i3c_master_register() acquires &i3cbus->lock twice. See the log below. Use i3cdev->desc->info instead of calling i3c_device_info() to avoid acquiring the lock twice. v2: - Modified the title and commit message ============================================ WARNING: possible recursive locking detected 6.11.0-mainline -------------------------------------------- init/1 is trying to acquire lock: f1ffff80a6a40dc0 (&i3cbus->lock){++++}-{3:3}, at: i3c_bus_normaluse_lock but task is already holding lock: f1ffff80a6a40dc0 (&i3cbus->lock){++++}-{3:3}, at: i3c_master_register other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(&i3cbus->lock); lock(&i3cbus->lock); *** DEADLOCK *** May be due to missing lock nesting notation 2 locks held by init/1: #0: fcffff809b6798f8 (&dev->mutex){....}-{3:3}, at: __driver_attach #1: f1ffff80a6a40dc0 (&i3cbus->lock){++++}-{3:3}, at: i3c_master_register stack backtrace: CPU: 6 UID: 0 PID: 1 Comm: init Call trace: dump_backtrace+0xfc/0x17c show_stack+0x18/0x28 dump_stack_lvl+0x40/0xc0 dump_stack+0x18/0x24 print_deadlock_bug+0x388/0x390 __lock_acquire+0x18bc/0x32ec lock_acquire+0x134/0x2b0 down_read+0x50/0x19c i3c_bus_normaluse_lock+0x14/0x24 i3c_device_get_info+0x24/0x58 i3c_device_uevent+0x34/0xa4 dev_uevent+0x310/0x384 kobject_uevent_env+0x244/0x414 kobject_uevent+0x14/0x20 device_add+0x278/0x460 device_register+0x20/0x34 i3c_master_register_new_i3c_devs+0x78/0x154 i3c_master_register+0x6a0/0x6d4 mtk_i3c_master_probe+0x3b8/0x4d8 platform_probe+0xa0/0xe0 really_probe+0x114/0x454 __driver_probe_device+0xa0/0x15c driver_probe_device+0x3c/0x1ac __driver_attach+0xc4/0x1f0 bus_for_each_dev+0x104/0x160 driver_attach+0x24/0x34 bus_add_driver+0x14c/0x294 driver_register+0x68/0x104 __platform_driver_register+0x20/0x30 init_module+0x20/0xfe4 do_one_initcall+0x184/0x464 do_init_module+0x58/0x1ec load_module+0xefc/0x10c8 __arm64_sys_finit_module+0x238/0x33c invoke_syscall+0x58/0x10c el0_svc_common+0xa8/0xdc do_el0_svc+0x1c/0x28 el0_svc+0x50/0xac el0t_64_sync_handler+0x70/0xbc el0t_64_sync+0x1a8/0x1ac
- Published
- Jan 11, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- CWE-667
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel5.0 and later · before 5.4.287
- linux linux kernel5.5 and later · before 5.10.231
- linux linux kernel5.11 and later · before 5.15.174
- linux linux kernel5.16 and later · before 6.1.120
- linux linux kernel6.2 and later · before 6.6.66
- linux linux kernel6.7 and later · before 6.12.5
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.0affected
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 9a2173660ee53d5699744f02e6ab7bf89fcd0b1aaffected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 5ac1dd51aaa0ce8b5421d1137e857955a4b6f55eaffected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 2d98fa2a50b8058de52ada168fa5dbabb574711baffected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 816187b1833908941286e71b0041059a4acd52edaffected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before ffe19e363c6f8b992ba835a361542568dea17409affected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 1f51ae217d09c361ede900b94735a6d2df6c0344affected · git
- 3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 and later · before 6cf7b65f7029914dc0cd7db86fac9ee5159008c6affected · git
- before 5.0not affected · semver
- 5.4.287 and later · up to and including 5.4.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux | before 5.10.234-1 | 5.10.234-1 |
| Debian:11 | linux-6.1 | before 6.1.128-1~deb11u1 | 6.1.128-1~deb11u1 |
| Debian:12 | linux | before 6.1.123-1 | 6.1.123-1 |
| Debian:13 | linux | before 6.12.5-1 | 6.12.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2024-56780Jan 8, 2025 · quota: flush quota_release_work upon quota writeback22Monitor
- ← EarlierCVE-2024-41149Jan 11, 2025 · block: avoid to reuse `hctx` not removed from cpuhp callback list31Monitor
- Later →CVE-2024-45828Jan 11, 2025 · i3c: mipi-i3c-hci: Mask ring interrupts before ring stop request22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1f51ae217d09c361ede900b94735a6d2df6c0344 | Vendor (CNA) |
| Linux Linux | 2d98fa2a50b8058de52ada168fa5dbabb574711b | Vendor (CNA) |
| Linux Linux | 5ac1dd51aaa0ce8b5421d1137e857955a4b6f55e | Vendor (CNA) |
| Linux Linux | 6cf7b65f7029914dc0cd7db86fac9ee5159008c6 | Vendor (CNA) |
| Linux Linux | 816187b1833908941286e71b0041059a4acd52ed | Vendor (CNA) |
| Linux Linux | 9a2173660ee53d5699744f02e6ab7bf89fcd0b1a | Vendor (CNA) |
| Linux Linux | ffe19e363c6f8b992ba835a361542568dea17409 | Vendor (CNA) |
| azl3 kernel 6.6.64.2-9 on Azure Linux 3.0 | 6.6.76.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| azl3 kernel 6.6.76.1-1 on Azure Linux 3.0 | 6.6.76.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-2 on CBL Mariner 2.0 | 5.15.176.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.173.1-2 on CBL-Mariner 2.0 | 5.15.176.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-1 on CBL Mariner 2.0 | 5.15.176.3-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.123-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.1 | 6.1.128-1~deb11u1 · Debian:11 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/2d98fa2a50b8058de52ada168fa5dbabb574711b
- git.kernel.org/stable/c/5ac1dd51aaa0ce8b5421d1137e857955a4b6f55e
- git.kernel.org/stable/c/6cf7b65f7029914dc0cd7db86fac9ee5159008c6
- git.kernel.org/stable/c/816187b1833908941286e71b0041059a4acd52ed
- git.kernel.org/stable/c/9a2173660ee53d5699744f02e6ab7bf89fcd0b1a
- git.kernel.org/stable/c/ffe19e363c6f8b992ba835a361542568dea17409
- lists.debian.org/debian-lts-announce/2025/03/msg00001.html
- lists.debian.org/debian-lts-announce/2025/03/msg00002.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.