VYPR
Unrated severityNVD Advisory· Published Dec 4, 2025· Updated Apr 15, 2026

CVE-2025-40233

CVE-2025-40233

Description

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

ocfs2: clear extent cache after moving/defragmenting extents

The extent map cache can become stale when extents are moved or defragmented, causing subsequent operations to see outdated extent flags. This triggers a BUG_ON in ocfs2_refcount_cal_cow_clusters().

The problem occurs when: 1. copy_file_range() creates a reflinked extent with OCFS2_EXT_REFCOUNTED 2. ioctl(FITRIM) triggers ocfs2_move_extents() 3. __ocfs2_move_extents_range() reads and caches the extent (flags=0x2) 4. ocfs2_move_extent()/ocfs2_defrag_extent() calls __ocfs2_move_extent() which clears OCFS2_EXT_REFCOUNTED flag on disk (flags=0x0) 5. The extent map cache is not invalidated after the move 6. Later write() operations read stale cached flags (0x2) but disk has updated flags (0x0), causing a mismatch 7. BUG_ON(!(rec->e_flags & OCFS2_EXT_REFCOUNTED)) triggers

Fix by clearing the extent map cache after each extent move/defrag operation in __ocfs2_move_extents_range(). This ensures subsequent operations read fresh extent data from disk.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

A stale extent map cache in the Linux kernel's ocfs2 filesystem can cause a BUG_ON crash after reflink, FITRIM, and defrag operations, fixed by clearing the cache after moves.

Vulnerability

Overview

CVE-2025-40233 is a bug in the Linux kernel's ocfs2 (Oracle Cluster File System) that arises when the extent map cache is not cleared after extents are moved or defragmented. The root cause is a stale cache that retains old extent flags after a move operation, leading to a mismatch between cached and on-disk flags. This mismatch triggers a BUG_ON assertion in ocfs2_refcount_cal_cow_clusters(), causing a kernel panic [1][2][3].

Attack

Vector and Prerequisites

The bug can be triggered through a sequence of legitimate syscalls. First, copy_file_range() creates a reflinked extent, setting the OCFS2_EXT_REFCOUNTED flag. Next, an ioctl(FITRIM) call triggers ocfs2_move_extents(), which reads the extent into the cache. During __ocfs2_move_extent(), the move/defrag routine clears the REFCOUNTED flag on disk but neglects to invalidate the cached entry. A subsequent write operation then reads the stale cached flag, causing the BUG_ON [1]. No special privileges beyond access to the ocfs2 filesystem are needed, and the attack surface is local, requiring only the ability to perform file operations on the affected filesystem.

Impact

Successful exploitation results in a denial of service (kernel crash/BUG_ON). The impact) on any system using ocfs2 that performs reflink and then FITRIM/defrag operations on the same file. There is no evidence of memory corruption or privilege escalation, but the crash can disrupt services relying on the ocfs2 filesystem.

Mitigation

Status

The fix has been applied to the Linux kernel stable tree in commit e92af7737a94, and another stable commit 78a63493f8e3. It clears the extent map cache after each extent move or defrag operation in __ocfs2_move_extents_range(), ensuring that subsequent reads fetch the current on-disk flags. Users should update their kernel to a version containing these commits. No workarounds are mentioned [1][2][3].

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

3

Patches

8

Vulnerability mechanics

Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.

References

8

News mentions

0

No linked articles in our index yet.