CVE-2026-99050

gpio: mpsse: fix race when arming the IRQ poll worker

  • High 7.8

Description

In the Linux kernel, the following vulnerability has been resolved: gpio: mpsse: fix race when arming the IRQ poll worker gpio_mpsse_irq_enable() arms the poll worker before publishing it: schedule_work() runs before the worker is added to priv->workers. If gpio_mpsse_disconnect() walks the list in that window it misses the worker, and once disconnect returns, the USB core frees mpsse_priv while the orphaned gpio_mpsse_poll() work keeps accessing it, causing a use-after-free. Fix this by publishing and arming the worker in one irq_spin critical section. Teardown walks the same list under irq_spin, so a worker found on the list is guaranteed to be armed, and cancel_work_sync() handles it whether it is queued or running. A worker armed after the disconnect walk would still be missed, so also set a new priv->dying flag under irq_spin before the teardown walk, and check it in the same critical section, freeing it via kfree_rcu() instead when the device is going away, since kfree() would be called with the IRQ core's raw spinlock held and may sleep on PREEMPT_RT. schedule_work() is safe to call with irq_spin held, and the next probe gets a fresh mpsse_priv, so the flag never needs to be cleared. This issue was found by an in-house static analysis tool.

Key facts

Published
23 Oct 2026
Last changed
24 Oct 2026
Assigned by
Linux
EPSS
0.157% likely to be exploited in the next 30 days, higher than 4.892% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.8CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 472d900c8bcac301ae0e40fdca7db799bd989ff5 up to but excluding 76390ac0bca7e5058b7482eb4d951c3bda5df812 (affected)
  • 179ef1127d7a4f09f0e741fa9f30b8a8e7886271 up to but excluding c0071ee496e1228976c72b096f529503222708a0 (affected)
  • 179ef1127d7a4f09f0e741fa9f30b8a8e7886271 up to but excluding 7efa1a1953cd6b20b23a3524d5b4b81789c6ef25 (affected)
  • 6.18.6 up to but excluding 6.18.57 (affected)
LinuxLinux
  • Default status: affected
  • 6.19 (affected)
  • 0 up to but excluding 6.19 (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.11 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 23 Oct 2026 Published

References