VulnerabilityPublished 10 Aug 2026Updated 21 Oct 2026

CVE-2026-68318: Linux kernel · pds_core: fix use-after-free on workqueue during remove

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in ecc7a7d7569ec1d6a61e18372696b9de97635156 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:07 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in ecc7a7d7569ec1d6a61e18372696b9de97635156, bac237c2aedb8225bfd2317c1361bbfce1e419ca, 224214eb4182ff20a665b615a90b66017539dd75 +2

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 01ba61b55b2041a39c54aefb3153c770dd59a0ef, < ecc7a7d7569ec1d6a61e18372696b9de97635156	Fixed in ecc7a7d7569ec1d6a61e18372696b9de97635156
LinuxLinux	Affected ≥ 01ba61b55b2041a39c54aefb3153c770dd59a0ef, < bac237c2aedb8225bfd2317c1361bbfce1e419ca	Fixed in bac237c2aedb8225bfd2317c1361bbfce1e419ca
LinuxLinux	Affected ≥ 01ba61b55b2041a39c54aefb3153c770dd59a0ef, < 224214eb4182ff20a665b615a90b66017539dd75	Fixed in 224214eb4182ff20a665b615a90b66017539dd75
LinuxLinux	Affected ≥ 01ba61b55b2041a39c54aefb3153c770dd59a0ef, < 9e0f80fac50ab95dd75537c8ecaf5051d01f19b5	Fixed in 9e0f80fac50ab95dd75537c8ecaf5051d01f19b5
LinuxLinux	Affected ≥ 01ba61b55b2041a39c54aefb3153c770dd59a0ef, < 0ad134881508c36b65c1a8864f8bec53adbd3327	Fixed in 0ad134881508c36b65c1a8864f8bec53adbd3327
LinuxLinux	Affected =6.4	Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: pds_core: fix use-after-free on workqueue during remove In pdsc_remove(), the workqueue is destroyed before pdsc_teardown() is called. This ordering allows two paths to queue work on the destroyed workqueue: 1. If pdsc_teardown() -> pdsc_devcmd_reset() times out, the error path in pdsc_devcmd_locked() queues health_work. 2. A NotifyQ event can trigger the ISR and queue work before free_irq() is called in pdsc_teardown(). Fix by moving destroy_workqueue() after pdsc_teardown() so the workqueue outlives every queuer; destroy_workqueue() then flushes any work still pending. Draining the queued work also requires ordering the teardown so the resources that work touches are freed last: - In pdsc_qcq_free(), after freeing the interrupt, cancel_work_sync() the queue's work and only then clear qcq->intx, so pdsc_process_adminq()'s read of qcq->intx for interrupt-credit return cannot race with the clear. - Free adminqcq before notifyqcq: the shared adminq ISR is released when adminqcq is freed, and the adminq work accesses notifyqcq, so both must be stopped before notifyqcq is freed.

References

Community reviews

Loading reviews…