Kernel service interruption via invalid IRQ locking
Published Jan 31, 2026 · Updated Jan 31, 2026
Improper IRQ context handling in affected Linux Kernel releases beginning with 5.13 allows local users to interrupt kernel service. The interrupt_cnt_isr handler runs with IRQF_NO_THREAD and calls counter_push_event, which acquires events_list_lock as spinlock_t in an invalid wait context. Reachability requires a local process and an active interrupt-cnt counter path; the published impact is service interruption without confidentiality or integrity loss.
Summary
What happened
Improper IRQ context handling in affected Linux Kernel releases beginning with 5.13 allows local users to interrupt kernel service. The interrupt_cnt_isr handler runs with IRQF_NO_THREAD and calls counter_push_event, which acquires events_list_lock as spinlock_t in an invalid wait context. Reachability requires a local process and an active interrupt-cnt counter path; the published impact is service interruption without confidentiality or integrity loss.
The record
- CVE
- CVE-2025-71180
- Published
- Jan 31, 2026
- Updated
- Jan 31, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 31, 2026CVE publishedPublication date reported by the CVE source.
- Jan 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.13
- Affected versionversion=a55ebd47f21f6f0472766fb52c973849e31d1466 <1c5a3175aecf82cd86dfcbef2a23e8b26d8d8e7c
- Affected versionversion=a55ebd47f21f6f0472766fb52c973849e31d1466 <23f9485510c338476b9735d516c1d4aacb810d46
- Affected versionversion=a55ebd47f21f6f0472766fb52c973849e31d1466 <425886b1f8304621b3f16632b274357067d5f13f
- Affected versionversion=a55ebd47f21f6f0472766fb52c973849e31d1466 <49a66829dd3653695e60d7cae13521d131362fcd
- Affected versionversion=a55ebd47f21f6f0472766fb52c973849e31d1466 <51d2e5d6491447258cb39ff1deb93df15d3c23cb
- Affected versionversion=a55ebd47f21f6f0472766fb52c973849e31d1466 <ef668c9a2261ec9287faba6e6ef05a98b391aa2b
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo