CVE-2025-38605: Linux kernel · wifi: ath12k: Pass ab pointer directly to ath12k_dp_tx_get_encap_type()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ee4f8e7fa578f9f28cef5f409677db25f4f83d7e : update Linux kernel when convenient.
Data as of 26 Oct 2026, 20:49 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ee4f8e7fa578f9f28cef5f409677db25f4f83d7e, d9d2a0466e981d1be95fc8bdc05806ea21def758, be27a11a42b2190f817b198bf5e753e5e4ac849e +2
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available and has been applied in the Linux kernel source code. Users should update to a fixed version of the Linux kernel that includes the patches referenced by the commit hashes provided. No additional mitigation is required once the system is updated.
Description
A vulnerability in the Linux kernel's ath12k wireless driver could cause a kernel panic due to a NULL pointer dereference during the vdev delete sequence. This occurs because the arvif->ar pointer may become NULL, but the code dereferences it unnecessarily. The issue is fixed by passing a valid pointer directly to avoid the panic.
References
- git.kernel.org/stable/c/be27a11a42b2190f817b198bf5e753e5e4ac849e (opens in a new tab)
- git.kernel.org/stable/c/d9d2a0466e981d1be95fc8bdc05806ea21def758 (opens in a new tab)
- git.kernel.org/stable/c/b508f370f88f277c95e2bd3bc47217a96d668cee (opens in a new tab)
- git.kernel.org/stable/c/ee4f8e7fa578f9f28cef5f409677db25f4f83d7e (opens in a new tab)
- git.kernel.org/stable/c/05062834350f0bf7ad1abcebc2807220e90220eb (opens in a new tab)