Skip to main content

Linux Kernel CVE-2025-68261

HIGH
2025-12-16 416baaa9-dc9f-4396-8d5f-8c081fb06d67
7.5
CVSS 3.1 · Vendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Share

Severity by source

Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67) PRIMARY
7.5 HIGH
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
vuln.today AI
4.7 MEDIUM

Local write access to an ext4 volume is needed (AV:L, PR:L), success requires winning a timing race (AC:H), and impact is a kernel panic only (A:H, C:N/I:N).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
SUSE
5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Red Hat
5.5 MEDIUM
qualitative

Primary rating from Vendor (416baaa9-dc9f-4396-8d5f-8c081fb06d67).

CVSS VectorVendor: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

4
Analysis Generated
Jul 30, 2026 - 06:41 vuln.today
CVSS changed
Jul 30, 2026 - 06:37 NVD
7.5 (HIGH)
CVE Published
Dec 16, 2025 - 15:15 cve.org
HIGH 7.5
CVE Published
Dec 16, 2025 - 15:15 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

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 between inline data destruction and block mapping.

The function ext4_destroy_inline_data_nolock() changes the inode data layout by clearing EXT4_INODE_INLINE_DATA and setting EXT4_INODE_EXTENTS. At the same time, another thread may execute ext4_map_blocks(), which tests EXT4_INODE_EXTENTS to decide whether to call ext4_ext_map_blocks() or ext4_ind_map_blocks().

Without i_data_sem protection, ext4_ind_map_blocks() may receive inode with EXT4_INODE_EXTENTS flag and triggering assert.

