CVE-2025-38412: platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: dell-wmi-sysman: Fix WMI data block retrieval in sysfs callbacks
After retrieving WMI data blocks in sysfs callbacks, check for the
validity of them before dereferencing their content.
Security readout for executives and security teams
Plain-English summary
A flaw in Linux’s Dell system-management driver can mishandle invalid firmware-management data. On an affected Dell system, a local low-privilege user may be able to trigger serious confidentiality, integrity, or availability impact. It is not remotely exploitable according to the supplied CVSS vector.
Executive priority
Treat this as a high-priority endpoint patching issue, especially where untrusted users have local accounts. It is less urgent than an internet-reachable flaw, but potential kernel-level impact warrants prompt remediation through approved distribution updates.
Technical view
The dell-wmi-sysman driver’s sysfs callbacks could dereference a retrieved WMI data block without first confirming that it was valid. The stable-kernel changes add validation before dereferencing. The supplied CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, scoring 7.8.
Likely exposure
Exposure is most plausible on Dell systems running an affected Linux kernel with dell-wmi-sysman present and usable. The supplied version data names several kernels from 5.11 through 6.16, but does not clearly define complete affected and fixed ranges. Confirm status through the operating-system vendor.
Exploitation context
The supplied record requires local access with low privileges and no user interaction. It is not listed in KEV, and the source bundle provides no evidence of active exploitation or a public exploit. Absence from KEV does not prove exploitation has never occurred.
Researcher notes
The source bundle does not identify a CWE, detailed failure mode, proof of concept, or exploitation telemetry. Repeated commit identifiers and the anomalous version value “0” make the affected-version data unreliable for precise scanning. Use distribution package provenance and the cited stable commits rather than version-string assumptions alone.
Mitigation direction
Install a vendor-supported kernel package that explicitly fixes CVE-2025-38412.
Confirm the updated package incorporates the applicable cited stable-kernel correction.
Prioritize affected Dell multi-user systems and endpoints exposed to untrusted local accounts.
If updates are unavailable, obtain mitigation guidance from the Linux distribution vendor.
Validation and detection
Inventory Dell systems, installed kernel versions, and distribution package revisions.
Determine whether dell-wmi-sysman is present and applicable on each system.
Check vendor advisories and package changelogs for explicit CVE-2025-38412 remediation.
Verify patched systems boot successfully and retain required Dell management functionality.
Review kernel logs for related driver faults, while recognizing they do not establish exploitation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CVE-2025-38412 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.
1CVSS vectors
3Timeline events
1ADP providers
8Source links
CVSS vector scores
1 official score
We 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.