linux-cve-announce - CVE-2022-50297: wifi: ath9k: verify the expected usb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025091557-CVE-2022-50297-974e@gregkh>
Date: Mon, 15 Sep 2025 16:45:59 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50297: wifi: ath9k: verify the expected usb_endpoints are present

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

wifi: ath9k: verify the expected usb_endpoints are present

The bug arises when a USB device claims to be an ATH9K but doesn't
have the expected endpoints. (In this case there was an interrupt
endpoint where the driver expected a bulk endpoint.) The kernel
needs to be able to handle such devices without getting an internal error.

usb 1-1: BOGUS urb xfer, pipe 3 != type 1
WARNING: CPU: 3 PID: 500 at drivers/usb/core/urb.c:493 usb_submit_urb+0xce2/0x1430 drivers/usb/core/urb.c:493
Modules linked in:
CPU: 3 PID: 500 Comm: kworker/3:2 Not tainted 5.10.135-syzkaller #0
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
Workqueue: events request_firmware_work_func
RIP: 0010:usb_submit_urb+0xce2/0x1430 drivers/usb/core/urb.c:493
Call Trace:
 ath9k_hif_usb_alloc_rx_urbs drivers/net/wireless/ath/ath9k/hif_usb.c:908 [inline]
 ath9k_hif_usb_alloc_urbs+0x75e/0x1010 drivers/net/wireless/ath/ath9k/hif_usb.c:1019
 ath9k_hif_usb_dev_init drivers/net/wireless/ath/ath9k/hif_usb.c:1109 [inline]
 ath9k_hif_usb_firmware_cb+0x142/0x530 drivers/net/wireless/ath/ath9k/hif_usb.c:1242
 request_firmware_work_func+0x12e/0x240 drivers/base/firmware_loader/main.c:1097
 process_one_work+0x9af/0x1600 kernel/workqueue.c:2279
 worker_thread+0x61d/0x12f0 kernel/workqueue.c:2425
 kthread+0x3b4/0x4a0 kernel/kthread.c:313
 ret_from_fork+0x22/0x30 arch/x86/entry/entry_64.S:299

Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

The Linux kernel CVE team has assigned CVE-2022-50297 to this issue.


Affected and fixed versions
===========================

	Fixed in 4.9.337 with commit 932f0a5e829fb0b823f96d7fa9a0f4fc96660b77
	Fixed in 4.14.303 with commit d008a202a0528a058bac658e657c010ce8534f4a
	Fixed in 4.19.270 with commit d64436af0bc3c9e579be761d7684f228fb95f3bb
	Fixed in 5.4.229 with commit ca57748593ddd8e46d033fbaeb9d01ec533a6bfe
	Fixed in 5.10.163 with commit 1824ccabee5445347b83642e4087cc2eca070343
	Fixed in 5.15.86 with commit c319196a0e34ed2e66d6f876f58d8d446335c2a7
	Fixed in 6.0.16 with commit 2d2eccf52ea0215c8d386b62af0b5fd4fc122bd5
	Fixed in 6.1.2 with commit 0b7e6d681e00a96cde2b32a15ffa70e1be2e3209
	Fixed in 6.2 with commit 16ef02bad239f11f322df8425d302be62f0443ce

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2022-50297
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/net/wireless/ath/ath9k/hif_usb.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/932f0a5e829fb0b823f96d7fa9a0f4fc96660b77
	https://git.kernel.org/stable/c/d008a202a0528a058bac658e657c010ce8534f4a
	https://git.kernel.org/stable/c/d64436af0bc3c9e579be761d7684f228fb95f3bb
	https://git.kernel.org/stable/c/ca57748593ddd8e46d033fbaeb9d01ec533a6bfe
	https://git.kernel.org/stable/c/1824ccabee5445347b83642e4087cc2eca070343
	https://git.kernel.org/stable/c/c319196a0e34ed2e66d6f876f58d8d446335c2a7
	https://git.kernel.org/stable/c/2d2eccf52ea0215c8d386b62af0b5fd4fc122bd5
	https://git.kernel.org/stable/c/0b7e6d681e00a96cde2b32a15ffa70e1be2e3209
	https://git.kernel.org/stable/c/16ef02bad239f11f322df8425d302be62f0443ce