CVE-2026-46187

wifi: rsi: fix kthread lifetime race between self-exit and external-stop

MEDIUM
4.7
CVSS Score
Published: May 28, 2026 at 09:36 AM UTC
Updated: October 15, 2026 at 02:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM4.7
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: wifi: rsi: fix kthread lifetime race between self-exit and external-stop RSI driver use both self-exit(kthread_complete_and_exit) and external-stop (kthread_stop) when killing a kthread. Generally, kthread_stop() is called first, and in this case, no particular issues occur. However, in rare instances where kthread_complete_and_exit() is called first and then kthread_stop() is called, a UAF occurs because the kthread object, which has already exited and been freed, is accessed again. Therefore, to prevent this with minimal modification, you must remove kthread_stop() and change the code to wait until the self-exit operation is completed.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.18.139 ≤ v < 3.194.14.113 ≤ v < 4.154.19.36 ≤ v < 5.10.2584.4.179 ≤ v < 4.54.9.170 ≤ v < 4.105.11 ≤ v < 5.15.2095.16 ≤ v < 6.1.1756.13 ≤ v < 6.18.306.19 ≤ v < 7.0.76.2 ≤ v < 6.6.1406.7 ≤ v < 6.12.883.18.1394.14.1134.19.364.4.1794.9.1704c62764d0fc21a34ffc44eec1210038c3a2e44737.17.1 rc17.1 rc2ad78e2e057ab8d914a2b5e3e6acf29c3c8a428a3c8ed05b1d8520f40395916438da9b38ce937a896d8f70ad66032363e3edceee81a7be2aaccb2d7f5de1fd69b6541ff61177114d63af7ea719c426cf0ec759c0015fb7d4f5c7cb5711d2c8905724c7983
Vendor states this is fixed in 16d9f674c619838bdeae42abc0929c9c5477ea1f (fixed)
Vendor states this is fixed in 4ac3095da22fc50e51ec10c3b8323c21ab3e441a (fixed)
Vendor states this is fixed in 4f4c9b13c485abd0a2d2c97f9db339d1dd8e147f (fixed)
Vendor states this is fixed in 4f697813162d5f9151726a6d2bee82bffe4b0256 (fixed)
Vendor states this is fixed in 4f9a4ae8d2c198f01611ea376034c326ef43ab56 (fixed)
Vendor states this is fixed in 95fcb436586dc3c2983537d557ac05bbc6a027f3 (fixed)
Vendor states this is fixed in 9dfe8a4458a063c6433526bc59112a169eee1aa3 (fixed)
Vendor states this is fixed in db57a1aa54ff68669781976e4edb045e09e2b65b (fixed)
Affected range stops below 3.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.15, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 4.20 (unaffected)
Affected range stops below 4.5, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.258 (unaffected)
Vendor states this is fixed in 5.15.209 (unaffected)
Vendor states this is fixed in 6.1.175 (unaffected)
Vendor states this is fixed in 6.12.88 (unaffected)
Vendor states this is fixed in 6.18.30 (unaffected)
Vendor states this is fixed in 6.6.140 (unaffected)
Vendor states this is fixed in 7.0.7 (unaffected)
Vendor states this is fixed in 7.1 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
HIGH
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-362

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card