In the Linux kernel, the following vulnerability has been resolved: i3c: master: Fix info leak and UAF in device unregister path… (CVE-2026-80952)
A vulnerability in the Linux kernel's i3c master device unregister path could lead to an information leak and use-after-free (UAF) condition. The issue arises because the device descriptor is cleared prematurely before device_unregister() completes, causing race conditions where kernel stack contents may be leaked and driver callbacks may encounter unexpected NULL pointers. The fix involves maintaining the device descriptor valid until device_unregister() finishes by taking an extra device reference and clearing the descriptor afterward.
AI Analysis
Technical Summary
The Linux kernel's i3c master device unregister function i3c_master_unregister_i3c_devs() previously cleared the device descriptor before calling device_unregister(). During device_unregister(), device_del() emits a KOBJ_REMOVE uevent and unbinds the driver while the device descriptor is still expected to be valid. This race condition allows i3c_device_uevent() and a racing modalias_show() to observe a NULL descriptor and fall back to an uninitialized stack structure, leaking kernel stack contents in the modalias. Additionally, driver remove callbacks may encounter unexpected NULL descriptors during unbind, causing use-after-free issues. The fix keeps the descriptor valid until device_unregister() completes by taking an extra reference with get_device() before unregistering and releasing it afterward, preventing both information leakage and UAF.
Potential Impact
This vulnerability can lead to leakage of kernel stack contents through the generated modalias, potentially exposing sensitive kernel memory information. It also introduces a use-after-free condition during device unregistration, which could cause instability or crashes in kernel drivers handling the i3c devices. There is no indication of known exploits in the wild.
Mitigation Recommendations
A fix has been implemented that keeps the device descriptor valid until device_unregister() completes by taking an extra device reference before unregistering and clearing the descriptor afterward. Users should update their Linux kernel to a version that includes this fix once available. Since this is a kernel-level vulnerability, applying the official patch or kernel update is the recommended remediation.
In the Linux kernel, the following vulnerability has been resolved: i3c: master: Fix info leak and UAF in device unregister path… (CVE-2026-80952)
Description
A vulnerability in the Linux kernel's i3c master device unregister path could lead to an information leak and use-after-free (UAF) condition. The issue arises because the device descriptor is cleared prematurely before device_unregister() completes, causing race conditions where kernel stack contents may be leaked and driver callbacks may encounter unexpected NULL pointers. The fix involves maintaining the device descriptor valid until device_unregister() finishes by taking an extra device reference and clearing the descriptor afterward.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel's i3c master device unregister function i3c_master_unregister_i3c_devs() previously cleared the device descriptor before calling device_unregister(). During device_unregister(), device_del() emits a KOBJ_REMOVE uevent and unbinds the driver while the device descriptor is still expected to be valid. This race condition allows i3c_device_uevent() and a racing modalias_show() to observe a NULL descriptor and fall back to an uninitialized stack structure, leaking kernel stack contents in the modalias. Additionally, driver remove callbacks may encounter unexpected NULL descriptors during unbind, causing use-after-free issues. The fix keeps the descriptor valid until device_unregister() completes by taking an extra reference with get_device() before unregistering and releasing it afterward, preventing both information leakage and UAF.
Potential Impact
This vulnerability can lead to leakage of kernel stack contents through the generated modalias, potentially exposing sensitive kernel memory information. It also introduces a use-after-free condition during device unregistration, which could cause instability or crashes in kernel drivers handling the i3c devices. There is no indication of known exploits in the wild.
Mitigation Recommendations
A fix has been implemented that keeps the device descriptor valid until device_unregister() completes by taking an extra device reference before unregistering and clearing the descriptor afterward. Users should update their Linux kernel to a version that includes this fix once available. Since this is a kernel-level vulnerability, applying the official patch or kernel update is the recommended remediation.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-m64m-jwhp-5878
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-80952"]
Threat ID: 6aa4a02e55bf5e2cf5a86b6b
Added to database: 09/12/2026, 00:43:26 UTC
Last enriched: 09/12/2026, 01:24:51 UTC
Last updated: 09/12/2026, 02:41:26 UTC
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.