CVE-2026-22995
BaseFortify
Publication date: 2026-01-23
Last updated on: 2026-02-26
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 | From 6.18.4 (inc) to 6.18.6 (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 (UAF) issue in the Linux kernel's ublk driver. It occurs due to a race condition between asynchronous partition scan work and device teardown. Specifically, after scheduling partition scan work, the device may be stopped and its disk freed, but the partition scan worker still tries to access the freed disk, leading to UAF. The fix involves holding a reference to the disk during the scan to prevent accessing freed memory and properly canceling work when the disk is detached.
How can this vulnerability impact me? :
This vulnerability can lead to use-after-free conditions, which may cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or escalate privileges by exploiting the freed memory access in the kernel.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update your Linux kernel to a version that includes the fix for the use-after-free in ublk_partition_scan_work. The fix involves proper reference counting and synchronization to prevent the race condition. Until then, avoid operations that trigger partition scan work concurrently with device teardown. Specifically, ensure your system uses the patched kernel where ublk_get_disk()/ublk_put_disk() are used and flush_work() is replaced with cancel_work_sync() to prevent the issue.