linux-cve-announce - CVE-2025-38604: wifi: rtl818x: Kill URBs before clearing tx status queue

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <2025081921-CVE-2025-38604-fd5d@gregkh>
Date: Tue, 19 Aug 2025 19:18:50 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-38604: wifi: rtl818x: Kill URBs before clearing tx status queue

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

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

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

wifi: rtl818x: Kill URBs before clearing tx status queue

In rtl8187_stop() move the call of usb_kill_anchored_urbs() before clearing
b_tx_status.queue. This change prevents callbacks from using already freed
skb due to anchor was not killed before freeing such skb.

 BUG: kernel NULL pointer dereference, address: 0000000000000080
 #PF: supervisor read access in kernel mode
 #PF: error_code(0x0000) - not-present page
 PGD 0 P4D 0
 Oops: Oops: 0000 [#1] SMP NOPTI
 CPU: 7 UID: 0 PID: 0 Comm: swapper/7 Not tainted 6.15.0 #8 PREEMPT(voluntary)
 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015
 RIP: 0010:ieee80211_tx_status_irqsafe+0x21/0xc0 [mac80211]
 Call Trace:
  <IRQ>
  rtl8187_tx_cb+0x116/0x150 [rtl8187]
  __usb_hcd_giveback_urb+0x9d/0x120
  usb_giveback_urb_bh+0xbb/0x140
  process_one_work+0x19b/0x3c0
  bh_worker+0x1a7/0x210
  tasklet_action+0x10/0x30
  handle_softirqs+0xf0/0x340
  __irq_exit_rcu+0xcd/0xf0
  common_interrupt+0x85/0xa0
  </IRQ>

Tested on RTL8187BvE device.

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

The Linux kernel CVE team has assigned CVE-2025-38604 to this issue.


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

	Issue introduced in 2.6.29 with commit c1db52b9d27ee6e15a7136e67e4a21dc916cd07f and fixed in 6.1.148 with commit 8c767727f331fb9455b0f81daad832b5925688cb
	Issue introduced in 2.6.29 with commit c1db52b9d27ee6e15a7136e67e4a21dc916cd07f and fixed in 6.6.102 with commit 14ca6952691fa8cc91e7644512e6ff24a595283f
	Issue introduced in 2.6.29 with commit c1db52b9d27ee6e15a7136e67e4a21dc916cd07f and fixed in 6.12.42 with commit 7858a95566f4ebf59524666683d2dcdba3fca968
	Issue introduced in 2.6.29 with commit c1db52b9d27ee6e15a7136e67e4a21dc916cd07f and fixed in 6.15.10 with commit c51a45ad9070a6d296174fcbe5c466352836c12b
	Issue introduced in 2.6.29 with commit c1db52b9d27ee6e15a7136e67e4a21dc916cd07f and fixed in 6.16.1 with commit 81cfe34d0630de4e23ae804dcc08fb6f861dc37d
	Issue introduced in 2.6.29 with commit c1db52b9d27ee6e15a7136e67e4a21dc916cd07f and fixed in 6.17-rc1 with commit 16d8fd74dbfca0ea58645cd2fca13be10cae3cdd

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-2025-38604
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/realtek/rtl818x/rtl8187/dev.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/8c767727f331fb9455b0f81daad832b5925688cb
	https://git.kernel.org/stable/c/14ca6952691fa8cc91e7644512e6ff24a595283f
	https://git.kernel.org/stable/c/7858a95566f4ebf59524666683d2dcdba3fca968
	https://git.kernel.org/stable/c/c51a45ad9070a6d296174fcbe5c466352836c12b
	https://git.kernel.org/stable/c/81cfe34d0630de4e23ae804dcc08fb6f861dc37d
	https://git.kernel.org/stable/c/16d8fd74dbfca0ea58645cd2fca13be10cae3cdd