CVE-2026-53085

*** Pendiente de traducción *** In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> bpf: fix mm lifecycle in open-coded task_vma iterator<br /> <br /> The open-coded task_vma iterator reads task-&gt;mm locklessly and acquires<br /> mmap_read_trylock() but never calls mmget(). If the task exits<br /> concurrently, the mm_struct can be freed as it is not<br /> SLAB_TYPESAFE_BY_RCU, resulting in a use-after-free.<br /> <br /> Safely read task-&gt;mm with a trylock on alloc_lock and acquire an mm<br /> reference. Drop the reference via bpf_iter_mmput_async() in _destroy()<br /> and error paths. bpf_iter_mmput_async() is a local wrapper around<br /> mmput_async() with a fallback to mmput() on !CONFIG_MMU.<br /> <br /> Reject irqs-disabled contexts (including NMI) up front. Operations used<br /> by _next() and _destroy() (mmap_read_unlock, bpf_iter_mmput_async)<br /> take spinlocks with IRQs disabled (pool-&gt;lock, pi_lock). Running from<br /> NMI or from a tracepoint that fires with those locks held could<br /> deadlock.<br /> <br /> A trylock on alloc_lock is used instead of the blocking task_lock()<br /> (get_task_mm) to avoid a deadlock when a softirq BPF program iterates<br /> a task that already holds its alloc_lock on the same CPU.