{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68318 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68318 is an use after free vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68318 and fix it if it is affected.\n\nWhat it is: CVE-2026-68318 is an use after free vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-68318 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-68318/ (Markdown: https://insights.sbomify.com/CVE-2026-68318/index.md)","id":"CVE-2026-68318","markdown":"https://insights.sbomify.com/CVE-2026-68318/index.md","name":"CVE-2026-68318","record":{"aliases":["AZL-94728","BELL-CVE-2026-68318","DEBIAN-CVE-2026-68318","GHSA-q3gg-v595-rj52","UBUNTU-CVE-2026-68318"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A use-after-free in the pds_core driver allows local attackers to execute arbitrary code or escalate privileges during device removal.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\npds_core: fix use-after-free on workqueue during remove\n\nIn pdsc_remove(), the workqueue is destroyed before pdsc_teardown()\nis called. This ordering allows two paths to queue work on the\ndestroyed workqueue:\n\n1. If pdsc_teardown() -\u003e pdsc_devcmd_reset() times out, the error\n   path in pdsc_devcmd_locked() queues health_work.\n\n2. A NotifyQ event can trigger the ISR and queue work before free_irq()\n   is called in pdsc_teardown().\n\nFix by moving destroy_workqueue() after pdsc_teardown() so the\nworkqueue outlives every queuer; destroy_workqueue() then flushes any\nwork still pending.\n\nDraining the queued work also requires ordering the teardown so the\nresources that work touches are freed last:\n\n  - In pdsc_qcq_free(), after freeing the interrupt, cancel_work_sync()\n    the queue's work and only then clear qcq-\u003eintx, so\n    pdsc_process_adminq()'s read of qcq-\u003eintx for interrupt-credit\n    return cannot race with the clear.\n\n  - Free adminqcq before notifyqcq: the shared adminq ISR is released\n    when adminqcq is freed, and the adminq work accesses notifyqcq, so\n    both must be stopped before notifyqcq is freed.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"pds_core: fix use-after-free on workqueue during remove","id":"CVE-2026-68318","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"pds_core: fix deadlock between reset thread and remove","id":"CVE-2026-68319"},"packages":[],"prev":{"headline":"pds_core: fix auxiliary device add/del races","id":"CVE-2026-68317"},"products":["Linux"],"published":"2026-08-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A use-after-free in the pds_core driver allows local attackers to execute arbitrary code or escalate privileges during device removal.","url":"https://insights.sbomify.com/CVE-2026-68318/"}