CVE-2025-38197: platform/x86: dell_rbu: Fix list usage
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: dell_rbu: Fix list usage
Pass the correct list head to list_for_each_entry*() when looping through
the packet list.
Without this patch, reading the packet data via sysfs will show the data
incorrectly (because it starts at the wrong packet), and clearing the
packet list will result in a NULL pointer dereference.
Security readout for executives and security teams
Plain-English summary
A Linux Dell BIOS update driver uses the wrong list starting point when handling firmware packets. Reading packet data can return incorrect contents, while clearing packets can crash the kernel through a NULL pointer dereference. Exploitation requires local, low-privileged access; the supplied evidence does not establish remote or active exploitation.
Executive priority
Treat as an accelerated patching item for exposed multi-user or Dell firmware-management systems. It is high severity because a local user may trigger incorrect data handling or a system crash, but current evidence does not justify emergency incident response based on active exploitation.
Technical view
CVE-2025-38197 affects list traversal in platform/x86/dell_rbu. The wrong list head is passed to list_for_each_entry-style processing, causing packet reads through sysfs to begin incorrectly and packet-list clearing to dereference NULL. The supplied CVSS 3.1 score is 7.3 with local access, low complexity, low privileges, no user interaction, and high availability impact.
Likely exposure
Exposure is most likely on affected Linux kernels where the Dell RBU driver and relevant sysfs packet operations are available. Local access and low privileges are required according to the CVSS vector. The flattened version data is ambiguous, so confirm affected and fixed releases through kernel or distribution advisories.
Exploitation context
The source bundle marks this CVE as absent from KEV and provides no evidence of exploitation in the wild. The documented outcomes are incorrect packet-data disclosure and a kernel NULL pointer dereference. No evidence establishes remote reachability, privilege escalation, or reliable code execution.
Researcher notes
The affected-version array appears flattened and includes both release numbers and repeated commit identifiers, preventing reliable range interpretation from this bundle alone. The description directly supports incorrect sysfs output and NULL-dereference denial of service. Although the CVSS vector claims high confidentiality impact, the supplied narrative does not explain its scope.
Mitigation direction
Install a vendor-supported kernel containing the cited stable fix.
Check Linux distribution advisories for the exact corrected package version.
Prioritize shared systems where untrusted users have local accounts.
Restrict unnecessary local access while patching is pending.
Validation and detection
Inventory kernel versions on systems using the Dell RBU driver.
Determine whether the driver and relevant sysfs interfaces are present.
Compare installed packages with distribution security advisories.
Confirm the installed kernel incorporates the applicable stable commit.
Test firmware-update workflows safely after upgrading.
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-38197 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
10Source 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.