CVE-2025-39721: Linux kernel · crypto: qat – flush misc workqueue during device shutdown
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 5.5 Medium · fixed in 6.8.0-1046.49~22.04.1 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.8.0-1046.49~22.04.1, 6.8.0-1051.57~22.04.1, 6.8.0-1047.50~22.04.2 +24
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Sep 2025
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.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-8028-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8031-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-8031-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-6 (opens in a new tab)
- ubuntu.com/security/notices/USN-8031-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8052-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-7 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-8 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 25.10linux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=questingOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-aws-6.14pkg:deb/ubuntu/linux-aws-6.14?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=nobleOther threats | Affected
| Fixed in
|
Ubuntu 24.04 LTSlinux-azure-6.11pkg:deb/ubuntu/linux-azure-6.11?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available and should be applied by updating to the fixed Linux kernel versions as provided by the vendor. The Ubuntu security advisories USN-8028-1 and USN-8028-2 confirm that this vulnerability is fixed in Linux kernel versions 6.8.0-100.100 and later. After updating, a system reboot is required. Due to ABI changes, third-party kernel modules must be recompiled and reinstalled. No additional mitigation steps are indicated by the vendor.
Description
A use-after-free vulnerability in the Linux kernel's crypto QAT driver (intel_qat and device-specific qat_4xxx) can cause kernel crashes when the device-specific driver is repeatedly loaded and unloaded in a tight loop. This occurs because a deferred workqueue routine may execute after the driver is unloaded, dereferencing freed memory. The issue has been assigned CVE-2025-39721 and affects multiple Linux kernel versions. A patch is available to fix this flaw.
References
- ubuntu.com/security/CVE-2025-39721 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2025-39721 (opens in a new tab)
- git.kernel.org/linus/3d4df408ba9bad2b205c7fb8afc1836a6a4ca88a (opens in a new tab)
- git.kernel.org/stable/c/3d4df408ba9bad2b205c7fb8afc1836a6a4ca88a (opens in a new tab)
- git.kernel.org/stable/c/5858448a6c65d8ee3f8600570d3ce19febcb33be (opens in a new tab)
- git.kernel.org/stable/c/e59a52e429e13df3feb34f4853a8e36d121ed937 (opens in a new tab)
- git.kernel.org/stable/c/fe546f5c50fc474daca6bee72caa7ab68a74c33d (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8031-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-5 (opens in a new tab)
- ubuntu.com/security/notices/USN-8031-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-6 (opens in a new tab)
- ubuntu.com/security/notices/USN-8031-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8052-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-7 (opens in a new tab)
- ubuntu.com/security/notices/USN-8028-8 (opens in a new tab)
- ubuntu.com/security/notices/USN-8052-2 (opens in a new tab)