Security readout for executives and security teams
Plain-English summary
A remote client can send an invalid offset in a Linux SMC-D version 2 connection proposal. An affected server may then access an incorrect memory address and crash. This creates a potentially serious availability risk, but the supplied sources do not demonstrate code execution, data theft, or data modification.
Executive priority
Prioritize exposed or business-critical systems using SMC-D v2, especially where untrusted clients can connect. Treat remediation as urgent because a remote kernel crash could interrupt services. Scope first where SMC usage is uncertain; the sources do not justify assuming every Linux host is practically reachable through this path.
Technical view
The Linux kernel SMC server trusted the client-controlled smcd_v2_ext_offset field without sufficient bounds validation. An excessive offset could produce an invalid address access and kernel crash. The upstream correction validates the offset before use. Although the supplied CVSS is 9.8, the described and evidenced consequence is a possible crash.
Likely exposure
Exposure requires an affected Linux kernel using the relevant SMC-D v2 server path and accepting proposal messages from a reachable remote client. The supplied affected-version data is ambiguous, so vulnerability managers should confirm distribution-specific package status or whether a cited stable-kernel fix is present.
Exploitation context
The bundle marks this CVE as absent from KEV, and none of the cited sources establishes active exploitation or a public exploit. Network reachability, low stated complexity, and no required privileges increase theoretical risk, but observed exploitation is not evidenced here.
Researcher notes
The record supplies no CWE and does not establish exploitation beyond a possible invalid-address access and crash. It also presents affected-version information in a form that is difficult to interpret reliably. Avoid inferring remote code execution or full confidentiality and integrity compromise solely from the CVSS vector; validate branch ancestry and distribution backports.
Mitigation direction
- Update to a vendor-supported kernel package containing the smcd_v2_ext_offset validation fix.
- Use the cited stable-kernel commits to confirm backport coverage for maintained kernel branches.
- If immediate updating is impossible, consult the Linux distribution vendor for supported temporary mitigations.
- Limit untrusted client access to systems exposing the relevant SMC-D v2 server path.
Validation and detection
- Inventory kernel versions on systems where SMC-D is enabled or operationally required.
- Check each distribution advisory for the exact fixed package version and reboot requirements.
- Verify the installed kernel contains the applicable cited stable-kernel correction.
- Confirm systems booted into the updated kernel after package installation.
- Review kernel logs for unexplained crashes or faults involving SMC processing.
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-47408 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
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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.
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:H/I:H/A:H3.95.9LinuxVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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/a36364d8d4fabb105001f992fb8ff2d3546203d6CVE reference, Linux
- https://git.kernel.org/stable/c/e1cc8be2a785a8f1ce1f597f3e608602c5fccd46CVE reference, Linux
- https://git.kernel.org/stable/c/935caf324b445fe73d7708fae6f7176fb243f357CVE reference, Linux
- https://git.kernel.org/stable/c/48d5a8a304a643613dab376a278f29d3e22f7c34CVE reference, Linux
- https://git.kernel.org/stable/c/9ab332deb671d8f7e66d82a2ff2b3f715bc3a4adCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/03/msg00001.htmlCVE reference, CVE
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.