SEPTEMBER 20, 2026
Live Feed
Back to database
Case File

CVE-2026-80641

UNKNOWN · CVSS N/A EPSS 0.15%

Source: NVD + CISA KEV + EPSS · Published 2026-08-28 · Last synced 2026-09-20

CyberRota Analysis

AI-Generated

The vulnerability affects the Linux kernel's wlcore driver, specifically impacting devices using older firmware versions that fail to properly manage the Integrated Group Temporal Key (IGTK) ciphers, leading to repeated key-setting errors and potential wireless connectivity issues. This can result in degraded performance or complete failure to connect to Wi-Fi networks, particularly for devices utilizing the wl12xx and wl128x chipsets. Organizations relying on these wireless chipsets should prioritize addressing this issue to maintain network stability and security.

CVE
CVE-2026-80641
Severity
UNKNOWN
CVSS
N/A
EPSS
0.15%
Linux

Original NVD Description

In the Linux kernel, the following vulnerability has been resolved: wifi: wlcore: enable the right set of ciphers The firmware version number check for IGTK introduced in commit c34dbc5900b0 ("wifi: wlcore: Add support for IGTK key") lets the amount of ciphers decrease on every boot of a too old firmware and that is practically happening. It also does not take into account other chips than the wl18xx. On some wl128x, the following can be observed when connecting via nm to a common ap: [ 484.113311] wlcore: WARNING could not set keys [ 484.117828] wlcore: ERROR Could not add or replace key [ 484.123016] wlan0: failed to set key (5, ff:ff:ff:ff:ff:ff) to hardware (-5) [ 484.123046] wlcore: Hardware recovery in progress. FW ver: Rev 7.3.10.0.142 [ 484.139923] wlcore: pc: 0x0, hint_sts: 0x00000048 count: 1 [ 484.145721] wlcore: down [ 484.148986] ieee80211 phy0: Hardware restart was requested [ 484.610473] wlcore: firmware booted (Rev 7.3.10.0.142) [ 484.633758] wlcore: Association completed. [ 484.690490] wlcore: ERROR command execute failure 14 [ 484.690490] ------------[ cut here ]------------ [ 484.700195] WARNING: drivers/net/wireless/ti/wlcore/main.c:872 at wl12xx_queue_recovery_work+0x64/0x74 [wlcore], CPU#0: kworker/0:0/892 This repeats endlessly. Always disable IGTK on wl12xx and fix the decrementing mess.