Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
High

Use-after-free in Linux kernel GFS2 iomap inline data write path

IdentifiersCVE-2026-45984CWE-416· Use After Free

CVE-2026-45984 is a Linux kernel vulnerability in the GFS2 filesystem inline-data write path. In gfs2_iomap_begin(), inode metadata is read into the inline data buffer head (dibh) via gfs2_meta_inode_buffer(), and iomap->inline_data is set to point into dibh->b_data at an offset past struct gfs2_dinode. The bug is that gfs2_iomap_begin() then calls release_metapath(), which invokes brelse(dibh) and can drop the buffer-head reference count to zero while iomap->inline_data still references that memory. If the backing page is reclaimed before the write completes, iomap_write_end_inline() later performs memcpy() to iomap->inline_data, resulting in a kernel use-after-free write. The issue was identified from a KASAN report and code review. The fix stores dibh in iomap->private, takes an additional reference with get_bh() in gfs2_iomap_begin(), and releases it in gfs2_iomap_end() after the inline write operation completes.

Share:
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.

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.

Successful exploitation triggers a write-after-free in kernel memory during GFS2 inline data writes. This can lead to kernel memory corruption, system instability, crashes or denial of service, and potentially privilege escalation or other integrity/confidentiality impacts depending on allocator state and exploitability. Available scoring in the provided context characterizes the issue as local, low complexity, requiring low privileges and no user interaction.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting local access and privileges on systems that use the GFS2 filesystem, especially workloads capable of triggering inline-data write paths. Minimize use of affected kernels for untrusted multi-user workloads and prefer disabling or avoiding GFS2 where operationally feasible until patched. No specific runtime-only mitigation beyond applying a fixed kernel is provided in the available information.

Remediation

Patch, then assume compromise.

Upgrade to a Linux kernel build containing the upstream fix for CVE-2026-45984. The corrective change preserves the lifetime of the inline data buffer head across the full iomap operation by storing dibh in iomap->private, incrementing its reference count with get_bh() in gfs2_iomap_begin(), and releasing it in gfs2_iomap_end() after the inline write completes. Vendor kernel updates from SUSE and other downstreams listed in the provided context include this fix.
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
Rocky LinuxKerneloperating_system

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

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.
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

Community discussion across Reddit, Mastodon, and other social sources.