CVE-2026-23012
BaseFortify
Publication date: 2026-01-25
Last updated on: 2026-03-25
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 | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.19 |
| linux | linux_kernel | 6.17 |
| linux | linux_kernel | From 6.17.1 (inc) to 6.18.7 (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 DAMON subsystem. When damon_call() is executed on a DAMON context that is inactive, it returns an error but leaves a pointer to a deallocated damon_call_control object linked in the context's call_controls list. If another damon_call() is then executed on the same context, it tries to add a new damon_call_control object to the list, which still contains the pointer to the freed object, causing a use-after-free condition.
How can this vulnerability impact me? :
The use-after-free vulnerability could potentially lead to undefined behavior such as kernel crashes or memory corruption. However, exploitation is not straightforward because it requires sysfs write permissions and unusual file writes. Therefore, while it poses a risk, it is not easily exploitable under normal conditions.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version that includes the fix for the DAMON use-after-free issue. The fix involves changes to the damon_call() handling in the kernel, so applying the latest kernel patches or upgrading to a fixed kernel version is recommended. Additionally, restrict sysfs write permissions to prevent unauthorized triggering of the vulnerability.