Security readout for executives and security teams
Plain-English summary
A Linux networking-driver flaw can crash ARM64 systems using the MANA network adapter when receive-buffer memory is misaligned under certain MTU configurations, including 4000. The primary business impact is service interruption or host unavailability; the supplied sources do not indicate data theft or modification.
Executive priority
Treat this as a high-priority availability issue for ARM64 MANA deployments, especially critical network services or unusual MTUs. Expedite inventory and vendor-supported kernel updates. Systems outside that hardware-and-driver combination are less likely to be exposed based on the supplied evidence.
Technical view
The MANA driver passed an insufficiently aligned RX allocation size to napi_build_skb(). This could misalign skb_shared_info and cause an ARM64 alignment fault during atomic operations on dataref, producing a kernel panic. The kernel fix aligns the allocation-size calculation. The supplied CVSS is 7.5, reflecting remotely reachable availability impact.
Likely exposure
Exposure appears limited to affected Linux kernels on ARM64 systems using the MANA driver, particularly with relevant MTU settings. The supplied affected-version data is ambiguous and should not be treated as a reliable version range; confirm distribution backports and vendor status for each deployed kernel.
Exploitation context
CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public weaponized exploit. The CVSS vector describes network-reachable, unauthenticated availability impact, but the bundle does not establish practical exploitation conditions beyond the MANA, ARM64, and MTU-related crash scenario.
Researcher notes
The failure originates from RX buffer allocation-size alignment affecting skb_shared_info placement. ARM64 atomic access to the misaligned dataref can fault during packet processing. The sources document a corrective alignment change and sample panic, but do not establish exploit reliability, affected traffic patterns, or complete vulnerable-version boundaries.
Mitigation direction
- Install a vendor-supported kernel update containing the MANA RX allocation-alignment fix.
- Check distribution advisories because fixed commits may be backported without changing to an upstream version.
- Prioritize affected ARM64 hosts providing critical or highly available network services.
- If patching is delayed, ask the vendor whether changing affected MTU settings is a supported temporary measure.
Validation and detection
- Inventory ARM64 Linux hosts and identify systems actively using the MANA network driver.
- Record deployed kernel package versions and compare them with distribution security advisories.
- Confirm the installed kernel contains the referenced fix or an equivalent vendor backport.
- Review kernel logs for alignment faults or panic traces involving skb_clone, dataref, or MANA traffic processing.
- Validate updates in a representative environment without intentionally crashing production systems.
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-45001 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/65f20b174ec0172f2d6bcfd8533ab9c9e7e347faCVE reference, Linux
- https://git.kernel.org/stable/c/e6bea6a45f8a401f3d5a430bc81814f0cc8848cfCVE reference, Linux
- https://git.kernel.org/stable/c/32316f676b4ee87c0404d333d248ccf777f739bcCVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/03/msg00028.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.