Medium 5.5Published Jan 31, 2026

CVE-2025-71180counter: interrupt-cnt: Drop IRQF_NO_THREAD flag

Updated under an hour ago (Oct 28, 2026, 8:40 AM ET)

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for Linux

Exploited in the last 30 days

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.

CVSS: 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE): Not given
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: Linux
NVD analysis: Analyzed
Record last updated: May 11, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

Linux Linux linux:linux (from the name)	from a55ebd47f21f6f0472766fb52c973849e31d1466 before ef668c9a2261ec9287faba6e6ef05a98b391aa2b; from a55ebd47f21f6f0472766fb52c973849e31d1466 before 51d2e5d6491447258cb39ff1deb93df15d3c23cb; from a55ebd47f21f6f0472766fb52c973849e31d1466 before 1c5a3175aecf82cd86dfcbef2a23e8b26d8d8e7c; from a55ebd47f21f6f0472766fb52c973849e31d1466 before 49a66829dd3653695e60d7cae13521d131362fcd; from a55ebd47f21f6f0472766fb52c973849e31d1466 before 425886b1f8304621b3f16632b274357067d5f13f; from a55ebd47f21f6f0472766fb52c973849e31d1466 before 23f9485510c338476b9735d516c1d4aacb810d46	CNA record
linux linux_kernel linux:linux_kernel	from 5.13.1 before 5.15.198; from 5.16 before 6.1.161; from 6.2 before 6.6.121; from 6.7 before 6.12.66; from 6.13 before 6.18.6; 5.13; 6.19; 6.19; and 6 more ranges	NVD

References

References

https://git.kernel.org/stable/c/ef668c9a2261ec9287faba6e6ef05a98b391aa2b	patch
https://git.kernel.org/stable/c/51d2e5d6491447258cb39ff1deb93df15d3c23cb	patch
https://git.kernel.org/stable/c/1c5a3175aecf82cd86dfcbef2a23e8b26d8d8e7c	patch
https://git.kernel.org/stable/c/49a66829dd3653695e60d7cae13521d131362fcd	patch
https://git.kernel.org/stable/c/425886b1f8304621b3f16632b274357067d5f13f	patch
https://git.kernel.org/stable/c/23f9485510c338476b9735d516c1d4aacb810d46	patch

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.