Skip to content
Fencer Vulns
medium 5.5

CVE-2025-21667 json

iomap: avoid avoid truncating 64-bit offset to 32 bits

published 2025-01-31 21 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-2616

cvss
5.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

iomap: avoid avoid truncating 64-bit offset to 32 bits

on 32-bit kernels, iomap_write_delalloc_scan() was inadvertently using a 32-bit position due to folio_next_index() returning an unsigned long. This could lead to an infinite loop when writing to an xfs filesystem.

Patch / fix

  • Linux Linux 6.1.127, 6.6.74, 6.12.11, 6.13
  • linux Debian 12 6.1.128-1
  • linux Debian 14, Debian 13 6.12.11-1

debian advisories DEBIAN-CVE-2025-21667

  • linux Ubuntu 24.04 LTS 6.8.0-62.65
  • linux-aws Ubuntu 24.04 LTS 6.8.0-1030.32
  • linux-gcp Ubuntu 24.04 LTS 6.8.0-1031.33
  • linux-gke Ubuntu 24.04 LTS 6.8.0-1026.30
  • linux-ibm Ubuntu 24.04 LTS 6.8.0-1027.27
  • linux-azure Ubuntu 24.04 LTS 6.8.0-1030.35
  • linux-gkeop Ubuntu 24.04 LTS 6.8.0-1013.15
  • linux-raspi Ubuntu 24.04 LTS 6.8.0-1029.33

ubuntu advisories UBUNTU-CVE-2025-21667

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • kernel-source Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1
  • kernel-default Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1
  • kernel-kvmsmall Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1
  • kernel-default-base Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1.21.6
  • kernel-livepatch-MICRO-6-0_Update_6 Linux Micro 6.1, Linux Micro 6.0 1-3.1
  • kernel-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1
  • kernel-source-rt Linux Micro 6.1, Linux Micro 6.0 6.4.0-28.1
  • kernel-livepatch-MICRO-6-0-RT_Update_6 Linux Micro 6.1, Linux Micro 6.0 1-3.1

suse advisories SUSE-SU-2025:20192-1SUSE-SU-2025:20270-1SUSE-SU-2025:20190-1SUSE-SU-2025:20260-1SUSE-SU-2025:0955-1SUSE-SU-2025:0856-1

  • kernel Azure Linux 3.0 6.6.76.1-1

azure linux advisories AZL-56351

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-21667 updated cvss 5.5

kernel: iomap: avoid avoid truncating 64-bit offset to 32 bits

  • Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +82 more Red Hat Enterprise Linux 10 kernel
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
13 mo ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Linux Linux

Classification

Weakness
  • CWE-835 Loop with Unreachable Exit Condition
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.