CVE Intelligence
Medium Logic error

CVE-2026-46187 — wifi: rsi: fix kthread lifetime race between self-exit and external-stop

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.

Published May 28, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.1% (30-day exploitation probability)+0
  • Technical severity (medium)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.11%
ahead of 1% of scored CVEs · Oct 14, 2026
Affects
Linux
Linux and 1 more
CVSS base
4.7
Medium · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)
  • Documented patch — git.kernel.org (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux, Linux Linux Kernel).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Search available logs for exploit probes matching the vulnerability class (logic error), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux ≥ 4c62764d0fc21a34ffc44eec1210038c3a2e4473 and < 95fcb436586dc3c2983537d557ac05bbc6a027f3version 4.20≥ 4.19.36 and < 4.20≥ 4.14.113 and < 4.15≥ 4.9.170 and < 4.10≥ 4.4.179 and < 4.5≥ 3.18.139 and < 3.19version de1fd69b6541ff61177114d63af7ea719c426cf0
and 11 more version ad78e2e057ab8d914a2b5e3e6acf29c3c8a428a3version c8ed05b1d8520f40395916438da9b38ce937a896version ec759c0015fb7d4f5c7cb5711d2c8905724c7983version d8f70ad66032363e3edceee81a7be2aaccb2d7f5≥ 4c62764d0fc21a34ffc44eec1210038c3a2e4473 and < db57a1aa54ff68669781976e4edb045e09e2b65b≥ 4c62764d0fc21a34ffc44eec1210038c3a2e4473 and < 4f4c9b13c485abd0a2d2c97f9db339d1dd8e147f≥ 4c62764d0fc21a34ffc44eec1210038c3a2e4473 and < 4f9a4ae8d2c198f01611ea376034c326ef43ab56≥ 4c62764d0fc21a34ffc44eec1210038c3a2e4473 and < 16d9f674c619838bdeae42abc0929c9c5477ea1f≥ 4c62764d0fc21a34ffc44eec1210038c3a2e4473 and < 4f697813162d5f9151726a6d2bee82bffe4b0256≥ 4c62764d0fc21a34ffc44eec1210038c3a2e4473 and < 9dfe8a4458a063c6433526bc59112a169eee1aa3≥ 4c62764d0fc21a34ffc44eec1210038c3a2e4473 and < 4ac3095da22fc50e51ec10c3b8323c21ab3e441a
Vulnerable CVE Program (cve.org) e CISA ADP
Linux Linux Kernel ≥ 3.18.139 and < 3.19version 7.1-rc2version 7.1-rc1≥ 6.19 and < 7.0.7≥ 6.13 and < 6.18.30≥ 6.7 and < 6.12.88≥ 6.2 and < 6.6.140≥ 5.16 and < 6.1.175
and 5 more ≥ 5.11 and < 5.15.209≥ 4.19.36 and < 5.10.258≥ 4.14.113 and < 4.15≥ 4.9.170 and < 4.10≥ 4.4.179 and < 4.5
Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
4.7 CVSS 3.1 Medium 1.0 3.6 nvd@nist.gov via NIST National Vulnerability Database
4.7 CVSS 3.1 Medium — — GitHub, Inc. via GitHub Security Advisories
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-362 · Race Condition

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.11%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

  • 2026
  • Source status changed · Analyzed → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · linux/linux
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 4.7
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    May 28, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 15, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

11 on the record

Elsewhere on this site

Linux
every CVE for this vendor
Logic error
same class
CWE-362
other pages naming this weakness

Related CVEs (same products)

  • Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 13h
  • Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 13h
  • Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 1d
  • Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 1d
  • Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 1d
  • Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-46187 is "wifi: rsi: fix kthread lifetime race between self-exit and external-stop", rated Medium. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.7 describes technical severity. EPSS 0.11% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.