CVE-2026-72164

HIGHCVSS 7.8/10EPSS 0.21%

Last modified

CVE-2026-72164 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: ocfs2: avoid moving extents to occupied clusters For non-auto OCFS2_IOC_MOVE_EXT operations, userspace supplies a physical me_goal. ocfs2_move_extent() initializes new_phys_cpos from that goal and expects ocfs2_probe_alloc_group() to replace it with a free run in the target block group. The probe currently leaves *phys_cpos unchanged if the scan reaches the end of the group without finding a free run. EPSS estimates a 0.21% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: ocfs2: avoid moving extents to occupied clusters For non-auto OCFS2_IOC_MOVE_EXT operations, userspace supplies a physical me_goal. ocfs2_move_extent() initializes new_phys_cpos from that goal and expects ocfs2_probe_alloc_group() to replace it with a free run in the target block group. The probe currently leaves *phys_cpos unchanged if the scan reaches the end of the group without finding a free run. An occupied goal at the last bit can therefore survive the probe and be passed to __ocfs2_move_extent(), which copies file data into a cluster still owned by another inode before the bitmap is updated. When the probe does find a free run, it also subtracts move_len from the ending bit. The start of an N-bit run ending at i is i - N + 1, so the current calculation can report the bit immediately before the free run. Clear *phys_cpos before scanning and use the correct free-run start. Callers already treat a zero result as -ENOSPC, so failed probes no longer continue with an occupied caller-controlled goal.

Metrics

CVSS 3.1
7.8/10

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability
0.21%

11.6th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= e6b5859cccfa0fec02f3c5b1069481efc7186f47, < 3112afebf2a76e522fbaabcbb0c47aafbdc35932; >= e6b5859cccfa0fec02f3c5b1069481efc7186f47, < 35486b291b8fbde6c4d0b1c79e565c6260d3329d; >= e6b5859cccfa0fec02f3c5b1069481efc7186f47, < 19f7b04924b20b81dabbeed19d5542792ba5b6d6; >= e6b5859cccfa0fec02f3c5b1069481efc7186f47, < e281d892ce5870a50fdc718cb3bfc3dd5b62c728; >= e6b5859cccfa0fec02f3c5b1069481efc7186f47, < 0d0c5c17b18bdbc592ac26ab4d1de7e3dbf9be1e; >= e6b5859cccfa0fec02f3c5b1069481efc7186f47, < d5d5a21fb33cd9b963aea99da81e4dacd452cd95; >= e6b5859cccfa0fec02f3c5b1069481efc7186f47, < 4d1953d3aeb4a7f6623083e1839068ee1c157db2; >= e6b5859cccfa0fec02f3c5b1069481efc7186f47, < 22920541c35a9f23f219038ba5874c843a7c4419
LinuxLinux3.0

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-72164?
In the Linux kernel, the following vulnerability has been resolved: ocfs2: avoid moving extents to occupied clusters For non-auto OCFS2_IOC_MOVE_EXT operations, userspace supplies a physical me_goal. ocfs2_move_extent() initializes new_phys_cpos from that goal and expects ocfs2_probe_alloc_group() to replace it with a free run in the target block group. The probe currently leaves *phys_cpos unchanged if the scan reaches the end of the group without finding a free run. An occupied goal at the last bit can therefore survive the probe and be passed to __ocfs2_move_extent(), which copies file data into a cluster still owned by another inode before the bitmap is updated. When the probe does find a free run, it also subtracts move_len from the ending bit. The start of an N-bit run ending at i is i - N + 1, so the current calculation can report the bit immediately before the free run. Clear *phys_cpos before scanning and use the correct free-run start. Callers already treat a zero result as -ENOSPC, so failed probes no longer continue with an occupied caller-controlled goal.
How severe is CVE-2026-72164?
CVE-2026-72164 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.21% probability of exploitation in the next 30 days.
How do I fix CVE-2026-72164?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-72164?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST