Linux Kernel up to 7.1.4 ocfs2 ocfs2_move_extent race condition

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.4$0-$5k0.47

Summaryinfo

A vulnerability, which was classified as very critical, has been found in Linux Kernel up to 7.1.4. This affects the function ocfs2_move_extent of the component ocfs2. This manipulation causes race condition. This vulnerability is handled as CVE-2026-72164. It is possible to launch the attack on the local host. There is not any exploit available.

Detailsinfo

A vulnerability classified as very critical was found in Linux Kernel up to 7.1.4. Affected by this vulnerability is the function ocfs2_move_extent of the component ocfs2. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-72164 since 08/09/2026. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/15/2026).

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc1 eliminates this vulnerability. Applying the patch 3112afebf2a76e522fbaabcbb0c47aafbdc35932/35486b291b8fbde6c4d0b1c79e565c6260d3329d/19f7b04924b20b81dabbeed19d5542792ba5b6d6/e281d892ce5870a50fdc718cb3bfc3dd5b62c728/0d0c5c17b18bdbc592ac26ab4d1de7e3dbf9be1e/d5d5a21fb33cd9b963aea99da81e4dacd452cd95/4d1953d3aeb4a7f6623083e1839068ee1c157db2/22920541c35a9f23f219038ba5874c843a7c4419 is able to eliminate this problem.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.4

VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Race condition
CWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.261/5.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc1
Patch: 3112afebf2a76e522fbaabcbb0c47aafbdc35932/35486b291b8fbde6c4d0b1c79e565c6260d3329d/19f7b04924b20b81dabbeed19d5542792ba5b6d6/e281d892ce5870a50fdc718cb3bfc3dd5b62c728/0d0c5c17b18bdbc592ac26ab4d1de7e3dbf9be1e/d5d5a21fb33cd9b963aea99da81e4dacd452cd95/4d1953d3aeb4a7f6623083e1839068ee1c157db2/22920541c35a9f23f219038ba5874c843a7c4419

Timelineinfo

08/09/2026 CVE reserved
08/15/2026 +6 days Advisory disclosed
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-72164 (🔒)
GCVE (CVE): GCVE-0-2026-72164
GCVE (VulDB): GCVE-100-390601

Entryinfo

Created: 08/15/2026 13:12
Changes: 08/15/2026 13:12 (59)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you want to use VulDB in your project?

Use the official API to access entries easily!