CVE-2025-71180
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 5.15.198
- Linux Kernel < 6.1.161
- Linux Kernel < 6.6.121
- Linux Kernel < 6.12.66
- Linux Kernel < 6.18.6
- Linux Kernel 5.13
- Linux Kernel 6.19
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-71180.md and follow it. Check whether this project is affected by CVE-2025-71180. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- 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
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