CVE-2026-68198

HIGHCVSS 8.8/10EPSS 0.27%

Last modified

CVE-2026-68198 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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.. EPSS estimates a 0.27% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.27%

19.1th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= bdcd81707973cf8aa9305337166f8ee842a050d4, < a1bac650b2d6b1baab1f3e78e2e007a6e2948dde; >= bdcd81707973cf8aa9305337166f8ee842a050d4, < 2132a6db05846dd2318857d00e0c1291f9e41b29; >= bdcd81707973cf8aa9305337166f8ee842a050d4, < 17ff29cd8dbc977c97788a5f7c011ec807b58242; >= bdcd81707973cf8aa9305337166f8ee842a050d4, < 64af6534a085f49d6ed33338a19ab9cf0d0523c9; >= bdcd81707973cf8aa9305337166f8ee842a050d4, < b5d618fd61b9069b4c0a6b487022dd3117ad5acc; >= bdcd81707973cf8aa9305337166f8ee842a050d4, < 18965470d41e69d3fc10eb62afae29d10f4cdfd1; >= bdcd81707973cf8aa9305337166f8ee842a050d4, < a3313111b5d9046af60b370c93eec105b27380c1; >= bdcd81707973cf8aa9305337166f8ee842a050d4, < ba7debb4dd6427386862220e8335a53a4bfc235d
LinuxLinux3.2

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-68198?
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.
How severe is CVE-2026-68198?
CVE-2026-68198 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 0.27% probability of exploitation in the next 30 days.
How do I fix CVE-2026-68198?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-68198?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST