In the Linux kernel, the following vulnerability has been resolved:
crypto: marvell/cesa - Handle zero-length skcipher requests
Do not access random memory for zero-length skcipher requests.
Just return 0.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s Marvell CESA cryptographic driver can access unintended memory when processing a zero-length encryption request. The kernel fix returns immediately instead. Although rated high severity, practical exposure depends on whether the affected driver is available and reachable on a system.
Executive priority
Treat this as a high-priority kernel maintenance issue on systems using Marvell CESA, especially multi-user or shared-compute hosts. Prioritize exposure discovery before emergency-wide action because the evidence does not establish remote or active exploitation. Apply supported kernel updates through normal expedited patching processes.
Technical view
The marvell/cesa skcipher path failed to handle zero-length requests safely and could access random memory. CVSS 3.1 scores it 7.8 with a local, low-complexity, low-privilege attack model and potential confidentiality, integrity, and availability impact. The supplied sources do not detail the precise memory-access primitive or demonstrated consequences.
Likely exposure
Exposure is most likely on affected Linux kernels using or enabling the Marvell CESA cryptographic driver. Systems without that driver or relevant hardware may not be practically exposed. The supplied version data is insufficient to determine an individual system’s status without checking its distribution kernel and included patches.
Exploitation context
The supplied record is not in KEV, and no cited source reports active exploitation or provides a public proof of concept. The CVSS vector assumes local access with low privileges; it does not indicate remote exploitation. Real-world exploitability remains unclear from the available evidence.
Researcher notes
The core defect and correction are clearly described, but the bundle omits affected hardware details, a CWE, proof of concept, crash evidence, and the exact consequences of the memory access. The CVSS claims complete confidentiality, integrity, and availability impact, but those outcomes are not demonstrated in the supplied narrative. Validate branch-specific fixes carefully.
Mitigation direction
Upgrade to a vendor-supported kernel containing the appropriate stable fix for CVE-2025-38173.
Prioritize systems where marvell/cesa is enabled and untrusted local users or workloads are present.
Reboot as required by vendor instructions so the corrected kernel becomes active.
If patching is delayed, request vendor guidance before disabling the affected driver or cryptographic functionality.
Validation and detection
Inventory running kernel builds and compare them with distribution advisories and the listed stable fixes.
Determine whether the marvell/cesa driver is present, enabled, built in, or loaded.
Verify the running kernel incorporates an applicable listed fix, not merely that an updated package is installed.
In an authorized test environment, confirm zero-length skcipher requests return safely without invalid memory access.
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-2025-38173 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
1ADP providers
11Source links
CVSS vector scores
1 official score
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.