CVE-2026-80952 i3c: master: Fix info leak and UAF in device unregister path

High 7.8 Published Updated

A use-after-free and information leak in the Linux kernel i3c master driver allows attackers to read kernel stack memory or potentially execute code during device unregistration.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2026-80952?

CVE-2026-80952 is a high-severity use after free vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Which versions are affected by CVE-2026-80952?

How do I fix CVE-2026-80952?

Apply the vendor's patch.

Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.

Is CVE-2026-80952 being exploited?

There is no known exploitation of CVE-2026-80952 in the wild and no public exploit code.

Sources

Also known as AZL-100211, BELL-CVE-2026-80952, DEBIAN-CVE-2026-80952, GHSA-m64m-jwhp-5878, UBUNTU-CVE-2026-80952.

Is CVE-2026-80952 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free