Answer in brief
CVE-2026-68318 records a Unknown severity vulnerability in pds_core: fix use-after-free on workqueue during 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 | >=01ba61b55b2041a39c54aefb3153c770dd59a0ef <224214eb4182ff20a665b615a90b66017539dd75 || >=01ba61b55b2041a39c54aefb3153c770dd59a0ef <9e0f80fac50ab95dd75537c8ecaf5051d01f19b5 || >=01ba61b55b2041a39c54aefb3153c770dd59a0ef <ecc7a7d7569ec1d6a61e18372696b9de97635156 || >=01ba61b55b2041a39c54aefb3153c770dd59a0ef <0ad134881508c36b65c1a8864f8bec53adbd3327 | 224214eb4182ff20a665b615a90b66017539dd75, 9e0f80fac50ab95dd75537c8ecaf5051d01f19b5, ecc7a7d7569ec1d6a61e18372696b9de97635156, 0ad134881508c36b65c1a8864f8bec53adbd3327 |
| Linux/Linuxgeneric | 6.4 | 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 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.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-68318 records a Unknown severity vulnerability in pds_core: fix use-after-free on workqueue during 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 | >=01ba61b55b2041a39c54aefb3153c770dd59a0ef <224214eb4182ff20a665b615a90b66017539dd75 || >=01ba61b55b2041a39c54aefb3153c770dd59a0ef <9e0f80fac50ab95dd75537c8ecaf5051d01f19b5 || >=01ba61b55b2041a39c54aefb3153c770dd59a0ef <ecc7a7d7569ec1d6a61e18372696b9de97635156 || >=01ba61b55b2041a39c54aefb3153c770dd59a0ef <0ad134881508c36b65c1a8864f8bec53adbd3327 | 224214eb4182ff20a665b615a90b66017539dd75, 9e0f80fac50ab95dd75537c8ecaf5051d01f19b5, ecc7a7d7569ec1d6a61e18372696b9de97635156, 0ad134881508c36b65c1a8864f8bec53adbd3327 |
| Linux/Linuxgeneric | 6.4 | 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 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.
Quoted source text, attributed separately from HOL analysis.