CVE-2026-31527
Use-After-Free in Linux Kernel Driver Core platform Component
Publication date: 2026-04-22
Last updated on: 2026-04-28
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | From 6.13 (inc) to 6.18.21 (exc) |
| linux | linux_kernel | From 6.19 (inc) to 6.19.11 (exc) |
| linux | linux_kernel | From 3.17 (inc) to 6.12.80 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's driver core platform. When a driver is attached using the __driver_attach() function, the bus' match() callback is called without holding the device lock. This causes the driver_override field to be accessed without proper locking, which can lead to a Use-After-Free (UAF) condition.
The issue is fixed by using the driver-core driver_override infrastructure, which manages locking internally to prevent this unsafe access.
How can this vulnerability impact me? :
A Use-After-Free (UAF) vulnerability can lead to undefined behavior including system crashes, data corruption, or potentially allow an attacker to execute arbitrary code with kernel privileges. This can compromise the stability and security of the affected system.