CVE-2026-23344
Use-After-Free Vulnerability in Linux Kernel crypto CCP Component
Publication date: 2026-03-25
Last updated on: 2026-04-24
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 | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | 7.0 |
| linux | linux_kernel | From 6.19.1 (inc) to 6.19.7 (exc) |
| linux | linux_kernel | 6.19 |
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 crypto component, specifically in the ccp module. In the error handling path of the function sev_tsm_init_locked(), the code attempts to access memory fields of an object 't' after it has already been freed using kfree(). The problematic pr_err() call tries to read fields 'tio_en' and 'tio_init_done' from 't' after the memory has been released, which can lead to undefined behavior or crashes.
The fix involved moving the pr_err() call to before the kfree(t) call, ensuring that the memory is still valid when accessed.
How can this vulnerability impact me? :
This use-after-free vulnerability can cause the Linux kernel to behave unpredictably, potentially leading to system crashes or kernel panics. Accessing freed memory can also open the door to security risks such as memory corruption, which attackers might exploit to execute arbitrary code or escalate privileges.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is a use-after-free bug in the Linux kernel's crypto ccp component, specifically in the sev_tsm_init_locked() function. To mitigate this vulnerability, you should update your Linux kernel to a version where this issue has been fixed.
- Apply the latest kernel patches or upgrade to a kernel version released after 2026-03-25 that includes the fix.
- Avoid running untrusted code that could trigger this error path until the patch is applied.