LiveActive security incident?Get immediate response
CVE Record

CVE-2026-45986: crypto: ccree - fix a memory leak in cc_mac_digest()

In the Linux kernel, the following vulnerability has been resolved: crypto: ccree - fix a memory leak in cc_mac_digest() Add cc_unmap_result() if cc_map_hash_request_final() fails to prevent potential memory leak.

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

Security readout for executives and security teams

Plain-English summary

CVE-2026-45986 is a Linux kernel memory-leak fix in the ccree crypto driver. If a specific hash finalization mapping fails, cleanup may be skipped. The public record does not provide CVSS, CWE, exploitability details, or evidence of active exploitation, so business urgency depends on affected kernel use and vendor patch availability.

Executive priority

Treat this as a patch-management item, not an emergency, unless critical systems use affected Linux kernels with relevant crypto driver exposure. The lack of CVSS, KEV listing, and exploitation evidence keeps urgency uncertain, but kernel memory leaks should still be remediated through normal vendor update cycles.

Technical view

The issue is in cc_mac_digest() within Linux kernel crypto ccree code. The fix adds cc_unmap_result() when cc_map_hash_request_final() fails, preventing leaked mapped result state. The CVE record lists Linux kernel versions and multiple stable commit references, but does not include CPEs, CVSS, or a detailed impact analysis.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions where the ccree crypto driver code is present and exercised. The source bundle lacks distro package mappings, CPEs, and hardware or configuration prerequisites, so exact fleet exposure requires local kernel and vendor advisory validation.

Exploitation context

No active exploitation is stated. The KEV flag is false, and the provided sources only describe a resolved memory leak. There is no public source in the bundle showing exploit activity, exploit maturity, privilege requirements, or a remote attack path.

Researcher notes

Evidence is sparse: the record identifies a cleanup omission after cc_map_hash_request_final() failure and links stable commits. It does not establish reachability, attacker control, required privileges, or denial-of-service severity. Analysis should focus on driver configuration, call-path reachability, and distro backport status.

Mitigation direction

  • Check Linux distribution advisories for CVE-2026-45986 package status.
  • Update affected kernels to versions containing the referenced stable fixes.
  • Prioritize systems using ccree crypto functionality or related hardware support.
  • Monitor vendor security notes for CVSS, impact, and backport clarification.
  • Avoid assuming unrelated Linux kernels are affected without vendor confirmation.

Validation and detection

  • Inventory running kernel versions across Linux hosts.
  • Compare kernels against vendor advisories and listed stable commit references.
  • Verify patched builds include the cc_mac_digest() cleanup fix.
  • Check whether ccree support is built, loaded, or operationally relevant.
  • Review memory-pressure telemetry on systems awaiting patching.
Prepared
Confidence
medium
Sources
10

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-45986 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
9Source 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
LinuxLinux63893811b0fcb52f6eaf9811cc08bddd46f81c3e, 63893811b0fcb52f6eaf9811cc08bddd46f81c3e, 63893811b0fcb52f6eaf9811cc08bddd46f81c3e, 63893811b0fcb52f6eaf9811cc08bddd46f81c3e, 63893811b0fcb52f6eaf9811cc08bddd46f81c3e, 63893811b0fcb52f6eaf9811cc08bddd46f81c3e, 63893811b0fcb52f6eaf9811cc08bddd46f81c3e, 63893811b0fcb52f6eaf9811cc08bddd46f81c3eunaffected
LinuxLinux4.17, 0, 5.10.258, 5.15.209, 6.1.175, 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1affected
Weakness

CWE details

No CWE listed

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