CVE-2025-38536
BaseFortify
Publication date: 2025-08-16
Last updated on: 2025-11-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | 6.16 |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a use-after-free bug in the Linux kernel's airoha driver. Specifically, the function airoha_npu_get() used the np->name field after the node np was released by calling of_node_put(np). Since of_node_put(np) was called unconditionally after of_find_device_by_node(np), if the device pdev was NULL, it could lead to accessing memory that had already been freed, causing a use-after-free condition. The fix involved moving the call to of_node_put(np) after error checks to ensure the node is only released after handling both error and success cases properly, preventing potential resource issues.
How can this vulnerability impact me? :
This use-after-free vulnerability can lead to undefined behavior such as system crashes, memory corruption, or potential escalation of privileges if exploited. It may cause instability or security risks in systems running the affected Linux kernel version with the airoha driver.