Skip to main content

Linux Kernel EUVDEUVD-2026-48975

| CVE-2026-64263 MEDIUM
2026-07-25 Linux GHSA-298c-3cxp-3c2h
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 privilege suffices; no scope change; impact is kernel crash only, so availability is high and confidentiality/integrity are unaffected.

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

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

5
Analysis Generated
Aug 12, 2026 - 16:20 vuln.today
CVSS changed
Aug 12, 2026 - 16:07 NVD
5.5 (MEDIUM)
Patch available
Jul 25, 2026 - 11:18 EUVD
CVE Published
Jul 25, 2026 - 08:49 nvd
MEDIUM 5.5
CVE Published
Jul 25, 2026 - 08:49 cve.org
UNKNOWN (no severity yet)

DescriptionNVD

In the Linux kernel, the following vulnerability has been resolved:

fuse-uring: fix moving cancelled entry to ent_in_userspace list

fuse_uring_cancel() moves entries that are available (these have no reqs attached) to the ent_in_userspace list. ent_list_request_expired() checks the first entry on ent_in_userspace and dereferences ent->fuse_req unconditionally, which will crash on a cancelled entry that was moved to this list.

Fix this by freeing the entry and dropping queue_refs directly in fuse_uring_cancel(). This is safe because cancel is the cancel handler itself - after io_uring_cmd_done(), no more cancels will be dispatched for this command, and teardown serializes with cancel via queue->lock.

Since cancel now decrements queue_refs, fuse_uring_abort() must no longer gate fuse_uring_abort_end_requests() on queue_refs > 0, as cancelled entries may have already dropped queue_refs while requests are still queued. Remove the gate so abort always flushes requests and stops queues.

AnalysisAI

Kernel panic in the Linux kernel's fuse-uring subsystem allows a local low-privileged attacker to crash the system by triggering a NULL pointer dereference through crafted io_uring cancellation sequences against a FUSE filesystem. The root cause is that fuse_uring_cancel() moves cancelled entries with no attached requests to the ent_in_userspace list, where ent_list_request_expired() unconditionally dereferences ent->fuse_req, crashing the kernel. No public exploit code exists and EPSS sits at 0.21% (11th percentile), indicating negligible opportunistic exploitation pressure; however, the low privilege requirement and local DoS impact make it relevant for multi-tenant or shared-access Linux environments.

Technical ContextAI

fuse-uring is a Linux kernel subsystem introduced in kernel 6.16 that integrates FUSE (Filesystem in Userspace) with io_uring for high-performance asynchronous I/O. The affected code path involves the cancellation handler fuse_uring_cancel() and the expiry checker ent_list_request_expired(). When an io_uring command is cancelled for an 'available' entry - one that has no fuse_req attached - the cancel handler moves that entry to the ent_in_userspace list. The expiry checker then reads the first entry on that list and dereferences ent->fuse_req without a NULL guard, producing a kernel NULL pointer dereference and system crash. The fix restructures the cancel handler to free the entry and drop queue_refs directly rather than relocating it, and removes the queue_refs gate in fuse_uring_abort() that incorrectly prevented request flushing when queue_refs had already been decremented by cancelled entries. Affected CPE: cpe:2.3:a:linux:linux:*. No CWE was formally assigned, but the root cause class is a missing NULL check following a state transition in a complex async cancellation path.

RemediationAI

Upgrade to Linux kernel 6.18.39, 7.1.4, or 7.2-rc1 or later, which incorporate the fixes available at https://git.kernel.org/stable/c/50f3e03db823cabc41fe35c27d77c2bdb112baad (6.x branch), https://git.kernel.org/stable/c/e8afc85acdf329361b2d8df2ad9b52364686235f (6.18 branch), and https://git.kernel.org/stable/c/198f45eeb9f78b2a2d6d8be95e4e43468eb2c6bc (7.x branch). Linux distribution maintainers (RHEL, Debian, Ubuntu, SUSE) should be checked for backported patches if in-tree kernel upgrade is not feasible. As a compensating control where patching is not immediately possible, io_uring can be disabled system-wide by setting /proc/sys/kernel/io_uring_disabled=2 (available since kernel 6.6), which eliminates the attack surface entirely at the cost of blocking all io_uring usage for all processes - this may impact performance-sensitive workloads relying on async I/O. Alternatively, using seccomp policies to block io_uring-related syscalls (io_uring_setup, io_uring_enter) for untrusted processes provides a more scoped mitigation with less system-wide impact.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
openSUSE Tumbleweed Fixed
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise Desktop 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected
SUSE Linux Enterprise High Availability Extension 15 SP7 Not-Affected

Share

EUVD-2026-48975 vulnerability details – vuln.today

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