CVE-2025-38342: software node: Correct a OOB check in software_node_get_reference_args()
In the Linux kernel, the following vulnerability has been resolved:
software node: Correct a OOB check in software_node_get_reference_args()
software_node_get_reference_args() wants to get @index-th element, so
the property value requires at least '(index + 1) * sizeof(*ref)' bytes
but that can not be guaranteed by current OOB check, and may cause OOB
for malformed property.
Fix by using as OOB check '((index + 1) * sizeof(*ref) > prop->length)'.
Security readout for executives and security teams
Plain-English summary
A Linux kernel bounds check can miscalculate whether a requested software-node reference fits inside a property. A malformed property may therefore cause memory access beyond the property's boundary. The supplied severity is high, although exploitation requires local access, low privileges, and high complexity.
Executive priority
Treat this as a high-priority kernel maintenance issue, especially for shared or multi-user Linux systems. It is not supported as an emergency internet-wide threat because exploitation is local, complex, and not reported active. Confirm vendor-specific exposure and schedule tested kernel updates promptly.
Technical view
software_node_get_reference_args() checked property length without correctly accounting for the requested zero-based index. The corrected condition requires enough bytes for index plus one references. The supplied CVSS 3.1 score is 7.0, with potential high confidentiality, integrity, and availability impact.
Likely exposure
The bundle identifies Linux kernel releases from 5.0 through 6.16, including specific stable releases, as affected. Package-level exposure remains uncertain because distributors may backport fixes without changing upstream version numbers. Risk is most relevant on systems where low-privileged local users or workloads can reach the vulnerable software-node handling path.
Exploitation context
The supplied vector indicates local, low-privileged, high-complexity exploitation without user interaction. The bundle says this CVE is not in KEV and provides no evidence of active exploitation. It also does not establish how commonly untrusted users can supply or influence the malformed property needed to reach the flaw.
Researcher notes
The version metadata is difficult to interpret: it includes a value of "0" and repeated commit identifiers without a complete package mapping. Use the official correction commits to identify backports. The sources describe an out-of-bounds condition but provide no demonstrated exploit, affected call-path prevalence, or source-backed workaround.
Mitigation direction
Deploy a vendor-supported kernel update containing the official bounds-check correction, then reboot into it.
Where updates are unavailable, follow distributor or appliance-vendor guidance; the sources provide no specific workaround.
Prioritize multi-user hosts, shared compute, and systems running low-trust local workloads.
Validation and detection
Record each system's active kernel release and package build, including container hosts and embedded appliances.
Check vendor advisories and changelogs for a backport of the cited software-node bounds-check correction.
After updating and rebooting, verify the active kernel is the vendor-fixed build.
Review local-access and workload trust boundaries because the supplied vector requires local access and low privileges.
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-38342 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
2ADP providers
11Source 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.