CVE-2026-92500

/// Technical description

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

ext4: use fsdata to track inline data write state and fix race

Instead of checking the live inode state (ext4_has_inline_data(inode)

and ext4_test_inode_state(inode, EXT4_STATE_MAY_INLINE_DATA)) in the

write_end handlers, use the fsdata parameter of the address space

operations to explicitly pass down the state in which write_begin

prepared the write.

A concurrent thread (such as ext4_page_mkwrite()) can convert the

inline data to an extent between write_begin and write_end. If this

happens, the write_end handlers would previously miss the inline

write_end path and fall through to extent-based write_end logic.

However, since block buffers were never allocated in write_begin,

this resulted in NULL pointer dereferences or data loss because

folio_buffers(folio) was NULL.

Define EXT4_WRITE_DATA_INLINE (4) as a bit flag (Bit 2), treating

fsdata as bitwise flags rather than mutually exclusive enums to keep

states of the

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References