CVE-2025-71180

In the Linux kernel, the following vulnerability has been resolved: counter: interrupt-cnt: Drop IRQF_NO_THREAD flag An IRQ handler can either be IRQF_NO_THREAD or acquire spinlock_t, as CONFIG_PROVE_RAW_LOCK_NESTING warns: ============================= [ BUG: Invalid wait context ] 6.18.0-rc1+git... #1 ----------------------------- some-user-space-process/1251 is trying to lock: (&counter->events_list_lock){....}-{3:3}, at: counter_push_event [counter] other info that might help us debug this: context-{2:2} no locks held by some-user-space-process/.... stack backtrace: CPU: 0 UID: 0 PID: 1251 Comm: some-user-space-process 6.18.0-rc1+git... #1 PREEMPT Call trace: show_stack (C) dump_stack_lvl dump_stack __lock_acquire lock_acquire _raw_spin_lock_irqsave counter_push_event [counter] interrupt_cnt_isr [interrupt_cnt] __handle_irq_event_percpu handle_irq_event handle_simple_irq handle_irq_desc generic_handle_domain_irq gpio_irq_handler handle_irq_desc generic_handle_domain_irq gic_handle_irq call_on_irq_stack do_interrupt_handler el0_interrupt __el0_irq_handler_common el0t_64_irq_handler el0t_64_irq ... and Sebastian correctly points out. Remove IRQF_NO_THREAD as an alternative to switching to raw_spinlock_t, because the latter would limit all potential nested locks to raw_spinlock_t only.
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.13:-:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc8:*:*:*:*:*:*

History

25 Mar 2026, 19:45

Type Values Removed Values Added
CWE NVD-CWE-noinfo
First Time Linux
Linux linux Kernel
Summary
  • (es) En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta: counter: interrupt-cnt: Eliminar el flag IRQF_NO_THREAD Un manejador de IRQ puede ser IRQF_NO_THREAD o adquirir un spinlock_t, como advierte CONFIG_PROVE_RAW_LOCK_NESTING: ============================= [ BUG: Contexto de espera inválido ] 6.18.0-rc1+git... #1 ----------------------------- some-user-space-process/1251 está intentando bloquear: (&counter->events_list_lock){....}-{3:3}, at: counter_push_event [counter] otra información que podría ayudarnos a depurar esto: context-{2:2} ningún bloqueo mantenido por some-user-space-process/.... rastreo de pila: CPU: 0 UID: 0 PID: 1251 Comm: some-user-space-process 6.18.0-rc1+git... #1 PREEMPT Traza de llamada: show_stack (C) dump_stack_lvl dump_stack __lock_acquire lock_acquire _raw_spin_lock_irqsave counter_push_event [counter] interrupt_cnt_isr [interrupt_cnt] __handle_irq_event_percpu handle_irq_event handle_simple_irq handle_irq_desc generic_handle_domain_irq gpio_irq_handler handle_irq_desc generic_handle_domain_irq gic_handle_irq call_on_irq_stack do_interrupt_handler el0_interrupt __el0_irq_handler_common el0t_64_irq_handler el0t_64_irq ... y Sebastian señala correctamente. Eliminar IRQF_NO_THREAD como alternativa a cambiar a raw_spinlock_t, porque esto último limitaría todos los posibles bloqueos anidados solo a raw_spinlock_t.
CVSS v2 : unknown
v3 : unknown
v2 : unknown
v3 : 5.5
CPE cpe:2.3:o:linux:linux_kernel:6.19:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.13:-:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc8:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc4:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc6:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc5:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:6.19:rc7:*:*:*:*:*:*
References () https://git.kernel.org/stable/c/1c5a3175aecf82cd86dfcbef2a23e8b26d8d8e7c - () https://git.kernel.org/stable/c/1c5a3175aecf82cd86dfcbef2a23e8b26d8d8e7c - Patch
References () https://git.kernel.org/stable/c/23f9485510c338476b9735d516c1d4aacb810d46 - () https://git.kernel.org/stable/c/23f9485510c338476b9735d516c1d4aacb810d46 - Patch
References () https://git.kernel.org/stable/c/425886b1f8304621b3f16632b274357067d5f13f - () https://git.kernel.org/stable/c/425886b1f8304621b3f16632b274357067d5f13f - Patch
References () https://git.kernel.org/stable/c/49a66829dd3653695e60d7cae13521d131362fcd - () https://git.kernel.org/stable/c/49a66829dd3653695e60d7cae13521d131362fcd - Patch
References () https://git.kernel.org/stable/c/51d2e5d6491447258cb39ff1deb93df15d3c23cb - () https://git.kernel.org/stable/c/51d2e5d6491447258cb39ff1deb93df15d3c23cb - Patch
References () https://git.kernel.org/stable/c/ef668c9a2261ec9287faba6e6ef05a98b391aa2b - () https://git.kernel.org/stable/c/ef668c9a2261ec9287faba6e6ef05a98b391aa2b - Patch

31 Jan 2026, 12:16

Type Values Removed Values Added
New CVE

Information

Published : 2026-01-31 12:16

Updated : 2026-03-25 19:45


NVD link : CVE-2025-71180

Mitre link : CVE-2025-71180

CVE.ORG link : CVE-2025-71180


JSON object : View

Products Affected

linux

  • linux_kernel