CVE-2026-80952

i3c: master: Fix info leak and UAF in device unregister path

HIGH
7.8
CVSS Score
Published: September 11, 2026 at 07:42 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.1%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3a379bbcea0af6280e1ca0d1edfcf4e68cde6ee05.0
Vendor states this is fixed in 109995153898454c7795c2c299fd0a0b57456a4b (fixed)
Vendor states this is fixed in 334cfb5e285cece5dc49fb3fb8ea9b70b2cb5d7e (fixed)
Vendor states this is fixed in 4837be0f9ac2efe5e83b35a696b6242c473d280c (fixed)
Vendor states this is fixed in 94fb9786d67a8f8b899e77381620f86bad94fdf7 (fixed)
Vendor states this is fixed in c16b6f25e0cc2dd1055dde1256cbf5a9e888cf49 (fixed)
Vendor states this is fixed in c64daaaba08e490c8347ff60aacac4dd51249f91 (fixed)
Vendor states this is fixed in d2c743efd2d1ee64e94324664808f623dd865872 (fixed)
Vendor states this is fixed in ef72ff6650c4ebf2b444708d84df66db42f262d9 (fixed)
Vendor states this is fixed in 5.0 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card