LiveActive security incident?Get immediate response
CVE Record

CVE-2026-23344: crypto: ccp - Fix use-after-free on error path

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

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE is a Linux kernel bug in an error-handling path. A freed memory object can still be referenced when logging an initialization failure. The available sources do not provide a CVSS score, attack scenario, or evidence of exploitation, so urgency depends on affected kernel exposure and vendor patch availability.

Executive priority

Treat as a patch-tracking item unless your fleet runs the affected kernel ranges. There is not enough evidence in the sources to justify emergency response, but kernel memory-safety bugs should be folded into normal accelerated maintenance once vendor updates are available.

Technical view

The flaw is a use-after-free in the Linux kernel crypto ccp code, inside sev_tsm_init_locked(). On an error path, pr_err() reads t->tio_en and t->tio_init_done after kfree(t). The fix moves logging before freeing the object. The issue was reported by the Smatch static analyzer.

Likely exposure

Exposure appears limited to Linux kernels matching the CVE affected version data, including listed 6.19 through 6.19.7 and 7.0 ranges. The source bundle does not identify distributions, packages, configurations, or runtime conditions beyond the crypto ccp and SEV TSM code path.

Exploitation context

The bundle does not show active exploitation, KEV listing, public exploit code, or real-world abuse. It describes a static-analysis finding in an error path. Practical exploitability and impact are not established by the provided sources.

Researcher notes

Key uncertainty is exploitability. The code issue is clear, but sources only describe an error-path dereference after free and a minimal fix. Validate against exact kernel trees and distro backports rather than assuming upstream version strings map cleanly to packaged kernels.

Mitigation direction

  • Update to a kernel build that includes the referenced stable fixes.
  • Track distribution advisories for backported fixes matching your kernel package.
  • Prioritize kernels listed as affected in the CVE record.
  • If patching is delayed, follow vendor guidance; no temporary mitigation is specified in the bundle.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and images.
  • Compare deployed kernels with the affected version data in the CVE record.
  • Confirm vendor kernel changelogs include one of the referenced stable commits or equivalent backport.
  • Review vulnerability scanner findings for kernel package mapping accuracy.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2026-23344 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4be423572da1f4c11f45168e3fafda870ddac9f8, 4be423572da1f4c11f45168e3fafda870ddac9f8unaffected
LinuxLinux6.19, 0, 6.19.7, 7.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.