LiveActive security incident?Get immediate response
CVE Record

CVE-2024-46827: wifi: ath12k: fix firmware crash due to invalid peer nss

In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix firmware crash due to invalid peer nss Currently, if the access point receives an association request containing an Extended HE Capabilities Information Element with an invalid MCS-NSS, it triggers a firmware crash. This issue arises when EHT-PHY capabilities shows support for a bandwidth and MCS-NSS set for that particular bandwidth is filled by zeros and due to this, driver obtains peer_nss as 0 and sending this value to firmware causes crash. Address this issue by implementing a validation step for the peer_nss value before passing it to the firmware. If the value is greater than zero, proceed with forwarding it to the firmware. However, if the value is invalid, reject the association request to prevent potential firmware crashes. Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.0.1-00029-QCAHKSWPL_SILICONZ-1

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue can crash Wi-Fi firmware when an access point receives a malformed association request. The likely business impact is wireless service disruption, not data theft, based on the provided sources. Exposure depends on running affected Linux kernels with the ath12k Wi-Fi driver in access-point scenarios.

Executive priority

Treat as a moderate availability risk for Linux-based wireless infrastructure. Prioritize remediation where affected systems provide production Wi-Fi, guest access, operational connectivity, or managed wireless service delivery.

Technical view

The ath12k driver could pass peer_nss value 0 to firmware when parsing invalid EHT-PHY MCS-NSS capability data in an association request. The fix validates peer_nss before firmware handoff and rejects invalid association requests, preventing the firmware crash.

Likely exposure

Most relevant exposure is Linux systems using ath12k Wi-Fi in access point mode. The source names Linux kernel versions and notes testing on QCN9274 hardware, but it does not fully enumerate all impacted hardware or distributions.

Exploitation context

The bundle does not show CISA KEV listing, public exploitation, or exploit maturity. Triggering requires association-request reachability to an affected wireless access point, making this a proximity-based denial-of-service concern from the available evidence.

Researcher notes

Evidence supports a driver-to-firmware crash path caused by invalid peer NSS handling. The bundle lacks CVSS, CWE, exploit status, and complete distribution mapping, so validation should focus on kernel lineage, ath12k deployment, and vendor backports.

Mitigation direction

  • Upgrade to a Linux kernel build containing the referenced stable ath12k fix.
  • Check Linux distribution advisories for backported fixes matching CVE-2024-46827.
  • Prioritize Linux wireless access points using ath12k for remediation review.
  • Where patching is delayed, reduce reliance on affected AP-mode systems.
  • Monitor for unexpected ath12k firmware crashes and wireless service interruptions.

Validation and detection

  • Inventory Linux kernels that use the ath12k driver.
  • Identify systems operating ath12k Wi-Fi in access point mode.
  • Compare installed kernels against vendor changelogs and referenced stable commits.
  • Review kernel logs for ath12k firmware crash messages.
  • Confirm patched behavior rejects invalid association requests in authorized testing.
Prepared
Confidence
medium
Sources
5

Public sources used

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-46827 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

0CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd889913205cf7ebda905b1e62c5867ed4e39f6c2, d889913205cf7ebda905b1e62c5867ed4e39f6c2, d889913205cf7ebda905b1e62c5867ed4e39f6c2unaffected
LinuxLinux6.3, 0, 6.6.51, 6.10.10, 6.11affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.