CVE-2025-71180
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
- 2026-01-31Published by the CNA11:38 UTC
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| linux linux_kernel | from 5.13 before 5.15.198fixed in 5.15.198from 5.13.1 before 5.15.198fixed in 5.15.198from 5.13 before 6.1.161fixed in 6.1.161from 5.16 before 6.1.161fixed in 6.1.161from 5.13 before 6.12.66fixed in 6.12.66(+8 more) | 5.15.1985.15.1986.1.1616.1.1616.12.66 |
References
- https://git.kernel.org/stable/c/1c5a3175aecf82cd86dfcbef2a23e8b26d8d8e7c
- https://git.kernel.org/stable/c/23f9485510c338476b9735d516c1d4aacb810d46
- https://git.kernel.org/stable/c/425886b1f8304621b3f16632b274357067d5f13f
- https://git.kernel.org/stable/c/49a66829dd3653695e60d7cae13521d131362fcd
- https://git.kernel.org/stable/c/51d2e5d6491447258cb39ff1deb93df15d3c23cb
- https://git.kernel.org/stable/c/ef668c9a2261ec9287faba6e6ef05a98b391aa2b
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2025-71180'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2025-71180'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2025-71180'curl 'https://api.contrastcyber.com/cve_products/CVE-2025-71180'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).