In the Linux kernel, the following vulnerability has been resolved: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() Fix a race… (CVE-2025-68261)
A race condition vulnerability in the Linux kernel's ext4 filesystem was resolved by adding i_data_sem protection in the ext4_destroy_inline_data_nolock() function. The flaw allowed a race between inline data destruction and block mapping, potentially causing a kernel BUG and system crash. This occurs because ext4_ind_map_blocks() could be called with an inode flagged as EXT4_INODE_EXTENTS without proper synchronization, triggering an assertion failure and invalid opcode exception.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel ext4 filesystem involves a race condition between the destruction of inline data and block mapping. Specifically, ext4_destroy_inline_data_nolock() modifies the inode data layout by clearing the EXT4_INODE_INLINE_DATA flag and setting EXT4_INODE_EXTENTS. Without the i_data_sem semaphore protection, concurrent execution of ext4_map_blocks() may observe the inode with the EXT4_INODE_EXTENTS flag and call ext4_ind_map_blocks(), which triggers an assertion failure and kernel BUG. This can lead to system instability or crash. The issue was resolved by adding i_data_sem protection to ext4_destroy_inline_data_nolock(), preventing the race condition.
Potential Impact
This vulnerability can cause a denial of service by crashing the kernel due to a race condition in ext4 filesystem operations. It does not impact confidentiality or integrity but results in system instability and unmounting of the filesystem. There is no indication of remote code execution or privilege escalation from the provided data.
Mitigation Recommendations
A fix has been implemented in the Linux kernel by adding i_data_sem protection in ext4_destroy_inline_data_nolock() to prevent the race condition. Users should update to the fixed kernel version once available. Patch status is not explicitly confirmed in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the current remediation guidance.
In the Linux kernel, the following vulnerability has been resolved: ext4: add i_data_sem protection in ext4_destroy_inline_data_nolock() Fix a race… (CVE-2025-68261)
Description
A race condition vulnerability in the Linux kernel's ext4 filesystem was resolved by adding i_data_sem protection in the ext4_destroy_inline_data_nolock() function. The flaw allowed a race between inline data destruction and block mapping, potentially causing a kernel BUG and system crash. This occurs because ext4_ind_map_blocks() could be called with an inode flagged as EXT4_INODE_EXTENTS without proper synchronization, triggering an assertion failure and invalid opcode exception.
CVSS v3.1
Score 7.5high
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel ext4 filesystem involves a race condition between the destruction of inline data and block mapping. Specifically, ext4_destroy_inline_data_nolock() modifies the inode data layout by clearing the EXT4_INODE_INLINE_DATA flag and setting EXT4_INODE_EXTENTS. Without the i_data_sem semaphore protection, concurrent execution of ext4_map_blocks() may observe the inode with the EXT4_INODE_EXTENTS flag and call ext4_ind_map_blocks(), which triggers an assertion failure and kernel BUG. This can lead to system instability or crash. The issue was resolved by adding i_data_sem protection to ext4_destroy_inline_data_nolock(), preventing the race condition.
Potential Impact
This vulnerability can cause a denial of service by crashing the kernel due to a race condition in ext4 filesystem operations. It does not impact confidentiality or integrity but results in system instability and unmounting of the filesystem. There is no indication of remote code execution or privilege escalation from the provided data.
Mitigation Recommendations
A fix has been implemented in the Linux kernel by adding i_data_sem protection in ext4_destroy_inline_data_nolock() to prevent the race condition. Users should update to the fixed kernel version once available. Patch status is not explicitly confirmed in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the current remediation guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-q2j6-qrc9-gxpm
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2025-68261"]
- Database Specific Severity
- HIGH
- Cvss Version
- 3.1
Threat ID: 6a6b72d39c2644c7f84782e6
Added to database: 07/30/2026, 15:50:43 UTC
Last enriched: 07/30/2026, 18:40:12 UTC
Last updated: 09/10/2026, 19:38:48 UTC
Views: 28
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.