CVE-2026-90095 Linux CVE debrief

Who should care

Defenders and administrators of Linux systems using fuse should assess exposure and verify if their kernel versions are affected. They should also ensure that FUSE_OVER_IO_URING is properly set in FUSE_INIT_REPLY to prevent potential deadlocks. This involves reviewing the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. Additionally, they should plan vendor-supported updates or mitigations through normal

Why it matters

Defenders should care about CVE-2026-90095 as it concerns a Linux kernel vulnerability affecting fuse over-io-uring condition, potentially leading to deadlocks. Verification of kernel versions and FUSE_OVER_IO_URING setting is crucial.

• Potential deadlocks between fch->bg_lock and queue->lock
• Necessity to verify FUSE_OVER_IO_URING setting in FUSE_INIT_REPLY
• Potential impact on systems using fuse with io-uring

Technical summary

The Linux kernel vulnerability CVE-2026-90095 addresses a condition to enable over-io-uring in fuse. The existing condition in fuse_uring_cmd() was insufficient, potentially leading to deadlocks. The fix requires FUSE_OVER_IO_URING to be set in the FUSE_INIT_REPLY by fuse servers. This change ensures that the barrier in fuse_uring_ready() works correctly, preventing potential deadlocks between fch->bg_lock and queue->lock. The vulnerability affects Linux systems using fuse and requires verification of kernel versions and FUSE_OVER_IO_URING setting.

Defensive priority

Defenders should prioritize verifying if their Linux kernel versions are affected and ensure that FUSE_OVER_IO_URING is properly set in FUSE_INIT_REPLY to prevent potential deadlocks.

Recommended defensive actions

• Verify Linux kernel versions for potential vulnerability
• Ensure FUSE_OVER_IO_URING is set in FUSE_INIT_REPLY
• Monitor for updates on Qemu patches for fuse-io-uring
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability and its fix. However, the corpus does not establish versions, exploitation, impact, or remediation for all affected systems, requiring verification from official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.