CVE-2025-39777: Linux kernel · crypto: acomp – Fix CFI failure due to type punning
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 19 Nov 2026, 02:22 UTC
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 11 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 18 Nov 2026.
What to do
AI-suggested
A fix has been implemented in the Linux kernel to address this issue by correcting the type usage in the crypto acomp workspace free function. Users should apply the official kernel updates that include this fix. Since this is a kernel-level issue, upgrading to a patched kernel version is the recommended mitigation.
Description
CVE-2025-39777 is a medium severity vulnerability in the Linux kernel's crypto subsystem related to acomp. It addresses a control flow integrity (CFI) failure caused by type punning, which could lead to a crash when CFI is enabled. The fix involves ensuring consistent use of types in the workspace free function and calling it through a correctly typed function pointer.