kernel BUG at fs/ext4/indirect.c:546! EXT4-fs (loop2): unmounting filesystem. invalid opcode: 0000 [#1] PREEMPT SMP KASAN NOPTI Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 RIP: 0010:ext4_ind_map_blocks.cold+0x2b/0x5a fs/ext4/indirect.c:546

Call Trace: <TASK> ext4_map_blocks+0xb9b/0x16f0 fs/ext4/inode.c:681 _ext4_get_block+0x242/0x590 fs/ext4/inode.c:822 ext4_block_write_begin+0x48b/0x12c0 fs/ext4/inode.c:1124 ext4_write_begin+0x598/0xef0 fs/ext4/inode.c:1255 ext4_da_write_begin+0x21e/0x9c0 fs/ext4/inode.c:3000 generic_perform_write+0x259/0x5d0 mm/filemap.c:3846 ext4_buffered_write_iter+0x15b/0x470 fs/ext4/file.c:285 ext4_file_write_iter+0x8e0/0x17f0 fs/ext4/file.c:679 call_write_iter include/linux/fs.h:2271 [inline] do_iter_readv_writev+0x212/0x3c0 fs/read_write.c:735 do_iter_write+0x186/0x710 fs/read_write.c:861 vfs_iter_write+0x70/0xa0 fs/read_write.c:902 iter_file_splice_write+0x73b/0xc90 fs/splice.c:685 do_splice_from fs/splice.c:763 [inline] direct_splice_actor+0x10f/0x170 fs/splice.c:950 splice_direct_to_actor+0x33a/0xa10 fs/splice.c:896 do_splice_direct+0x1a9/0x280 fs/splice.c:1002 do_sendfile+0xb13/0x12c0 fs/read_write.c:1255 __do_sys_sendfile64 fs/read_write.c:1323 [inline] __se_sys_sendfile64 fs/read_write.c:1309 [inline] __x64_sys_sendfile64+0x1cf/0x210 fs/read_write.c:1309 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x35/0x80 arch/x86/entry/common.c:81 entry_SYSCALL_64_after_hwframe+0x6e/0xd8

AnalysisAI

Local denial-of-service in the Linux kernel ext4 filesystem allows a low-privileged user to crash the system by racing inline-data destruction against block mapping. The function ext4_destroy_inline_data_nolock() flips an inode from EXT4_INODE_INLINE_DATA to EXT4_INODE_EXTENTS without holding i_data_sem, so a concurrent ext4_map_blocks() can enter ext4_ind_map_blocks() on an inode that already advertises extents, tripping a BUG_ON at fs/ext4/indirect.c:546 and panicking the kernel. No public exploit identified at time of analysis; EPSS is low (0.18%, 8th percentile) and the flaw is availability-only (kernel oops), not information disclosure despite the input tag.

Technical ContextAI

The bug lives in ext4's inline-data feature, which stores very small file contents directly inside the inode's i_blocks/xattr area instead of in separate data blocks. When a file outgrows inline capacity, ext4_destroy_inline_data_nolock() migrates the inode to the standard on-disk layout by clearing the EXT4_INODE_INLINE_DATA flag and setting EXT4_INODE_EXTENTS. ext4_map_blocks() reads EXT4_INODE_EXTENTS to dispatch either to the extent mapper (ext4_ext_map_blocks) or the legacy indirect-block mapper (ext4_ind_map_blocks). The two code paths were not serialized by the inode's i_data_sem read/write semaphore, creating a classic data race (CWE-362, race condition / concurrent state transition). The indirect mapper defensively asserts that the extents flag is NOT set; observing it mid-transition triggers the BUG_ON. The call chain in the report (sendfile64 → splice → ext4_da_write_begin → ext4_map_blocks → ext4_ind_map_blocks.cold) shows a delayed-allocation buffered write reaching the mapper during the layout switch. CWE is listed as N/A in the input but the root cause is unambiguously an unlocked concurrent state transition.

Affected ProductsAI

The Linux kernel's ext4 filesystem is affected on any version that supports inline data and lacks i_data_sem protection in ext4_destroy_inline_data_nolock(); the input provides no CPE strings, so exact version boundaries are not enumerable from the data. Multiple stable-branch fix commits are referenced (git.kernel.org/stable/c/0cd8feea..., 144c48da..., 22a76b08..., 5b266cf6..., 5cad18e5..., 61e03dc3..., b322bac9..., ba8aeff2...), indicating the fix was backported across several maintained stable series. Siemens has issued product advisory SSA-019113 (https://cert-portal.siemens.com/productcert/html/ssa-019113.html) for its Linux-based products that embed the affected kernel.

RemediationAI

Update to a Linux kernel build that includes the ext4 fix adding i_data_sem protection in ext4_destroy_inline_data_nolock(); the upstream fix is available as the stable commits listed (e.g. git.kernel.org/stable/c/0cd8feea8777f8d9b9a862b89c688b049a5c8475 and its sibling backports 144c48da..., 22a76b08..., 5b266cf6..., 5cad18e5..., 61e03dc3..., b322bac9..., ba8aeff2...), so apply the vendor kernel package that has backported it. Released tagged version numbers are not enumerated in the input, so confirm the fixed package version with your distribution's advisory. For Siemens deployments follow SSA-019113 (https://cert-portal.siemens.com/productcert/html/ssa-019113.html). As a compensating control where patching must wait, avoid mounting untrusted ext4 images and restrict local write access to ext4 filesystems for untrusted users, since exploitation requires local file writes; note this does not fully close the race for legitimate local workloads. Disabling the ext4 inline_data feature at mkfs time on new filesystems removes the vulnerable transition path but cannot be toggled on existing populated filesystems and changes small-file storage behavior.

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
Container suse/sl-micro/6.0/baremetal-os-container:latest Container suse/sl-micro/6.0/toolbox:latest Affected
Container suse/sl-micro/6.0/base-os-container:2.1.3-7.95 Image SL-Micro Image SLE-Micro Image SLE-Micro-Azure Image SLE-Micro-BYOS Image SLE-Micro-BYOS-Azure Image SLE-Micro-BYOS-EC2 Image SLE-Micro-BYOS-GCE Image SLE-Micro-EC2 Image SLE-Micro-GCE Affected
Container suse/sl-micro/6.0/kvm-os-container:2.1.3-6.115 Affected
Container suse/sl-micro/6.0/rt-os-container:2.1.3-7.146 Affected
Container suse/sl-micro/6.1/base-os-container:2.2.1-5.80 Image SL-Micro-Azure Image SL-Micro-BYOS-Azure Image SL-Micro-BYOS-EC2 Image SL-Micro-BYOS-GCE Image SL-Micro-EC2 Image SUSE-Multi-Linux-Manager-Proxy-BYOS-Azure Image SUSE-Multi-Linux-Manager-Proxy-BYOS-EC2 Image SUSE-Multi-Linux-Manager-Proxy-BYOS-GCE Image SUSE-Multi-Linux-Manager-Server-Azure-llc Image SUSE-Multi-Linux-Manager-Server-Azure-ltd Image SUSE-Multi-Linux-Manager-Server-BYOS-Azure Image SUSE-Multi-Linux-Manager-Server-BYOS-EC2 Image SUSE-Multi-Linux-Manager-Server-BYOS-GCE Image SUSE-Multi-Linux-Manager-Server-EC2-llc Image SUSE-Multi-Linux-Manager-Server-EC2-ltd Affected

Share

CVE-2025-68261 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy