CVE-2024-43879: wifi: cfg80211: handle 2x996 RU allocation in cfg80211_calculate_bitrate_he()
In the Linux kernel, the following vulnerability has been resolved:
wifi: cfg80211: handle 2x996 RU allocation in cfg80211_calculate_bitrate_he()
Currently NL80211_RATE_INFO_HE_RU_ALLOC_2x996 is not handled in
cfg80211_calculate_bitrate_he(), leading to below warning:
kernel: invalid HE MCS: bw:6, ru:6
kernel: WARNING: CPU: 0 PID: 2312 at net/wireless/util.c:1501 cfg80211_calculate_bitrate_he+0x22b/0x270 [cfg80211]
Fix it by handling 2x996 RU allocation in the same way as 160 MHz bandwidth.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel Wi-Fi defect in cfg80211 bitrate calculation for a specific Wi-Fi 6 RU allocation. The reported impact is a kernel warning, not a clearly documented compromise path. Treat it as a routine kernel maintenance issue unless affected systems are safety-critical, embedded, or exposed to unusual wireless traffic conditions.
Executive priority
Schedule normal patch-cycle remediation. Escalate only where Linux Wi-Fi is used in operational technology, appliances, or managed endpoints with strict reliability requirements. Current sources do not justify emergency response.
Technical view
cfg80211_calculate_bitrate_he() did not handle NL80211_RATE_INFO_HE_RU_ALLOC_2x996, producing an invalid HE MCS warning. The kernel fix handles 2x996 RU allocation like 160 MHz bandwidth. Sources do not provide CVSS, CWE, a crash-to-compromise chain, or confirmed exploitation.
Likely exposure
Exposure is most plausible on Linux systems using affected kernel versions with Wi-Fi/cfg80211 HE support. Servers without Wi-Fi hardware or disabled wireless stacks are less likely to be practically exposed. Distribution and vendor kernel backports may change version-based conclusions.
Exploitation context
The bundle does not show CISA KEV listing or any cited active exploitation. Public evidence describes a resolved kernel warning condition. No source here proves remote code execution, privilege escalation, or a weaponized exploit.
Researcher notes
The source record is thin: no CVSS, CWE, exploit status, or full impact analysis. Focus validation on affected kernel branches, downstream backports, wireless capability, and whether the warning can affect reliability in the local deployment context.
Mitigation direction
Update to vendor-supported kernels containing the stable cfg80211 fix.
Apply Debian LTS or device-vendor kernel updates where applicable.
Check Siemens advisories for affected industrial product guidance.
Prioritize embedded or wireless-enabled Linux assets over non-Wi-Fi servers.
Avoid direct wrangler or deployment assumptions; follow normal OS patch governance.
Validation and detection
Inventory Linux kernel versions on wireless-enabled assets.
Confirm whether cfg80211 and Wi-Fi 6 HE functionality are present.
Compare installed kernels against vendor fixed packages or stable commits.
Review kernel logs for invalid HE MCS warnings.
Verify Debian or vendor advisory status for managed distributions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-43879 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.