Answer in brief
CVE-2026-80952 records a Unknown severity vulnerability in i3c: master: Fix info leak and UAF in device unregister path. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <c16b6f25e0cc2dd1055dde1256cbf5a9e888cf49 || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <94fb9786d67a8f8b899e77381620f86bad94fdf7 || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <4837be0f9ac2efe5e83b35a696b6242c473d280c || >=3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee0 <d2c743efd2d1ee64e94324664808f623dd865872 | c16b6f25e0cc2dd1055dde1256cbf5a9e888cf49, 94fb9786d67a8f8b899e77381620f86bad94fdf7, 4837be0f9ac2efe5e83b35a696b6242c473d280c, d2c743efd2d1ee64e94324664808f623dd865872 |
| Linux/Linuxgeneric | 5.0 | Not reported |
Published upstream
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 11, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 11, 2026
In the Linux kernel, the following vulnerability has been resolved: i3c: master: Fix info leak and UAF in device unregister path i3c_master_unregister_i3c_devs() clears i3cdev->dev->desc 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. As a result, i3c_device_uevent() and a racing modalias_show() can observe a NULL desc and fall back to an uninitialized stack struct i3c_device_info, leaking kernel stack contents in the generated modalias. Driver .remove() callbacks may also encounter an unexpected NULL desc during unbind. Keep desc valid until device_unregister() has completed. Since device_unregister() drops the device reference and may free the device, take an extra reference with get_device() before unregistering. Clear desc afterwards and release the extra reference with put_device(). This preserves the release-time invariant that desc must be NULL while avoiding both the information leak and a potential use-after-free from writing desc after the device has been released.
Quoted source text, attributed separately from HOL analysis.