CVE-2026-64164
Gravedad:
Pendiente de análisis
Tipo:
No Disponible / Otro tipo
Fecha de publicación:
19/07/2026
Última modificación:
19/07/2026
Descripción
*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br />
<br />
btrfs: tracepoints: fix sleep while in atomic context in btrfs_sync_file()<br />
<br />
The trace event btrfs_sync_file() is called in an atomic context (all trace<br />
events are) and its call to dput(), which is needed due to the call to<br />
dget_parent(), can sleep, triggering a kernel splat.<br />
<br />
This can be reproduced by enabling the trace event and running btrfs/056<br />
from fstests for example. The splat shown in dmesg is the following:<br />
<br />
[53.919] BUG: sleeping function called from invalid context at fs/dcache.c:970<br />
[53.947] in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 32773, name: xfs_io<br />
[53.988] preempt_count: 2, expected: 0<br />
[53.967] RCU nest depth: 0, expected: 0<br />
[53.943] Preemption disabled at:<br />
[53.944] [] 0x0<br />
[54.078] CPU: 0 UID: 0 PID: 32773 Comm: xfs_io Tainted: G W 7.1.0-rc1-btrfs-next-232+ #1 PREEMPT(full)<br />
[54.070] Tainted: [W]=WARN<br />
[54.071] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.2-0-gea1b7a073390-prebuilt.qemu.org 04/01/2014<br />
[54.072] Call Trace:<br />
[54.074] <br />
[54.076] dump_stack_lvl+0x56/0x80<br />
[54.079] __might_resched.cold+0xd6/0x10f<br />
[54.072] dput.part.0+0x24/0x110<br />
[54.078] trace_event_raw_event_btrfs_sync_file+0x75/0x140 [btrfs]<br />
[54.089] btrfs_sync_file+0x1ed/0x530 [btrfs]<br />
[54.087] ? __handle_mm_fault+0x8ae/0xed0<br />
[54.089] btrfs_do_write_iter+0x172/0x210 [btrfs]<br />
[54.091] vfs_write+0x21f/0x450<br />
[54.094] __x64_sys_pwrite64+0x8d/0xc0<br />
[54.096] ? do_user_addr_fault+0x20c/0x670<br />
[54.099] do_syscall_64+0x60/0xf20<br />
[54.092] ? clear_bhb_loop+0x60/0xb0<br />
[54.094] entry_SYSCALL_64_after_hwframe+0x76/0x7e<br />
<br />
So stop using dget_parent() and dput() and access the parent dentry<br />
directly as dentry->d_parent. This is also what ext4 is doing in<br />
its equivalent trace event ext4_sync_file_enter().
Impacto
Referencias a soluciones, herramientas e información
- https://git.kernel.org/stable/c/0a96d9a85cd2240481297156b9bb72e10b7a8036
- https://git.kernel.org/stable/c/12a0487945c09760a5968d9333383014ea294117
- https://git.kernel.org/stable/c/26b2290baaf6da6add0f782a100766e686a33f4f
- https://git.kernel.org/stable/c/4361954f0e158af0530caa1e57f12b531be4658f
- https://git.kernel.org/stable/c/6279992c9ba2774901c9d4dd4a481162e2534714
- https://git.kernel.org/stable/c/c32a7e0e3c73c1c0768556a56bd78de9f7b83780
- https://git.kernel.org/stable/c/c73370c677646e86fc4b1780fb07027bdf847375
- https://git.kernel.org/stable/c/d78b0a80eac36879ef5478707135c446920e134b



