# CVE-2026-68198: wifi: ath6kl: fix use-after-free in aggr_reset_state()

> A use-after-free vulnerability in the Linux kernel's ath6kl Wi-Fi driver allows attackers to potentially execute code or escalate privileges via a race condition.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-94998, BELL-CVE-2026-68198, DEBIAN-CVE-2026-68198, GHSA-mrq7-mrhj-vm2g, UBUNTU-CVE-2026-68198

## What is CVE-2026-68198?

CVE-2026-68198 is a high-severity use after free vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-68198?


## How do I fix CVE-2026-68198?

Apply the vendor's patch.

## Is CVE-2026-68198 being exploited?

There is no known exploitation of CVE-2026-68198 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68198 and fix it if it is affected.

What it is: CVE-2026-68198 is a high-severity use after free vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68198 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68198/ (Markdown: https://insights.sbomify.com/CVE-2026-68198/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68198
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68198
- OSV: https://osv.dev/vulnerability/CVE-2026-68198

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68198/
Summaries are generated and may contain mistakes; the official description above is the record.