CVE-2026-72164

ocfs2: avoid moving extents to occupied clusters

HIGH
7.8
CVSS Score
Published: August 15, 2026 at 05:53 AM UTC
Updated: October 16, 2026 at 07:17 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
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

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.

Affected

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

3.0e6b5859cccfa0fec02f3c5b1069481efc7186f47
Vendor states this is fixed in 0d0c5c17b18bdbc592ac26ab4d1de7e3dbf9be1e (fixed)
Vendor states this is fixed in 19f7b04924b20b81dabbeed19d5542792ba5b6d6 (fixed)
Vendor states this is fixed in 22920541c35a9f23f219038ba5874c843a7c4419 (fixed)
Vendor states this is fixed in 3112afebf2a76e522fbaabcbb0c47aafbdc35932 (fixed)
Vendor states this is fixed in 35486b291b8fbde6c4d0b1c79e565c6260d3329d (fixed)
Vendor states this is fixed in 4d1953d3aeb4a7f6623083e1839068ee1c157db2 (fixed)
Vendor states this is fixed in d5d5a21fb33cd9b963aea99da81e4dacd452cd95 (fixed)
Vendor states this is fixed in e281d892ce5870a50fdc718cb3bfc3dd5b62c728 (fixed)
Vendor states this is fixed in 3.0 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card