CVE-2022-49503·Kernel vulnerability
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()'
- Severity
- high
- Software
- Kernel
- Fixed in
- 5.18.3
- Published
- 2025-02-26
Affected versions
From: 5.18
Until: 5.18.3
Fixed in: 5.18.3
How to fix this CVE
Update your Linux kernel to version 5.18.3 or later to address a bounds-checking vulnerability in the ath9k_htc wireless driver that could allow out-of-bounds memory access. This fix validates the rxstatus->rs_keyix field before it is used in bitmap operations, preventing potential privilege escalation or denial of service from local attackers.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your kernel version by running 'uname -r' and verify if it falls between 5.18 and 5.18.2
- Step 2: Confirm if ath9k_htc driver is loaded by running 'lsmod | grep ath9k_htc' or 'ethtool -i <interface> | grep driver'
- Step 3: Search system logs for wireless driver errors with 'grep -i "ath9k\|keyix" /var/log/kern.log' or 'journalctl -u kernel | grep -i ath9k'
- Step 4: After patching, verify the kernel update with 'uname -r' and confirm it shows 5.18.3 or higher
FAQ
What is CVE-2022-49503?
This vulnerability is an out-of-bounds memory access flaw in the ath9k_htc Wi-Fi driver that fails to validate the rxstatus->rs_keyix field before using it in bitmap operations, potentially allowing local privilege escalation or kernel crashes.
Is CVE-2022-49503 being actively exploited?
No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available, though it remains a local privilege escalation risk.
What versions of Kernel are affected by CVE-2022-49503?
Linux kernel versions 5.18 through 5.18.2 are affected; version 5.18.3 and later contain the fix.
How do I check if my server is vulnerable to CVE-2022-49503?
Run 'uname -r' to check your kernel version, and 'lsmod | grep ath9k_htc' to verify if the vulnerable driver is loaded. If your kernel is between 5.18 and 5.18.2 and the driver is present, you are vulnerable.
Does Defensia detect CVE-2022-49503?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2022-49503 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/0bcb528402cd5e1a6e1833e956fd58a12d509e8e
- https://git.kernel.org/stable/c/2326d398ccd41ba6d93b8346532dfa432ab00fee
- https://git.kernel.org/stable/c/2dc509305cf956381532792cb8dceef2b1504765
- https://git.kernel.org/stable/c/3dad3fed5672828c7fb0465cb66a3d9a70952fa6
- https://git.kernel.org/stable/c/461e4c1f199076275f16bf6f3d3e42c6b6c79f33
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2022-49503. Free for 1 server.
Get started free