CVE-2026-31527 driver core: platform: use generic driver_override infrastructure

High 7.8 Published Updated

A race condition in the Linux kernel platform driver core allows a use-after-free, potentially enabling local attackers to execute code or escalate privileges.

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-31527?

CVE-2026-31527 is a high-severity use after free vulnerability in Linux kernel, published on 22 Apr 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:

driver core: platform: use generic driver_override infrastructure

When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF.

Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally.

Note that calling match() from __driver_attach() without the device lock held is intentional. [1]

Weakness: CWE-416

Which versions are affected by CVE-2026-31527?

It affects 1 product.

Products include Linux kernel.

How do I fix CVE-2026-31527?

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-31527 being exploited?

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

All Linux kernel vulnerabilities

Sources

Also known as BELL-CVE-2026-31527, DEBIAN-CVE-2026-31527, GHSA-jr2g-46m2-f9rc, ROOT-OS-DEBIAN-11-CVE-2026-31527, ROOT-OS-DEBIAN-12-CVE-2026-31527, ROOT-OS-DEBIAN-13-CVE-2026-31527 and 3 more.

Is CVE-2026-31527 in your software?

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

Check your SBOMs for free