In the Linux kernel, the following vulnerability has been resolved:
platform/x86: alienware-wmi-wmax: Fix `dmi_system_id` array
Add missing empty member to `awcc_dmi_table`.
Security readout for executives and security teams
Plain-English summary
A Linux Alienware WMI driver table is missing its required empty ending entry. Based on the supplied CVSS assessment, a low-privileged local user could potentially expose sensitive information or severely disrupt the system. This is a local-access issue, not a directly remote attack.
Executive priority
Treat this as a high-priority kernel maintenance issue, particularly on shared or multi-user Linux systems. It does not warrant the same perimeter response as a remotely exploitable flaw, but existing local access could provide a path to serious information exposure or service disruption.
Technical view
The alienware-wmi-wmax driver’s awcc_dmi_table lacks an empty terminating dmi_system_id member. The cited Linux stable fixes add that member. CVSS 3.1 rates exploitation as local, low-complexity, low-privilege, and interaction-free, with high confidentiality and availability impact but no rated integrity impact.
Likely exposure
Exposure is most relevant to systems running affected Linux 6.15–6.16-era kernels where the alienware-wmi-wmax code is present and applicable. The supplied normalized version information is ambiguous, and downstream distributions may backport fixes without adopting upstream version numbers. Confirm package-level status with each Linux vendor.
Exploitation context
The bundle marks this CVE as absent from KEV and provides no evidence of active exploitation or a public exploit. This is only absence of evidence in the supplied sources. The CVSS vector indicates that an attacker first needs local, low-privileged access.
Researcher notes
No CWE, precise failure mode, trigger conditions, or exploit primitive is documented in the supplied bundle. Consequences beyond the CVSS impacts should not be assumed. The remediation is narrowly described as adding the missing empty awcc_dmi_table member, with two stable-tree commits cited.
Mitigation direction
Apply a vendor-supported kernel containing the relevant cited Linux stable fix.
Check distribution advisories for package-specific backport and remediation status.
Prioritize multi-user systems and hosts where the affected driver is present or applicable.
If updating is delayed, consult vendor guidance; the supplied sources provide no workaround.
Validation and detection
Inventory running kernel releases and vendor package versions across Linux systems.
Confirm whether each vendor kernel includes the cited fix or an equivalent backport.
Determine whether alienware-wmi-wmax is included and applicable on potentially affected hosts.
After updating, verify the running kernel and documented fix provenance.
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-38661 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
0ADP providers
3Source 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.