NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 0/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
Fixed version: Linux Linux 19ef775c91c6bf4bd2b60f6616f4e28b621cdd6a, 54f905821f26d385fba407a920b51f0a752c76dc, 6.9.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 19ef775c91c6bf4bd2b60f6616f4e28b621cdd6a, 54f905821f26d385fba407a920b51f0a752c76dc, 6.9 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

—No exploit Fix available

Published: Aug 10, 2026
Updated: Aug 17, 2026
EPSS: 0.1% · 6th percentile
CWE: —

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 0 / 40 · —
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 38407914d48273d7f8ab765b9243658afe1c3ab6, 6.9affected
- 81665adf25d28a00a986533f1d3a5df76b79cad9 and later · before 90d9f3ef28843e6c35149324b8eefb427a7435c2affected · git
- 81665adf25d28a00a986533f1d3a5df76b79cad9 and later · before 19ef775c91c6bf4bd2b60f6616f4e28b621cdd6aaffected · git
- 81665adf25d28a00a986533f1d3a5df76b79cad9 and later · before 54f905821f26d385fba407a920b51f0a752c76dcaffected · git
- 81665adf25d28a00a986533f1d3a5df76b79cad9 and later · before ab0eec0ff0a421737a37f510ceab5c6ea59cd05aaffected · git
- 6.8.7 and later · before 6.9affected · semver
- before 6.9not affected · semver
- 6.12.101 and later · up to and including 6.12.*not affected · semver
- 6.18.42 and later · up to and including 6.18.*not affected · semver
- 7.1.6 and later · up to and including 7.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux-6.12	before 6.12.101-1~deb12u1	6.12.101-1~deb12u1
Debian:13	linux	before 6.12.101-1	6.12.101-1
Debian:14	linux	before 7.1.6-1	7.1.6-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
40Plan
CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
40Plan
CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
40Plan

Published before and after this one in the same product

← EarlierCVE-2026-68316Aug 10, 2026 · accel: ethosu: Fix element size accounting for cmd stream validation
31Monitor
← EarlierCVE-2026-68317Aug 10, 2026 · pds_core: fix auxiliary device add/del races
0Monitor
Later →CVE-2026-68321Aug 10, 2026 · net: txgbe: fix FDIR filter leak on remove
0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	19ef775c91c6bf4bd2b60f6616f4e28b621cdd6a	Vendor (CNA)
Linux Linux	54f905821f26d385fba407a920b51f0a752c76dc	Vendor (CNA)
Linux Linux	6.9	Vendor (CNA)
Linux Linux	90d9f3ef28843e6c35149324b8eefb427a7435c2	Vendor (CNA)
Linux Linux	ab0eec0ff0a421737a37f510ceab5c6ea59cd05a	Vendor (CNA)
debian:linux	6.12.101-1 · Debian:13	Package registry (OSV)
debian:linux-6.12	6.12.101-1~deb12u1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

TR-26-0800 · Aug 11, 2026(Linux Kernel Güvenlik Bildirimi)

All national notices →

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

git.kernel.org/stable/c/19ef775c91c6bf4bd2b60f6616f4e28b621cdd6a

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records