cbcvebase.
CVE-2025-71265
published 2026-03-18

CVE-2025-71265: In the Linux kernel, the following vulnerability has been resolved: fs: ntfs3: fix infinite loop in attr_load_runs_range on inconsistent metadata We found an…

PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.12%
2.3th percentile
In the Linux kernel, the following vulnerability has been resolved: fs: ntfs3: fix infinite loop in attr_load_runs_range on inconsistent metadata We found an infinite loop bug in the ntfs3 file system that can lead to a Denial-of-Service (DoS) condition. A malformed NTFS image can cause an infinite loop when an attribute header indicates an empty run list, while directory entries reference it as containing actual data. In NTFS, setting evcn=-1 with svcn=0 is a valid way to represent an empty run list, and run_unpack() correctly handles this by checking if evcn + 1 equals svcn and returning early without parsing any run data. However, this creates a problem when there is metadata inconsistency, where the attribute header claims to be empty (evcn=-1) but the caller expects to read actual data. When run_unpack() immediately returns success upon seeing this condition, it leaves the runs_tree uninitialized with run->runs as a NULL. The calling function attr_load_runs_range() assumes that a successful return means that the runs were loaded and sets clen to 0, expecting the next run_lookup_entry() call to succeed. Because runs_tree remains uninitialized, run_lookup_entry() continues to fail, and the loop increments vcn by zero (vcn += 0), leading to an infinite loop. This patch adds a retry counter to detect when run_lookup_entry() fails consecutively after attr_load_runs_vcn(). If the run is still not found on the second attempt, it indicates corrupted metadata and returns -EINVAL, preventing the Denial-of-Service (DoS) vulnerability.

Affected

65 ranges· showing 25
VendorProductVersion rangeFixed in
debianlinux< linux 6.19.6-1 (forky)linux 6.19.6-1 (forky)
linuxlinux
linuxlinux>= be71b5cba2e6485e8959da7a9f9a44461a1bb074 < 6f07a590616ff5f57f7c041d98e463fad9e9f7636f07a590616ff5f57f7c041d98e463fad9e9f763
linuxlinux>= be71b5cba2e6485e8959da7a9f9a44461a1bb074 < a89bc96d5abd8a4a8d5d911884ea347efcdf460ba89bc96d5abd8a4a8d5d911884ea347efcdf460b
linuxlinux>= be71b5cba2e6485e8959da7a9f9a44461a1bb074 < af839013c70a24779f9d1afb1575952009312d38af839013c70a24779f9d1afb1575952009312d38
linuxlinux>= be71b5cba2e6485e8959da7a9f9a44461a1bb074 < 78b61f7eac37a63284774b147f38dd0be6cad43c78b61f7eac37a63284774b147f38dd0be6cad43c
linuxlinux>= be71b5cba2e6485e8959da7a9f9a44461a1bb074 < c0b43c45d45f59e7faad48675a50231a210c379bc0b43c45d45f59e7faad48675a50231a210c379b
linuxlinux>= be71b5cba2e6485e8959da7a9f9a44461a1bb074 < 3c3a6e951b9b53dab2ac460a655313cf04c4a10a3c3a6e951b9b53dab2ac460a655313cf04c4a10a
linuxlinux>= be71b5cba2e6485e8959da7a9f9a44461a1bb074 < 4b90f16e4bb5607fb35e7802eb67874038da46404b90f16e4bb5607fb35e7802eb67874038da4640
linuxlinux_kernel>= 0 < 6.19.6-16.19.6-1
linuxlinux_kernel>= 5.15 < 5.15.2025.15.202
linuxlinux_kernel>= 5.15.0 < 5.15.2025.15.202
linuxlinux_kernel>= 5.16 < 6.1.1656.1.165
linuxlinux_kernel>= 5.16.0 < 6.1.1656.1.165
linuxlinux_kernel>= 6.13 < 6.18.166.18.16
linuxlinux_kernel>= 6.13.0 < 6.18.166.18.16
linuxlinux_kernel>= 6.19 < 6.19.66.19.6
linuxlinux_kernel>= 6.19.0 < 6.19.66.19.6
linuxlinux_kernel>= 6.2 < 6.6.1286.6.128
linuxlinux_kernel>= 6.2.0 < 6.6.1286.6.128
linuxlinux_kernel>= 6.7 < 6.12.756.12.75
linuxlinux_kernel>= 6.7.0 < 6.12.756.12.75
msrcazl3_kernel_6.6.126.1-1_on_azure_linux_3.0
ubuntulinux
ubuntulinux-aws

CVSS provenance

nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
vendor_ubuntu8.8HIGH
vendor_msrc5.5MEDIUM
Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.