CVE-2026-23221
Use-After-Free in Linux fsl-mc Driver Override Handling
Publication date: 2026-02-18
Last updated on: 2026-03-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.19 (inc) to 6.19.1 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.164 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.11 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.127 (exc) |
| linux | linux_kernel | From 5.10 (inc) to 5.15.201 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.74 (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 is a use-after-free issue in the Linux kernel's fsl-mc bus driver, specifically in the driver_override_show() function.
The problem occurs because driver_override_show() reads the driver_override string without holding the device_lock, while driver_override_store() modifies and frees this string while holding the device_lock.
If the string is freed by the store function while being read by the show function, it can lead to a concurrent use-after-free condition.
The fix involves holding the device_lock during the read operation to prevent this race condition.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know
How can this vulnerability impact me? :
A use-after-free vulnerability can lead to undefined behavior including system crashes, data corruption, or potential escalation of privileges if exploited.
In this case, concurrent access to freed memory in the Linux kernel could destabilize the system or be leveraged by an attacker to execute arbitrary code or cause denial of service.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know