CVE-2026-68198 — wifi: ath6kl: fix use-after-free in aggr_reset_state()
In the Linux kernel, the following vulnerability has been resolved: wifi: ath6kl: fix use-after-free in aggr_reset_state() The aggr_reset_state() function uses timer_delete() (non-synchronous) for the aggregation timer before proceeding to delete TID state and before the structure is freed by callers like aggr_module_destroy(). If the timer callback (aggr_timeout) is executing when aggr_reset_state() is called, the callback will continue to access aggr_conn fields like rx_tid[] and stat[] which may be freed immediately after by kfree(aggr_info->aggr_conn) in aggr_module_destroy(). Additionally, the timer callback can re-arm itself via mod_timer() while aggr_reset_state() is running, creating a more complex race condition. Use timer_delete_sync() instead to ensure any running timer callback has completed before returning.
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
- Technical severity (high)+6
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.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
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 (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- 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 |
|---|---|---|---|---|
| Linux | Linux |
≥ bdcd81707973cf8aa9305337166f8ee842a050d4 and < a1bac650b2d6b1baab1f3e78e2e007a6e2948dde≥ bdcd81707973cf8aa9305337166f8ee842a050d4 and < 2132a6db05846dd2318857d00e0c1291f9e41b29≥ bdcd81707973cf8aa9305337166f8ee842a050d4 and < 17ff29cd8dbc977c97788a5f7c011ec807b58242≥ bdcd81707973cf8aa9305337166f8ee842a050d4 and < 64af6534a085f49d6ed33338a19ab9cf0d0523c9≥ bdcd81707973cf8aa9305337166f8ee842a050d4 and < b5d618fd61b9069b4c0a6b487022dd3117ad5acc≥ bdcd81707973cf8aa9305337166f8ee842a050d4 and < 18965470d41e69d3fc10eb62afae29d10f4cdfd1≥ bdcd81707973cf8aa9305337166f8ee842a050d4 and < a3313111b5d9046af60b370c93eec105b27380c1≥ bdcd81707973cf8aa9305337166f8ee842a050d4 and < ba7debb4dd6427386862220e8335a53a4bfc235d and 1 moreversion 3.2 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
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 |
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 8.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/ba7debb4dd6427386862220e8335a53a4bfc235d
- git.kernel.org/stable/c/a3313111b5d9046af60b370c93eec105b27380c1
- git.kernel.org/stable/c/17ff29cd8dbc977c97788a5f7c011ec807b58242
- git.kernel.org/stable/c/a1bac650b2d6b1baab1f3e78e2e007a6e2948dde
- git.kernel.org/stable/c/2132a6db05846dd2318857d00e0c1291f9e41b29
- git.kernel.org/stable/c/64af6534a085f49d6ed33338a19ab9cf0d0523c9
- git.kernel.org/stable/c/18965470d41e69d3fc10eb62afae29d10f4cdfd1
- git.kernel.org/stable/c/b5d618fd61b9069b4c0a6b487022dd3117ad5acc
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 14h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 14h
- 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 FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- 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-2026-68198 is "wifi: ath6kl: fix use-after-free in aggr_reset_state()", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. 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.