Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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()'

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 21 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2022-49503, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
EPSS (exploitation in 30 days)
0.28% · top 79% of all CVEs (12 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected 4ed1a8d4a25711f780b96920fff2bb531229e322 – < 0bcb528402cd5e1a6e1833e956fd58a12d509e8e
    • affected 4ed1a8d4a25711f780b96920fff2bb531229e322 – < a048e0c3caa852397b7b50d4c82a0415c05f7ac3
    • affected 4ed1a8d4a25711f780b96920fff2bb531229e322 – < 4bdcf32c965c27f55ccc4ee71c1927131115b0bb
    • affected 4ed1a8d4a25711f780b96920fff2bb531229e322 – < 2326d398ccd41ba6d93b8346532dfa432ab00fee
    • affected 4ed1a8d4a25711f780b96920fff2bb531229e322 – < 461e4c1f199076275f16bf6f3d3e42c6b6c79f33
    • affected 4ed1a8d4a25711f780b96920fff2bb531229e322 – < 7f6defe0fabc79f29603c6fa3c80e4fe0456a3e9
    • affected 4ed1a8d4a25711f780b96920fff2bb531229e322 – < eda518db7db16c360bc84379d90675650daa3048
    • affected 4ed1a8d4a25711f780b96920fff2bb531229e322 – < 3dad3fed5672828c7fb0465cb66a3d9a70952fa6
    • affected 4ed1a8d4a25711f780b96920fff2bb531229e322 – < 2dc509305cf956381532792cb8dceef2b1504765
  • Linux · Linux

    • affected 3.15
    • unaffected < 3.15
    • unaffected 4.9.318 – ≤ 4.9.*
    • unaffected 4.14.283 – ≤ 4.14.*
    • unaffected 4.19.247 – ≤ 4.19.*
    • unaffected 5.4.198 – ≤ 5.4.*
    • unaffected 5.10.121 – ≤ 5.10.*
    • unaffected 5.15.46 – ≤ 5.15.*
    • unaffected 5.17.14 – ≤ 5.17.*
    • unaffected 5.18.3 – ≤ 5.18.*
    • unaffected 5.19 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-49503 badge
[![CVE-2022-49503](https://cveledger.app/badge/CVE-2022-49503.svg)](https://cveledger.app/cve/CVE-2022-49503)

Record last updated .