Answer in brief
CVE-2026-68319 records a Unknown severity vulnerability in pds_core: fix deadlock between reset thread and remove. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=81665adf25d28a00a986533f1d3a5df76b79cad9 <90d9f3ef28843e6c35149324b8eefb427a7435c2 || >=81665adf25d28a00a986533f1d3a5df76b79cad9 <19ef775c91c6bf4bd2b60f6616f4e28b621cdd6a || >=81665adf25d28a00a986533f1d3a5df76b79cad9 <54f905821f26d385fba407a920b51f0a752c76dc || >=81665adf25d28a00a986533f1d3a5df76b79cad9 <ab0eec0ff0a421737a37f510ceab5c6ea59cd05a || 38407914d48273d7f8ab765b9243658afe1c3ab6 || >=6.8.7 <6.9 | 90d9f3ef28843e6c35149324b8eefb427a7435c2, 19ef775c91c6bf4bd2b60f6616f4e28b621cdd6a, 54f905821f26d385fba407a920b51f0a752c76dc, ab0eec0ff0a421737a37f510ceab5c6ea59cd05a, 6.9 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68319 records a Unknown severity vulnerability in pds_core: fix deadlock between reset thread and remove. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=81665adf25d28a00a986533f1d3a5df76b79cad9 <90d9f3ef28843e6c35149324b8eefb427a7435c2 || >=81665adf25d28a00a986533f1d3a5df76b79cad9 <19ef775c91c6bf4bd2b60f6616f4e28b621cdd6a || >=81665adf25d28a00a986533f1d3a5df76b79cad9 <54f905821f26d385fba407a920b51f0a752c76dc || >=81665adf25d28a00a986533f1d3a5df76b79cad9 <ab0eec0ff0a421737a37f510ceab5c6ea59cd05a || 38407914d48273d7f8ab765b9243658afe1c3ab6 || >=6.8.7 <6.9 | 90d9f3ef28843e6c35149324b8eefb427a7435c2, 19ef775c91c6bf4bd2b60f6616f4e28b621cdd6a, 54f905821f26d385fba407a920b51f0a752c76dc, ab0eec0ff0a421737a37f510ceab5c6ea59cd05a, 6.9 |
| Linux/Linuxgeneric | 6.9 | Not reported |
Published upstream
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.