CVE-2025-71180counter: interrupt-cnt: Drop IRQF_NO_THREAD flag
- 5.5MediumCVSS base score
- 0.18%Exploitation in 30 daysEPSS · top 92% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
Published
- 3 months later
· 3 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.18% · top 92% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected a55ebd47f21f6f0472766fb52c973849e31d1466 – < ef668c9a2261ec9287faba6e6ef05a98b391aa2b
- affected a55ebd47f21f6f0472766fb52c973849e31d1466 – < 51d2e5d6491447258cb39ff1deb93df15d3c23cb
- affected a55ebd47f21f6f0472766fb52c973849e31d1466 – < 1c5a3175aecf82cd86dfcbef2a23e8b26d8d8e7c
- affected a55ebd47f21f6f0472766fb52c973849e31d1466 – < 49a66829dd3653695e60d7cae13521d131362fcd
- affected a55ebd47f21f6f0472766fb52c973849e31d1466 – < 425886b1f8304621b3f16632b274357067d5f13f
- affected a55ebd47f21f6f0472766fb52c973849e31d1466 – < 23f9485510c338476b9735d516c1d4aacb810d46
- affected 5.13
- unaffected < 5.13
- unaffected 5.15.198 – ≤ 5.15.*
- unaffected 6.1.161 – ≤ 6.1.*
- unaffected 6.6.121 – ≤ 6.6.*
- unaffected 6.12.66 – ≤ 6.12.*
- unaffected 6.18.6 – ≤ 6.18.*
- unaffected 6.19 – ≤ *
References
References6
- https://git.kernel.org/stable/c/ef668c9a2261ec9287faba6e6ef05a98b391aa2b (opens in a new tab)
- https://git.kernel.org/stable/c/51d2e5d6491447258cb39ff1deb93df15d3c23cb (opens in a new tab)
- https://git.kernel.org/stable/c/1c5a3175aecf82cd86dfcbef2a23e8b26d8d8e7c (opens in a new tab)
- https://git.kernel.org/stable/c/49a66829dd3653695e60d7cae13521d131362fcd (opens in a new tab)
- https://git.kernel.org/stable/c/425886b1f8304621b3f16632b274357067d5f13f (opens in a new tab)
- https://git.kernel.org/stable/c/23f9485510c338476b9735d516c1d4aacb810d46 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2025-206595 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2025-71180)Record last updated .