CVE-2024-39478: crypto: starfive - Do not free stack buffer
In the Linux kernel, the following vulnerability has been resolved:
crypto: starfive - Do not free stack buffer
RSA text data uses variable length buffer allocated in software stack.
Calling kfree on it causes undefined behaviour in subsequent operations.
Security readout for executives and security teams
Plain-English summary
A Linux StarFive crypto driver error tries to release memory stored on the software stack while handling variable-length RSA text. This can cause unpredictable kernel behavior, potentially including corruption or a crash. The supplied CVSS score is 7.8 (high), but the sources do not establish active exploitation or universal exposure across Linux systems.
Executive priority
Treat this as a high-priority, targeted kernel update rather than an internet-wide emergency. Quickly identify StarFive-based devices and locally accessible multi-user systems, then apply supported updates. Broader escalation should depend on confirmed driver use, vendor exposure guidance, or new evidence of exploitation.
Technical view
The StarFive crypto RSA path passes a stack-allocated, variable-length text buffer to kfree. Freeing non-heap memory is undefined behavior and may disrupt later kernel operations. The CVSS vector describes a local, low-complexity attack requiring low privileges, with potential high confidentiality, integrity, and availability impact. Trigger prerequisites are not documented in the bundle.
Likely exposure
Exposure is most plausible on systems running an affected kernel build where the StarFive crypto driver processes RSA operations. The bundle lists Linux 6.5, 6.9.5, and 6.10 as affected, alongside an ambiguous โ0โ entry. Distribution backports may change exposure, so version numbers alone are insufficient.
Exploitation context
The supplied record is not in KEV and provides no evidence of active exploitation or a public proof of concept. CVSS characterizes exploitation as local and requiring low privileges, not remotely reachable over a network. Whether unprivileged users can reliably reach the vulnerable RSA path is not established by these sources.
Researcher notes
The root cause is an invalid free: variable-length RSA text is stack-allocated and then passed to kfree. The two referenced stable-tree commits document corrections, but the bundle provides no fixed-version mapping, reachable call-path analysis, crash evidence, or exploit confirmation. The duplicated commit identifier and ambiguous version entry reduce precision.
Mitigation direction
Consult the Linux distribution or device vendor for affected-build and fixed-package mapping.
Apply a vendor-supported kernel update containing the applicable stable correction.
Prioritize devices that use the StarFive crypto driver for RSA operations.
Follow vendor-approved temporary guidance if an immediate kernel update is unavailable.
Validation and detection
Inventory kernel builds on devices using StarFive hardware or crypto functionality.
Confirm whether the StarFive crypto driver is present, enabled, and processing RSA workloads.
Check package changelogs for either referenced stable correction or an acknowledged backport.
After updating, verify the running kernel matches the vendor-designated fixed package.
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-2024-39478 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.
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.