Vulnerability 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.
References
- https://git.kernel.org/stable/c/19ef775c91c6bf4bd2b60f6616f4e28b621cdd6a
- https://git.kernel.org/stable/c/54f905821f26d385fba407a920b51f0a752c76dc
- https://git.kernel.org/stable/c/90d9f3ef28843e6c35149324b8eefb427a7435c2
- https://git.kernel.org/stable/c/ab0eec0ff0a421737a37f510ceab5c6ea59cd05a
FAQ
What is CVE-2026-68319?
CVE-2026-68319 is a documented vulnerability. 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...
How severe is CVE-2026-68319?
CVSS scoring is not yet available for CVE-2026-68319. Check NVD for updates.
Is there a patch for CVE-2026-68319?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.