CVE-2025-21699

gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag

MEDIUM

5.5

CVSS Score

Published: February 12, 2025 at 01:52 PM UTC

Updated: August 5, 2026 at 12:44 PM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

SSVC

No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: gfs2: Truncate address space when flipping GFS2_DIF_JDATA flag Truncate an inode's address space when flipping the GFS2_DIF_JDATA flag: depending on that flag, the pages in the address space will either use buffer heads or iomap_folio_state structs, and we cannot mix the two.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v < 5.4.2905.10 ≤ v < 5.10.2345.10 ≤ v < 5.15.1785.10 ≤ v < 6.1.1285.10 ≤ v < 6.12.125.10 ≤ v < 6.13.15.10 ≤ v < 6.145.10 ≤ v < 6.6.755.11 ≤ v < 5.15.1785.16 ≤ v < 6.1.1285.5 ≤ v < 5.10.2346.2 ≤ v < 6.6.756.7 ≤ v < 6.12.122164f9b9186962ffb7c687e18ec6f5255525f09d6.13 6.13 rc1 6.13 rc2 6.13 rc3 6.13 rc4 6.13 rc5 6.13 rc6 6.13 rc7

Vendor states this is fixed in 2a40a140e11fec699e128170ccaa98b6b82cb503 (fixed)

Vendor states this is fixed in 4516febe325342555bb09ca5b396fb816d655821 (fixed)

Vendor states this is fixed in 4dd57d1f0e9844311c635a7fb39abce4f2ac5a61 (fixed)

Vendor states this is fixed in 4e3ded34f3f3c9d7ed2aac7be8cf51153646574a (fixed)

Vendor states this is fixed in 5bb1fd0855bb0abc7d97e44758d6ffed7882d2d0 (fixed)

Vendor states this is fixed in 7c9d9223802fbed4dee1ae301661bf346964c9d2 (fixed)

Vendor states this is fixed in 8c41abc11aa8438c9ed2d973f97e66674c0355df (fixed)

Vendor states this is fixed in 5.10 (unaffected)

Vendor states this is fixed in 5.10.234 (unaffected)

Vendor states this is fixed in 5.15.178 (unaffected)

Affected range stops below 5.4.290, so it looks safe — our inference, not a vendor statement

Vendor states this is fixed in 6.1.128 (unaffected)

Vendor states this is fixed in 6.12.12 (unaffected)

Vendor states this is fixed in 6.13.1 (unaffected)

Vendor states this is fixed in 6.14 (unaffected)

Vendor states this is fixed in 6.6.75 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references