CVE-2025-71158: gpio: mpsse: ensure worker is torn down
In the Linux kernel, the following vulnerability has been resolved:
gpio: mpsse: ensure worker is torn down
When an IRQ worker is running, unplugging the device would cause a
crash. The sealevel hardware this driver was written for was not
hotpluggable, so I never realized it.
This change uses a spinlock to protect a list of workers, which
it tears down on disconnect.
Security readout for executives and security teams
Plain-English summary
A Linux GPIO driver can crash the system if its device is unplugged while an interrupt worker is running. Exposure appears limited to systems using the MPSSE GPIO driver with relevant hardware. The supplied sources do not establish remote exploitation or attacks in the wild.
Executive priority
Treat as a high-priority targeted update for exposed operational, embedded, or hardware-control systems. Broad emergency action is not supported because the trigger is local and hardware-dependent, with no evidence of active exploitation. Confirm exposure before prioritizing fleet-wide disruption.
Technical view
The gpio-mpsse disconnect path failed to stop active IRQ workers. Disconnecting hardware could therefore leave worker activity referencing invalid state and trigger a kernel crash. The fix protects the worker list with a spinlock and tears down workers during disconnect. The supplied description demonstrates availability impact; it does not explain the CVSS-rated confidentiality or integrity impacts.
Likely exposure
Most Linux systems are unlikely to exercise this driver and hardware path. Prioritize systems using gpio-mpsse with relevant Sealevel or compatible hardware, particularly where devices can be disconnected during IRQ activity. The bundle lists affected kernel versions but does not provide sufficiently clear distribution-specific package ranges.
Exploitation context
The CVSS vector requires local access, low privileges, low complexity, and no user interaction. Triggering also depends on an active IRQ worker and device disconnection. This CVE is not in KEV, and the supplied sources provide no evidence of active exploitation or public weaponization.
Researcher notes
No CWE is supplied. The record references two stable-kernel commits, likely for different maintained branches, but the bundle does not map them clearly to fixed distribution releases. Analysts should distinguish the documented disconnect-time crash from broader confidentiality and integrity effects implied only by the CVSS vector.
Mitigation direction
Install a vendor-supported kernel containing the applicable referenced stable fix.
Check distribution or appliance guidance for exact fixed package versions.
Until updated, prevent disconnection of affected hardware while IRQ activity may be running.
Restrict physical and local access to systems using the affected driver.
Validation and detection
Inventory kernel versions on systems connected to relevant GPIO hardware.
Determine whether gpio-mpsse is present and actively used.
Confirm the installed vendor kernel includes the applicable referenced fix.
Review kernel crash logs for failures associated with gpio-mpsse device disconnection.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2025-71158 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
3Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.