CVE-2025-38293 — wifi: ath11k: fix node corruption in ar->arvifs list
In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix node corruption in ar->arvifs list In current WLAN recovery code flow, ath11k_core_halt() only reinitializes the "arvifs" list head. This will cause the list node immediately following the list head to become an invalid list node. Because the prev of that node still points to the list head "arvifs", but the next of the list head "arvifs" no longer points to that list node. When a WLAN recovery occurs during the execution of a vif removal, and it happens before the spin_lock_bh(&ar->data_lock) in ath11k_mac_op_remove_interface(), list_del() will detect the previously mentioned situation, thereby triggering a kernel panic. The fix is to remove and reinitialize all vif list nodes from the list head "arvifs" during WLAN halt. The reinitialization is to make the list nodes valid, ensuring that the list_del() in ath11k_mac_op_remove_interface() can execute normally. Call trace: __list_del_entry_valid_or_report+0xb8/0xd0 ath11k_mac_op_remove_interface+0xb0/0x27c [ath11k] drv_remove_interface+0x48/0x194 [mac80211] ieee80211_do_stop+0x6e0/0x844 [mac80211] ieee80211_stop+0x44/0x17c [mac80211] __dev_close_many+0xac/0x150 __dev_change_flags+0x194/0x234 dev_change_flags+0x24/0x6c devinet_ioctl+0x3a0/0x670 inet_ioctl+0x200/0x248 sock_do_ioctl+0x60/0x118 sock_ioctl+0x274/0x35c __arm64_sys_ioctl+0xac/0xf0 invoke_syscall+0x48/0x114 ... Tested-on: QCA6698AQ hw2.1 PCI WLAN.HSP.1.1-04591-QCAHSPSWPL_V1_V2_SILICONZ_IOE-1
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.3% (30-day exploitation probability)+4
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
- Documented patch — git.kernel.org (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Debian Debian Linux, Linux Linux, Linux Linux Kernel).
- Apply the fixed version or the patch documented under Remediation.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Debian | Debian Linux | version 11.0 | Vulnerable | NIST National Vulnerability Database |
| Linux | Linux | ≥ d5c65159f2895379e11ca13f62feabe93278985d and < 6c139015b597e570dd5962934e9f9a2f4cc8ef48≥ d5c65159f2895379e11ca13f62feabe93278985d and < f9507cf2dd0e1ed5028c0e8240da6fe5fd3110d3≥ d5c65159f2895379e11ca13f62feabe93278985d and < b0974ed82e6ad5ff246fd90a5b14f3e7be4f2924≥ d5c65159f2895379e11ca13f62feabe93278985d and < f50ba7e7b607f2d00618799312e7fdb76a1ff48e≥ d5c65159f2895379e11ca13f62feabe93278985d and < f5d77d0d41ea7a204d47288d0cf0404a52b5890e≥ d5c65159f2895379e11ca13f62feabe93278985d and < 6d6cb27fe146061f2512e904618f5e005bb7bb6a≥ d5c65159f2895379e11ca13f62feabe93278985d and < 31e98e277ae47f56632e4d663b1d4fd12ba33ea8version 5.6 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Linux | Linux Kernel | ≥ 5.6 and < 5.10.239≥ 5.11 and < 5.15.186≥ 5.16 and < 6.1.142≥ 6.2 and < 6.6.94≥ 6.7 and < 6.12.34≥ 6.13 and < 6.15.3 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.8 | CVSS 3.1 | High | 2.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
| 5.5 | CVSS 3.1 | Medium | 1.8 | 3.6 | nvd@nist.gov via NIST National Vulnerability Database |
| 5.5 | CVSS 3.1 | Medium | — | — | GitHub, Inc. via GitHub Security Advisories |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · linux/linux kernel, debian/debian linux
- CVSS changed · 5.5
- Source status changed · → Modified
- Record created in this database
- 2025
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
11 on the record
- git.kernel.org/stable/c/6c139015b597e570dd5962934e9f9a2f4cc8ef48
- git.kernel.org/stable/c/f50ba7e7b607f2d00618799312e7fdb76a1ff48e
- git.kernel.org/stable/c/6d6cb27fe146061f2512e904618f5e005bb7bb6a
- git.kernel.org/stable/c/f5d77d0d41ea7a204d47288d0cf0404a52b5890e
- git.kernel.org/stable/c/f9507cf2dd0e1ed5028c0e8240da6fe5fd3110d3
- git.kernel.org/stable/c/b0974ed82e6ad5ff246fd90a5b14f3e7be4f2924
- git.kernel.org/stable/c/31e98e277ae47f56632e4d663b1d4fd12ba33ea8
- nvd.nist.gov/vuln/detail/CVE-2025-38293
- lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- github.com/advisories/GHSA-x3qq-xqjx-f5p7
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 19h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 19h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-38293 is "wifi: ath11k: fix node corruption in ar->arvifs list", rated Medium. It affects Debian Linux (Debian); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 5.5 describes technical severity. EPSS 0.34% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.