LiveActive security incident?Get immediate response
CVE Record

CVE-2022-49503: ath9k_htc: fix potential out of bounds access with invalid rxstatus->rs_keyix

In the Linux kernel, the following vulnerability has been resolved: ath9k_htc: fix potential out of bounds access with invalid rxstatus->rs_keyix The "rxstatus->rs_keyix" eventually gets passed to test_bit() so we need to ensure that it is within the bitmap. drivers/net/wireless/ath/ath9k/common.c:46 ath9k_cmn_rx_accept() error: passing untrusted data 'rx_stats->rs_keyix' to 'test_bit()'

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

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the ath9k_htc wireless driver. Invalid receive status data could lead to an out-of-bounds bitmap access. The public record does not state practical impact, exploitability, or attacker requirements, so business urgency depends on whether affected kernels and this driver are present.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency based on current evidence. Escalate patching for Linux devices using ath9k_htc wireless networking, especially unmanaged endpoints or systems operating near untrusted wireless environments.

Technical view

The flaw is in ath9k_cmn_rx_accept(), where untrusted rx_stats->rs_keyix can reach test_bit() without ensuring the index fits the bitmap. The kernel fix validates rs_keyix before use. No CVSS, CWE, impact statement, or exploit details are provided in the source bundle.

Likely exposure

Likely limited to Linux systems running affected kernel versions with the ath9k_htc Atheros wireless driver path available. The source lists Linux kernel versions and stable commits but does not describe distribution packages, configurations, hardware dependency, or reachable attack surface.

Exploitation context

CISA KEV is false, and the provided sources do not report active exploitation. The record describes a potential out-of-bounds access from invalid receive status data, but does not document whether exploitation is local, adjacent, remote, or only a stability issue.

Researcher notes

The source bundle is sparse: no CVSS, CWE, proof of exploitability, or distribution mapping. Focus validation on driver reachability and kernel provenance. Avoid assuming broader Wi-Fi stack exposure beyond the ath9k_htc/common.c path named in the record.

Mitigation direction

  • Update to a kernel build containing the referenced stable fixes.
  • Check your Linux distribution advisory for packaged fixed kernel versions.
  • Prioritize systems using ath9k_htc wireless hardware or modules.
  • Temporarily disable unused ath9k_htc hardware or modules if patching is delayed.

Validation and detection

  • Inventory kernel versions against the affected and fixed versions in the CVE record.
  • Check whether ath9k_htc is loaded or used on Linux endpoints.
  • Confirm vendor kernel changelogs include the referenced stable commits.
  • Record exceptions where the driver is absent or wireless hardware is not deployed.
Prepared
Confidence
medium
Sources
11

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-2022-49503 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
0ADP providers
10Source links

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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux4ed1a8d4a25711f780b96920fff2bb531229e322, 4ed1a8d4a25711f780b96920fff2bb531229e322, 4ed1a8d4a25711f780b96920fff2bb531229e322, 4ed1a8d4a25711f780b96920fff2bb531229e322, 4ed1a8d4a25711f780b96920fff2bb531229e322, 4ed1a8d4a25711f780b96920fff2bb531229e322, 4ed1a8d4a25711f780b96920fff2bb531229e322, 4ed1a8d4a25711f780b96920fff2bb531229e322, 4ed1a8d4a25711f780b96920fff2bb531229e322unaffected
LinuxLinux3.15, 0, 4.9.318, 4.14.283, 4.19.247, 5.4.198, 5.10.121, 5.15.46, 5.17.14, 5.18.3, 5.19affected
Weakness

CWE details

No CWE listed

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