Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-68319pds_core: fix deadlock between reset thread and remove

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.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 7 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 81665adf25d28a00a986533f1d3a5df76b79cad9 – < 90d9f3ef28843e6c35149324b8eefb427a7435c2
    • affected 81665adf25d28a00a986533f1d3a5df76b79cad9 – < 19ef775c91c6bf4bd2b60f6616f4e28b621cdd6a
    • affected 81665adf25d28a00a986533f1d3a5df76b79cad9 – < 54f905821f26d385fba407a920b51f0a752c76dc
    • affected 81665adf25d28a00a986533f1d3a5df76b79cad9 – < ab0eec0ff0a421737a37f510ceab5c6ea59cd05a
    • affected 38407914d48273d7f8ab765b9243658afe1c3ab6
    • affected 6.8.7 – < 6.9
  • Linux · Linux

    • affected 6.9
    • unaffected < 6.9
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-68319 badge
[![CVE-2026-68319](https://cveledger.app/badge/CVE-2026-68319.svg)](https://cveledger.app/cve/CVE-2026-68319)

Record last updated .