CVE-2026-68319

pds_core: fix deadlock between reset thread and remove

State
Published
Severity
Not scored
Published
Aug 10, 2026
Updated
Aug 17, 2026
Reserved
Jul 30, 2026

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 81665adf25d28a00a986533f1d3a5df76b79cad9 to before 90d9f3ef28843e6c35149324b8eefb427a7435c2Affected
  • 81665adf25d28a00a986533f1d3a5df76b79cad9 to before 19ef775c91c6bf4bd2b60f6616f4e28b621cdd6aAffected
  • 81665adf25d28a00a986533f1d3a5df76b79cad9 to before 54f905821f26d385fba407a920b51f0a752c76dcAffected
  • 81665adf25d28a00a986533f1d3a5df76b79cad9 to before ab0eec0ff0a421737a37f510ceab5c6ea59cd05aAffected
  • 38407914d48273d7f8ab765b9243658afe1c3ab6Affected
  • 6.8.7 to before 6.9Affected
LinuxLinux
  • 6.9Affected
  • before 6.9Not affected
  • 6.12.101 through 6.12.*Not affected
  • 6.18.42 through 6.18.*Not affected
  • 7.1.6 through 7.1.*Not affected
  • 7.2 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.