CVE-2025-38536: net: airoha: fix potential use-after-free in airoha_npu_get()
In the Linux kernel, the following vulnerability has been resolved:
net: airoha: fix potential use-after-free in airoha_npu_get()
np->name was being used after calling of_node_put(np), which
releases the node and can lead to a use-after-free bug.
Previously, of_node_put(np) was called unconditionally after
of_find_device_by_node(np), which could result in a use-after-free if
pdev is NULL.
This patch moves of_node_put(np) after the error check to ensure
the node is only released after both the error and success cases
are handled appropriately, preventing potential resource issues.
Security readout for executives and security teams
Plain-English summary
A Linux kernel networking driver can access a device-tree object after releasing it. On affected systems using the Airoha NPU path, this memory-safety error could cause a crash or potentially allow a local, low-privileged attacker to compromise confidentiality, integrity, and availability. The supplied evidence does not establish active exploitation.
Executive priority
Treat this as a high-priority kernel maintenance issue for appliances or hosts using Airoha NPU functionality, especially those permitting local untrusted access. Scope exposure promptly, then apply supported kernel updates. Broader emergency action is not supported because active exploitation is not evidenced.
Technical view
In airoha_npu_get(), of_node_put(np) could release the node before an error path referenced np->name when of_find_device_by_node(np) returned NULL. The fix delays releasing the node until error and success handling no longer require it, preventing the potential use-after-free.
Likely exposure
Exposure is likely concentrated in systems running an affected Linux kernel with the Airoha NPU driver present and the vulnerable path reachable. The bundle names 6.15, 6.15.8, and 6.16, but does not clearly express exact range boundaries. Distribution backports may alter exposure.
Exploitation context
The CVSS 3.1 vector scores this 7.8: local access, low privileges, low complexity, and no user interaction, with potentially high impact. CVE is not listed as KEV in the supplied bundle, and no supplied source reports exploitation in the wild or provides proof of practical exploitation.
Researcher notes
The vulnerable condition depends on device lookup returning NULL after the node reference was released. The sources establish a potential use-after-free and its lifetime-management fix, but do not demonstrate controllable memory reuse, a working exploit, affected hardware breadth, or exact downstream package versions.
Mitigation direction
Identify kernels containing the Airoha NPU driver and compare versions against vendor advisories.
Upgrade to a vendor-supported kernel containing one of the referenced upstream fixes.
Prioritize systems where untrusted or low-privileged users can execute locally.
If updates are delayed, consult the distribution vendor for supported mitigations.
Validation and detection
Record the running kernel version and distribution package revision on potentially affected systems.
Check distribution changelogs for backports of the referenced Linux stable commits.
Confirm whether the Airoha NPU driver is built, loaded, or used.
After updating, verify the installed kernel includes the fix and rebooted systems run it.
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-38536 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.