Linux Kernel up to 7.2-rc4 ath6kl aggr_reset_state use after free

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$5k-$25k0.82

Summaryinfo

A vulnerability classified as very critical has been found in Linux Kernel up to 6.6.150/6.12.102/6.18.41/7.1.5/7.2-rc4. The affected element is the function aggr_reset_state of the component ath6kl. This manipulation causes use after free. This vulnerability is tracked as CVE-2026-68198. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.6.150/6.12.102/6.18.41/7.1.5/7.2-rc4. It has been declared as very critical. Affected by this vulnerability is the function aggr_reset_state of the component ath6kl. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. This vulnerability is known as CVE-2026-68198 since 07/30/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/10/2026).

Upgrading to version 6.6.151, 6.12.103, 6.18.42, 7.1.6 or 7.2-rc5 eliminates this vulnerability. Applying the patch 64af6534a085f49d6ed33338a19ab9cf0d0523c9/b5d618fd61b9069b4c0a6b487022dd3117ad5acc/18965470d41e69d3fc10eb62afae29d10f4cdfd1/a3313111b5d9046af60b370c93eec105b27380c1/ba7debb4dd6427386862220e8335a53a4bfc235d is able to eliminate this problem.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Use after free
CWE: CWE-416 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.6.151/6.12.103/6.18.42/7.1.6/7.2-rc5
Patch: 64af6534a085f49d6ed33338a19ab9cf0d0523c9/b5d618fd61b9069b4c0a6b487022dd3117ad5acc/18965470d41e69d3fc10eb62afae29d10f4cdfd1/a3313111b5d9046af60b370c93eec105b27380c1/ba7debb4dd6427386862220e8335a53a4bfc235d

Timelineinfo

07/30/2026 CVE reserved
08/10/2026 +11 days Advisory disclosed
08/10/2026 +0 days VulDB entry created
08/10/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-68198 (🔒)
GCVE (CVE): GCVE-0-2026-68198
GCVE (VulDB): GCVE-100-387547

Entryinfo

Created: 08/10/2026 16:00
Changes: 08/10/2026 16:00 (59)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!