CVE-2026-23096
Use-After-Free in Linux Kernel uacce cdev Cleanup Causes Hang
Publication date: 2026-02-04
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 | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 5.11 (inc) to 5.15.199 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.162 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.122 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.68 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.8 (exc) |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | From 5.7 (inc) to 5.10.249 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in the Linux kernel's uacce component related to character device (cdev) handling during cleanup. Specifically, when the function cdev_device_add fails, it releases the cdev memory internally. However, if cdev_device_del is subsequently called, it causes a hang error. The fix involves checking the return value of cdev_device_add and clearing the uacce->cdev pointer to prevent calling cdev_device_del in the uacce_remove function, thereby avoiding the hang.
How can this vulnerability impact me? :
This vulnerability can cause the system to hang or become unresponsive when certain cleanup operations involving character devices are performed. This may lead to system instability or denial of service conditions if the affected code path is triggered.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
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