Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw in the STM32 hardware cryptography driver can trigger recursive spinlock handling during cryptographic finalization, potentially making an affected system unavailable. The supplied CVSS score is 7.5, driven entirely by availability impact; no confidentiality or integrity impact is identified.
Executive priority
Prioritize validation and vendor-supported updates for embedded or appliance fleets using STM32 cryptographic acceleration, especially where outages affect critical services. General Linux fleets without this hardware path are less likely to be exposed. Escalate remediation where driver use is confirmed; exploitation evidence remains absent.
Technical view
The stm32/cryp driver’s interrupt-mode finalize operation was called without disabling bottom halves, producing a spinlock recursion warning. The referenced stable-kernel commits correct this locking context. The sources identify affected Linux versions including 4.16, 6.6.50, 6.10.9, and 6.11, but do not fully define distribution-specific package ranges.
Likely exposure
Exposure is most plausible on Linux systems using the vulnerable STM32 cryptographic hardware driver and reaching its interrupt-mode finalization path. Kernel version alone is insufficient: hardware, driver configuration, backports, and vendor packaging affect exposure. The supplied affected-version data is incomplete and should not be treated as a definitive range.
Exploitation context
The supplied record is not in KEV, and no cited source establishes active exploitation or a public exploit. Although the CVSS vector states network reachability without privileges or interaction, the bundle does not explain how remote input reaches this hardware-driver path. Treat practical exploitability as unconfirmed.
Researcher notes
The core defect is a locking-context error: bottom halves were not disabled around interrupt-mode finalization, allowing spinlock recursion. The bundle provides correction commits but no reproducer, affected configuration details, crash conditions, or complete version boundaries. Researchers should avoid inferring universal remote exploitability from the CVSS vector alone.
Mitigation direction
- Apply a vendor-supported kernel containing the applicable referenced stable-kernel correction.
- Check distribution or device-vendor advisories for package-specific fixed versions and backports.
- Prioritize exposed or availability-critical systems confirmed to use the STM32 cryptography driver.
- If patching is delayed, consult vendor guidance about safely disabling the affected driver or hardware acceleration.
Validation and detection
- Inventory kernel versions, distribution package revisions, and vendor backport status.
- Confirm whether the STM32 cryptography driver is built, loaded, and used on each system.
- Compare kernel source or package changelogs with the three referenced correction commits.
- After updating, verify the running kernel and monitor logs for spinlock-recursion warnings.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-47658 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6LinuxVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/d93a2f86b0a998aa1f0870c85a2a60a0771ef89aCVE reference, Linux
- https://git.kernel.org/stable/c/5d734665cd5d93270731e0ff1dd673fec677f447CVE reference, Linux
- https://git.kernel.org/stable/c/56ddb9aa3b324c2d9645b5a7343e46010cf3f6ceCVE reference, Linux
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.