In the Linux kernel, the following vulnerability has been resolved:
KEYS: trusted: dcp: fix NULL dereference in AEAD crypto operation
When sealing or unsealing a key blob we currently do not wait for
the AEAD cipher operation to finish and simply return after submitting
the request. If there is some load on the system we can exit before
the cipher operation is done and the buffer we read from/write to
is already removed from the stack. This will e.g. result in NULL
pointer dereference errors in the DCP driver during blob creation.
Fix this by waiting for the AEAD cipher operation to finish before
resuming the seal and unseal calls.
Security readout for executives and security teams
Plain-English summary
A Linux kernel timing flaw can let trusted-key sealing or unsealing continue after a temporary memory buffer is gone. Under system load, this can trigger a NULL-pointer dereference in the DCP crypto driver, potentially crashing the system. The supplied CVSS score is 7.8, reflecting high local impact.
Executive priority
Treat this as high priority where affected DCP-backed trusted-key functionality is used, especially on multi-user or locally accessible systems. For other Linux systems, first establish whether the vulnerable path and affected kernel are present before escalating emergency remediation.
Technical view
The trusted-key DCP path submitted an AEAD request asynchronously without waiting for completion. Seal or unseal could return while the operation still referenced a stack buffer, causing unsafe access and observed NULL dereferences during blob creation. The cited kernel changes make these calls wait for AEAD completion.
Likely exposure
Exposure is limited to Linux systems using the affected trusted-key DCP cryptographic path. The bundle marks Linux 6.11, 6.11.8, and 6.12 as affected, but its version formatting is ambiguous. Confirm the status of each distribution kernel and backported fix with its vendor.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction. The supplied sources do not establish active exploitation, and the CVE is not identified as being in KEV. Do not interpret that absence as proof exploitation is impossible.
Researcher notes
This is CWE-476 arising from asynchronous completion and stack-buffer lifetime handling, rather than a generic remote flaw. The description documents NULL dereferences, while the CVSS vector assigns high confidentiality, integrity, and availability impacts. The supplied evidence does not explain a demonstrated path to those broader impacts.
Mitigation direction
Install a vendor kernel release containing the cited upstream fix.
Prioritize systems using trusted keys with DCP-backed cryptographic operations.
Check distribution advisories for backported fixes and exact affected package versions.
Restrict unnecessary local access until affected systems are updated.
Validation and detection
Inventory kernel versions on systems supporting DCP-backed trusted keys.
Confirm whether deployed kernels contain either cited corrective commit or an equivalent backport.
Review kernel logs for DCP NULL dereferences during trusted-key blob operations.
After updating, verify trusted-key sealing and unsealing complete reliably under normal load.
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.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
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.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.