CVE-2026-23344
Received Received - Intake
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
In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix use-after-free on error path In the error path of sev_tsm_init_locked(), the code dereferences 't' after it has been freed with kfree(). The pr_err() statement attempts to access t->tio_en and t->tio_init_done after the memory has been released. Move the pr_err() call before kfree(t) to access the fields while the memory is still valid. This issue reported by Smatch static analyser
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-25
Last Modified
2026-04-24
Generated
2026-06-16
AI Q&A
2026-03-25
EPSS Evaluated
2026-06-14
NVD
CVE-2026-23344
EUVD
EUVD-2026-15311
Affected Vendors & Products
Showing 9 associated CPEs
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
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

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.

Impact Analysis

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.

Mitigation Strategies

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.
Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-23344. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart