Security readout for executives and security teams
Plain-English summary
A flaw in the Linux kernel’s IPMI message handler can corrupt kernel memory when user creation fails to find the requested interface. A local, low-privileged attacker may be able to trigger serious confidentiality, integrity, or availability impacts. The supplied evidence does not establish practical exploitation.
Executive priority
Treat as a high-priority kernel update for multi-user or otherwise locally exposed Linux systems using IPMI. It is less urgent than an unauthenticated remote flaw, but kernel memory corruption can have severe consequences. Prioritize validated exposure rather than relying solely on the ambiguous version list.
Technical view
In ipmi_create_user(), a failed interface lookup can leave the intf list iterator invalid. The affected path then calls atomic_dec() through that invalid pointer, causing potential kernel memory corruption. The fix avoids decrementing nr_users unless the corresponding increment occurred, including during interface shutdown.
Likely exposure
Exposure is limited to systems running an affected Linux kernel where the vulnerable IPMI code path is reachable. The bundle lists Linux 5.19 and several later release boundaries, but its version data is ambiguous. Distribution kernels may contain backported fixes, so version strings alone are insufficient.
Exploitation context
The CVSS 3.1 score is 7.8 with local access and low privileges required, without user interaction. Potential impact spans confidentiality, integrity, and availability. The CVE is not listed as KEV in the supplied bundle, and no cited source establishes active exploitation or a public working exploit.
Researcher notes
The supplied record references five upstream stable commits, likely corresponding to maintained kernel branches. Exact branch-to-fix mapping is not explicit in the bundle. The affected-version array also contains duplicated commit identifiers and unusual boundaries; validate applicability through kernel or distribution advisories before declaring a host vulnerable.
Mitigation direction
- Install a distribution-supported kernel containing the applicable upstream stable fix.
- Check Linux vendor guidance because distribution kernels may backport fixes without changing major versions.
- Reboot into the corrected kernel when required by the vendor update process.
- Prioritize systems where untrusted local users can access relevant IPMI functionality.
Validation and detection
- Inventory running kernel versions and compare them with distribution security advisories.
- Confirm whether the vendor kernel package includes the referenced stable fix commit.
- Verify systems have booted the updated kernel after remediation.
- Assess whether IPMI functionality is enabled or used on potentially affected hosts.
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-38456 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.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/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/cbc1670297f675854e982d23c8583900ff0cc67aCVE reference, Linux
- https://git.kernel.org/stable/c/e2d5c005dfc96fe857676d1d8ac46b29275cb89bCVE reference, Linux
- https://git.kernel.org/stable/c/9e0d33e75c1604c3fad5586ad4dfa3b2695a3950CVE reference, Linux
- https://git.kernel.org/stable/c/7c1a6ddb99858e7d68961f74ae27caeeeca67b6aCVE reference, Linux
- https://git.kernel.org/stable/c/fa332f5dc6fc662ad7d3200048772c96b861cf6bCVE 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.