CVE-2025-38450
BaseFortify
Publication date: 2025-07-25
Last updated on: 2025-11-19
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 | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-476 | The product dereferences a pointer that it expects to be valid but is NULL. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a NULL pointer dereference in the Linux kernel's mt7925 WiFi driver. It occurs in the function mt7925_sta_set_decap_offload() when the function is called before the station (device) is fully initialized, causing the code to access a NULL pointer (msta->vif). This leads to a kernel panic (crash) in Access Point (AP) mode. The fix involves adding a NULL check for msta->vif and ensuring the station is ready before proceeding, preventing the crash.
How can this vulnerability impact me? :
This vulnerability can cause the Linux kernel to crash (kernel panic) when the affected WiFi driver function is triggered prematurely. This can lead to system instability, denial of service, or unexpected reboots on devices running the vulnerable kernel with the mt7925 WiFi driver in AP mode.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for kernel panic or crash messages related to mt7925_sta_set_decap_offload(). Specifically, look for kernel paging request errors or page faults referencing mt7925_sta_set_decap_offload and NULL pointer dereference in the mt7925 driver. Commands such as 'dmesg | grep mt7925_sta_set_decap_offload' or 'journalctl -k | grep mt7925_sta_set_decap_offload' can help identify these crash traces.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the fix is applied, which adds a NULL check for msta->vif before accessing its members to prevent kernel panic. Until the update is applied, avoid deploying the affected mt7925 driver in AP mode or triggering the mt7925_sta_set_decap_offload() function before the station is fully initialized.