Security readout for executives and security teams
Plain-English summary
A Linux storage driver flaw can access memory outside an expected array when certain MegaRAID systems use DRAM interleaving. Triggering requires local, low-privileged access according to the supplied CVSS data. Potential consequences include sensitive-data exposure, limited data modification, or system disruption, although the source bundle documents a sanitizer-detected failure rather than a demonstrated attack.
Executive priority
Treat this as a high-priority infrastructure patch for exposed storage servers, especially availability-sensitive systems. It is not supported as an internet-scale emergency because the stated attack vector is local and no active exploitation is documented. Complete hardware and kernel inventory promptly, then apply supported updates through normal expedited maintenance.
Technical view
The megaraid_sas driver can derive an invalid NUMA node index of -1 during MSI-X vector allocation and device probing. That value reaches an x86 topology cpumask array, producing an out-of-bounds access. The supplied CVSS 3.1 score is 7.3 with local, low-complexity, low-privilege attack conditions and high confidentiality and availability impacts.
Likely exposure
Exposure is most likely on affected Linux kernels where the megaraid_sas driver manages compatible MegaRAID hardware and DRAM interleaving is enabled. Systems without that driver or hardware are less likely to encounter the documented condition. The supplied version data is ambiguous, so kernel package provenance and vendor advisories should determine actual exposure.
Exploitation context
The supplied record is not in KEV and provides no evidence of active exploitation or a public exploit. It describes an out-of-bounds access detected during driver initialization. CVSS characterizes attack access as local with low privileges, but the bundle does not establish a reliable exploitation path or confirm real-world confidentiality, integrity, or availability impact.
Researcher notes
The observed path is megasas_probe_one to megasas_alloc_irq_vectors, followed by topology.h indexing with -1. Five stable-kernel commit references indicate backports, but the bundle does not map each commit to an exact release. The affected-version list is internally unclear, including an unexplained version “0”; validate boundaries against distribution advisories and commit ancestry.
Mitigation direction
- Install a vendor-supported kernel containing the applicable cited stable fix.
- Review Linux distribution guidance for the exact fixed kernel package and required reboot.
- Prioritize storage hosts using megaraid_sas with DRAM interleaving enabled.
- If immediate updating is impossible, assess whether affected hardware or driver use can be safely reduced.
Validation and detection
- Inventory kernel versions, distributions, and hosts loading the megaraid_sas module.
- Identify compatible MegaRAID controllers and determine whether DRAM interleaving is enabled.
- Check kernel logs for megasas_alloc_irq_vectors and topology array-index-out-of-bounds reports.
- Confirm the installed kernel package incorporates the applicable cited stable commit.
- Reboot after updating and verify the host runs the corrected kernel.
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-2025-38239 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.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H1.85.5LinuxVulnerability scoring details
Base CVSS 3.1 score
7.3HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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/f1064b3532192e987ab17be7281d5fee36fd25e1CVE reference, Linux
- https://git.kernel.org/stable/c/bf2c1643abc3b2507d56bb6c22bf9897272f8a35CVE reference, Linux
- https://git.kernel.org/stable/c/19a47c966deb36624843b7301f0373a3dc541a05CVE reference, Linux
- https://git.kernel.org/stable/c/074efb35552556a4b3b25eedab076d5dc24a8199CVE reference, Linux
- https://git.kernel.org/stable/c/752eb816b55adb0673727ba0ed96609a17895654CVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.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.