CVE-2026-97948 — powerpc/eeh: Fix recursive locking on devices without EEH sensitive driver
In the Linux kernel, the following vulnerability has been resolved: powerpc/eeh: Fix recursive locking on devices without EEH sensitive driver The commit 1010b4c012b0 ("powerpc/eeh: Make EEH driver device hotplug safe") refactored the EEH code such that the pci_rescan_remove_lock is held at the beginning of eeh_handle_normal_event() and the eeh_reset_device() is called with that lock being held. Looks like the commit missed to remove the existing lock/unlock inside eeh_rmv_device() which is no longer necessary. This is causing the eehd to hang on the lock which it actually holds when that code path is taken. [<0>] 0xc00000011c78f870 [<0>] __switch_to+0xfc/0x1a0 [<0>] pci_lock_rescan_remove+0x30/0x44 [<0>] eeh_rmv_device+0x290/0x2e0 [<0>] eeh_pe_dev_traverse+0x80/0x130 [<0>] eeh_reset_device+0xcc/0x23c [<0>] eeh_handle_normal_event+0x830/0xa80 [<0>] eeh_event_handler+0xf8/0x190 [<0>] kthread+0x194/0x1b0 [<0>] start_kernel_thread+0x14/0x18 The issue is seen for cases where the errors are detected on the PHB directly AND|OR for devices where the driver error_detected() returns PCI_ERS_RESULT_NEED_RESET, and driver being not EEH sensitive(i.e no error handlers like slot_reset(), resume() etc defined).
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
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.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
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.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version 19d5036e7ad766cf212aebec23b9f1d7924a62bcversion 6.17≥ 6.16.1 and < 6.17≥ 6.15.10 and < 6.16≥ 6.12.42 and < 6.12.111≥ 6.6.102 and < 6.6.158≥ 6.1.148 and < 6.1.189≥ 5.15.190 and < 5.15.222 and 10 more≥ 5.10.241 and < 5.10.271≥ 502f08831a9afb72dc98a56ae6504da43e93b250 and < 3833dfae0680b6b16e2469fbc90aa48376311cd8version d42bbd8f30ac38b1ce54715bf08ec3dac18d6b25≥ 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7 and < c5e68706527968282e49de205cc2b935823cb88a≥ 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7 and < 85d8eaefc052cf3e5ae2c7bafeda2db68b8898b4≥ 1010b4c012b0d78dfb9d3132b49aa2ef024a07a7 and < 2920af33d097ca335e492b346af70b72986ad6dc≥ d2c60a8a387e9fcc28447ef36c03f8e49fd052a6 and < 102e3dc5ab5ba052e294819e83384166b242c1ec≥ a426e8a6ae161f51888585b065db0f8f93ab2e16 and < 460fab22b65138531082910702f74b048b25237b≥ 59c6d3d81d42bf543c90597b4f38c53d6874c5a1 and < a58531181363219fa5de2b53d5d7274dcdfca98b≥ f56e004b781719d8fdf6c9619b15caf2579bc1f2 and < 24524fca27da674668941440e8e05cdfec0b0222 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/c5e68706527968282e49de205cc2b935823cb88a
- git.kernel.org/stable/c/a58531181363219fa5de2b53d5d7274dcdfca98b
- git.kernel.org/stable/c/85d8eaefc052cf3e5ae2c7bafeda2db68b8898b4
- git.kernel.org/stable/c/102e3dc5ab5ba052e294819e83384166b242c1ec
- git.kernel.org/stable/c/24524fca27da674668941440e8e05cdfec0b0222
- git.kernel.org/stable/c/460fab22b65138531082910702f74b048b25237b
- git.kernel.org/stable/c/3833dfae0680b6b16e2469fbc90aa48376311cd8
- git.kernel.org/stable/c/2920af33d097ca335e492b346af70b72986ad6dc
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 1d
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 1d
- Unknown CVE-2026-98431 RDMA/uverbs: Fix mmap_lock/disassociation_lock circular dependency 2d
- Unknown CVE-2026-98430 RDMA/efa: Keep admin queues alive while IRQ is registered 2d
- Unknown CVE-2026-98429 RDMA/efa: Keep EQ resources alive while IRQ is registered 2d
- Unknown CVE-2026-98428 ALSA: usb: 6fire: Avoid embedded URBs 2d
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 CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- 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-97948 is "powerpc/eeh: Fix recursive locking on devices without EEH sensitive driver", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.18% 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.