CVE-2026-31713: Linux kernel · fuse: abort on fatal signal during sync init
Source GCVE Database
Not known to be exploited · CVSS 5.5 Medium.
Data as of 27 Oct 2026, 00:07 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 1 May 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.
Description
In the Linux kernel, the following vulnerability has been resolved: fuse: abort on fatal signal during sync init When sync init is used and the server exits for some reason (error, crash) while processing FUSE_INIT, the filesystem creation will hang. The reason is that while all other threads will exit, the mounting thread (or process) will keep the device fd open, which will prevent an abort from happening. This is a regression from the async mount case, where the mount was done first, and the FUSE_INIT processing afterwards, in which case there's no such recursive syscall keeping the fd open.
References
- nvd.nist.gov/vuln/detail/CVE-2026-31713 (opens in a new tab)
- git.kernel.org/stable/c/0c7fca880a40a209a9c92be14143996d14b93ff6 (opens in a new tab)
- git.kernel.org/stable/c/204aa22a686bfee48daca7db620c1e017615f2ff (opens in a new tab)
- git.kernel.org/stable/c/300e812b882a174dca675d8028684001ad5826bc (opens in a new tab)