Status: UPDATED | Advisory ID: CVE-2026-45984
| CVE | CVE-2026-45984 |
| CVSS Score / Version | |
| Updated | 2026-10-16 |
| CVSS Vector | |
| CVSS Prose | |
| Affected products | |
| Classified as |
| Vendor | Product | Affected Versions | Patch Status |
|---|---|---|---|
| Linux | Linux Kernel | ||
| Red Hat | Red Hat Enterprise Linux 8 | ||
| Red Hat | Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | ||
| Red Hat | Red Hat Enterprise Linux 8.6 Extended Update Support Long-Life Add-On | ||
| Red Hat | Red Hat Enterprise Linux 8.8 Telecommunications Update Service | ||
| Red Hat | Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions | ||
| Red Hat | Red Hat Enterprise Linux 9 | ||
| Red Hat | Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions | ||
| Red Hat | Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions | ||
| Red Hat | Red Hat Enterprise Linux 9.6 Extended Update Support | ||
| Red Hat | Red Hat Enterprise Linux 7 Extended Lifecycle Support |
| Subsystems | OT Supporting Infrastructure |
| Sectors | All Sectors |
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().] (NVD)
Monitor Linux's and Red Hat's web pages for any future patch releases.
| Source | Reference |
|---|---|
| NVD | https://nvd.nist.gov/vuln/detail/CVE-2026-45984 |
| CVE | https://www.cve.org/CVERecord?id=CVE-2026-45984 |