CVE-2026-45984
In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix use-after-free in iomap inline data write path The inline data buffer head (dibh) is being released prematurely in gfs2_iomap_begin() via release_metapath() while…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.18%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix use-after-free in iomap inline data write path The inline data buffer head (dibh) is being released prematurely in gfs2_iomap_begin() via release_metapath() while iomap->inline_data still points to dibh->b_data. This causes a use-after-free when iomap_write_end_inline() later attempts to write to the inline data area. The bug sequence: 1. gfs2_iomap_begin() calls gfs2_meta_inode_buffer() to read inode metadata into dibh 2. Sets iomap->inline_data = dibh->b_data + sizeof(struct gfs2_dinode) 3. Calls release_metapath() which calls brelse(dibh), dropping refcount to 0 4. kswapd reclaims the page (~39ms later in the syzbot report) 5. iomap_write_end_inline() tries to memcpy() to iomap->inline_data 6. KASAN detects use-after-free write to freed memory Fix by storing dibh in iomap->private and incrementing its refcount with get_bh() in gfs2_iomap_begin(). The buffer is then properly released in gfs2_iomap_end() after the inline write completes, ensuring the page stays alive for the entire iomap operation. Note: A C reproducer is not available for this issue. The fix is based on analysis of the KASAN report and code review showing the buffer head is freed before use. [agruenba: Take buffer head reference in gfs2_iomap_begin() to avoid leaks in gfs2_iomap_get() and gfs2_iomap_alloc().]
- CVSS 3.1
- 7.8 HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 0.18% probability · 8th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-416, CWE-826
- Affected
- linux/linux kernel
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/1403989d1b502f4a2c0d0b42ccf1c25748442effPatch
- https://git.kernel.org/stable/c/1cae1bafdf9caa9b462b19af06b1a06902e4e142Patch
- https://git.kernel.org/stable/c/6d76febba07c40bcf358f63216d36ea68cf1c215Patch
- https://git.kernel.org/stable/c/764c3c84b5683e608f43735c803a5f415046686cPatch
- https://git.kernel.org/stable/c/815ddd27c0c7171a99fe802fdb19098ddef8b19dPatch
- https://git.kernel.org/stable/c/87d4954b5c59735a99ea98cb208d47130f6dce7dPatch
- https://git.kernel.org/stable/c/d87268326b277af3665237ac76a73dd9fa8e21b4Patch
- https://git.kernel.org/stable/c/faddeb848305e79db89ee0479bb0e33380656321Patch
- https://access.redhat.com/errata/RHSA-2026:27789
- https://access.redhat.com/errata/RHSA-2026:33743
- https://access.redhat.com/errata/RHSA-2026:35894
- https://access.redhat.com/errata/RHSA-2026:36049
- https://access.redhat.com/errata/RHSA-2026:36767
- https://access.redhat.com/errata/RHSA-2026:38902
- https://access.redhat.com/errata/RHSA-2026:51603
- https://access.redhat.com/errata/RHSA-2026:51604
- https://access.redhat.com/errata/RHSA-2026:55444
- https://access.redhat.com/errata/RHSA-2026:59142
- https://access.redhat.com/errata/RHSA-2026:59143
- https://access.redhat.com/errata/RHSA-2026:59145
- https://access.redhat.com/errata/RHSA-2026:59146
- https://access.redhat.com/errata/RHSA-2026:59147
- https://access.redhat.com/errata/RHSA-2026:59148
- https://access.redhat.com/errata/RHSA-2026:59149
- https://access.redhat.com/errata/RHSA-2026:61692
- https://access.redhat.com/errata/RHSA-2026:63189
- https://access.redhat.com/security/cve/CVE-2026-45984
- https://bugzilla.redhat.com/show_bug.cgi?id=2481922
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45984.json
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.