CVE-2025-68264 Affecting kernel-modules-extra package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CENTOS8-KERNELMODULESEXTRA-14511062
- published18 Dec 2025
- disclosed16 Dec 2025
Introduced: 16 Dec 2025
NewCVE-2025-68264 (opens in a new tab)How to fix?
There is no fixed version for Centos:8 kernel-modules-extra.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-modules-extra package and not the kernel-modules-extra package as distributed by Centos.
See How to fix? for Centos:8 relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
ext4: refresh inline data size before write operations
The cached ei->i_inline_size can become stale between the initial size check and when ext4_update_inline_data()/ext4_create_inline_data() use it. Although ext4_get_max_inline_size() reads the correct value at the time of the check, concurrent xattr operations can modify i_inline_size before ext4_write_lock_xattr() is acquired.
This causes ext4_update_inline_data() and ext4_create_inline_data() to work with stale capacity values, leading to a BUG_ON() crash in ext4_write_inline_data():
kernel BUG at fs/ext4/inline.c:1331! BUG_ON(pos + len > EXT4_I(inode)->i_inline_size);
The race window:
- ext4_get_max_inline_size() reads i_inline_size = 60 (correct)
- Size check passes for 50-byte write
- [Another thread adds xattr, i_inline_size changes to 40]
- ext4_write_lock_xattr() acquires lock
- ext4_update_inline_data() uses stale i_inline_size = 60
- Attempts to write 50 bytes but only 40 bytes actually available
- BUG_ON() triggers
Fix this by recalculating i_inline_size via ext4_find_inline_data_nolock() immediately after acquiring xattr_sem. This ensures ext4_update_inline_data() and ext4_create_inline_data() work with current values that are protected from concurrent modifications.
This is similar to commit a54c4613dac1 ("ext4: fix race writing to an inline_data file while its xattrs are changing") which fixed i_inline_off staleness. This patch addresses the related i_inline_size staleness issue.
References
- https://access.redhat.com/security/cve/CVE-2025-68264
- https://git.kernel.org/stable/c/210ac60a86a3ad2c76ae60e0dc71c34af6e7ea0b
- https://git.kernel.org/stable/c/58df743faf21ceb1880f930aa5dd428e2a5e415d
- https://git.kernel.org/stable/c/892e1cf17555735e9d021ab036c36bc7b58b0e3b
- https://git.kernel.org/stable/c/ca43ea29b4c4d2764aec8a26cffcfb677a871e6e