Skip to main content

Linux Kernel EUVDEUVD-2026-26522

| CVE-2026-31713 MEDIUM
2026-05-01 416baaa9-dc9f-4396-8d5f-8c081fb06d67
5.5
CVSS 3.1 · NVD
Share

Severity by source

NVD PRIMARY
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
5.5 MEDIUM

Local access with low privileges required to mount FUSE; impact is purely availability via mounting thread hang with no confidentiality or integrity effect.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative
Red Hat
5.5 LOW
qualitative

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

7
Analysis Generated
Jul 24, 2026 - 01:12 vuln.today
CVSS changed
May 06, 2026 - 21:22 NVD
5.5 (MEDIUM)
Patch released
May 01, 2026 - 15:24 nvd
Patch available
Patch available
May 01, 2026 - 15:02 EUVD
EUVD ID Assigned
May 01, 2026 - 14:22 euvd
EUVD-2026-26522
CVE Published
May 01, 2026 - 14:16 nvd
MEDIUM 5.5
CVE Published
May 01, 2026 - 14:16 nvd
N/A

DescriptionCVE.org

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.

AnalysisAI

Filesystem hang in the Linux kernel FUSE subsystem allows a local low-privileged user to cause a denial of service by triggering a deadlock during synchronous FUSE initialization. When the FUSE userspace server exits or crashes while processing FUSE_INIT via the sync init path, the mounting thread retains the device file descriptor open, blocking the kernel abort mechanism and causing an indefinite hang. Affecting Linux kernel versions through 6.18, this is a regression from the async mount behavior; fixes are available in 7.0.2, 6.18.25, and 7.1-rc1. No public exploit exists and EPSS is 0.02% (4th percentile), indicating negligible active exploitation probability.

Technical ContextAI

FUSE (Filesystem in Userspace) is a Linux kernel subsystem that exposes a device interface allowing unprivileged userspace programs to implement fully functional filesystems. The synchronous init path - used when the mounting thread itself handles FUSE_INIT before the mount completes - keeps the FUSE device fd open during the init handshake. This creates a recursive fd-hold: the mounting thread is the sole holder of the device, so if the userspace FUSE server exits abnormally (crash, SIGKILL, etc.) during FUSE_INIT processing, the kernel's abort logic cannot fire because it depends on all holders of the fd closing it first. The async mount path does not exhibit this because the mount syscall completes before FUSE_INIT is processed, meaning no recursive open is active. The root cause is a signal-handling gap in the synchronous init flow - the kernel does not check for fatal pending signals to break the wait loop when the fd owner is the waiter itself. CPE cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* covers all affected kernel versions; NVD did not assign a CWE, but the class is best described as improper handling of exceptional conditions (CWE-755) or a resource locking / signal-response failure.

RemediationAI

Upgrade to Linux kernel 7.0.2 or 6.18.25 (stable series), or to 7.1-rc1 (development), which include the three upstream fix commits: 0c7fca880a40a209a9c92be14143996d14b93ff6, 204aa22a686bfee48daca7db620c1e017615f2ff, and 300e812b882a174dca675d8028684001ad5826bc (https://git.kernel.org/stable/c/0c7fca880a40a209a9c92be14143996d14b93ff6). Ubuntu users should apply the packages referenced in USN-8488-1 (https://ubuntu.com/security/notices/USN-8488-1). For systems where immediate kernel upgrade is not feasible, restrict unprivileged FUSE mounting by setting user.max_user_namespaces=0 or configuring appropriate mount restrictions - note this will break legitimate FUSE-based applications such as SSHFS or OverlayFS in user namespaces. Red Hat and SUSE customers should monitor vendor advisories for backported patches to their supported kernel versions.

Vendor StatusVendor

SUSE

Severity: Medium
Product Status
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise Desktop 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Availability Extension 15 SP7 Fixed
SUSE Linux Enterprise High Performance Computing 15 SP7 Fixed

Share

EUVD-2026-26522 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy