Medium

Linux kernel io_uring O_DIRECT write filesystem-freeze deadlock

IdentifiersCVE-2024-53052CWE-833

CVE-2024-53052 is a deadlock in the Linux kernel io_uring read/write path when initiating an O_DIRECT write. The path unconditionally acquires the superblock write-in-flight read lock through kiocb_start_write(), rather than honoring the nonblocking IOCB_NOWAIT state. During a concurrent filesystem freeze, the freezer holds or waits to acquire the corresponding write lock while waiting for previously issued writes to complete. The task responsible for progressing those writes can become blocked while trying to start a new write, creating a circular wait. The fix honors IOCB_NOWAIT and returns EAGAIN for the nonblocking attempt, allowing io_uring to reissue a blocking write in a manner that runs completions and restores forward progress.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A successful trigger can leave both io_uring write processing and filesystem-freeze operations blocked indefinitely, causing a kernel-level denial of service for affected storage workloads and preventing completion of the freeze operation. The supplied information does not indicate memory corruption, information disclosure, or privilege escalation.

Mitigation

If you can’t patch tonight, do this now.

Until the kernel is updated, avoid concurrently initiating filesystem-freeze operations and io_uring O_DIRECT write workloads on the same mounted filesystem. Restrict filesystem-freeze capability to trusted administrators, as initiating a freeze requires CAP_SYS_ADMIN.

Remediation

Patch, then assume compromise.

Install a Linux kernel update incorporating the fix for CVE-2024-53052, which makes the io_uring write-start path honor IOCB_NOWAIT. Reboot after updating so the patched kernel is running.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

LinuxLinux Kerneloperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

1 SOURCESView more in app

redhat accessNews

Jan 1, 2026

RHSA-2025:20518 - Security Advisory - Red Hat Customer Portal

Linux kernel io_uring direct-I/O NOWAIT handling flaw.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity