CVE-2026-68319

pds_core: fix deadlock between reset thread and remove

N/A
Published: August 10, 2026 at 12:02 PM UTC
Updated: August 17, 2026 at 05:18 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
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: pds_core: fix deadlock between reset thread and remove pci_reset_function() acquires device_lock before performing the reset. pdsc_remove() is called by the PCI core with device_lock already held. If pdsc_pci_reset_thread() is running when pdsc_remove() is called, destroy_workqueue() will block waiting for the work to complete, while the work is blocked waiting for device_lock - deadlock. Use pci_try_reset_function() which uses pci_dev_trylock() internally. This acquires both the device lock and the PCI config access lock without blocking - if either lock is contended, it returns -EAGAIN immediately. This avoids the deadlock while also ensuring proper config space access serialization during the reset. The pci_dev_get/put calls are also removed as they were unnecessary - the driver-owned workqueue is destroyed in pdsc_remove(), guaranteeing the work completes before remove returns. The PCI core holds its reference to pci_dev throughout the entire unbind sequence.

Affected

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

v ≥ 6.8.76.8.7 ≤ v < 6.96.9 ≤ v < 6.12.1016.9 ≤ v < 6.18.426.9 ≤ v < 7.1.66.9 ≤ v < 7.238407914d48273d7f8ab765b9243658afe1c3ab66.8.76.981665adf25d28a00a986533f1d3a5df76b79cad9
Vendor states this is fixed in 19ef775c91c6bf4bd2b60f6616f4e28b621cdd6a (fixed)
Vendor states this is fixed in 54f905821f26d385fba407a920b51f0a752c76dc (fixed)
Vendor states this is fixed in 90d9f3ef28843e6c35149324b8eefb427a7435c2 (fixed)
Vendor states this is fixed in ab0eec0ff0a421737a37f510ceab5c6ea59cd05a (fixed)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

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