Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

MediumCVSS 5.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 1c5a3175aecf82cd86dfcbef2a23e8b26d8d8e7c, 23f9485510c338476b9735d516c1d4aacb810d46, 425886b1f8304621b3f16632b274357067d5f13f.

Low priority for now. Upgrade to Linux Linux 1c5a3175aecf82cd86dfcbef2a23e8b26d8d8e7c, 23f9485510c338476b9735d516c1d4aacb810d46, 425886b1f8304621b3f16632b274357067d5f13f or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

Published
Jan 31, 2026
Updated
Jun 17, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-71180

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.13affected
    • a55ebd47f21f6f0472766fb52c973849e31d1466 and later · before ef668c9a2261ec9287faba6e6ef05a98b391aa2baffected · git
    • a55ebd47f21f6f0472766fb52c973849e31d1466 and later · before 51d2e5d6491447258cb39ff1deb93df15d3c23cbaffected · git
    • a55ebd47f21f6f0472766fb52c973849e31d1466 and later · before 1c5a3175aecf82cd86dfcbef2a23e8b26d8d8e7caffected · git
    • a55ebd47f21f6f0472766fb52c973849e31d1466 and later · before 49a66829dd3653695e60d7cae13521d131362fcdaffected · git
    • a55ebd47f21f6f0472766fb52c973849e31d1466 and later · before 425886b1f8304621b3f16632b274357067d5f13faffected · git
    • a55ebd47f21f6f0472766fb52c973849e31d1466 and later · before 23f9485510c338476b9735d516c1d4aacb810d46affected · git
    • before 5.13not affected · semver
    • 5.15.198 and later · up to and including 5.15.*not affected · semver
    • 6.1.161 and later · up to and including 6.1.*not affected · semver
Affected versions · NVD (7)

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.13.1 and later · before 5.15.198
  • linux linux kernel5.16 and later · before 6.1.161
  • linux linux kernel6.2 and later · before 6.6.121
  • linux linux kernel6.7 and later · before 6.12.66
  • linux linux kernel6.13 and later · before 6.18.6
  • linux linux kernel5.13
  • linux linux kernel6.19

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.69-16.12.69-1
Debian:14linuxbefore 6.18.8-16.18.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-23013Jan 25, 2026 · net: octeon_ep_vf: fix free_irq dev_id mismatch in IRQ rollback
    31Monitor
  • ← EarlierCVE-2026-23014Jan 28, 2026 · perf: Ensure swevent hrtimer is properly destroyed
    22Monitor
  • Later →CVE-2025-71181Jan 31, 2026 · rust_binder: remove spin_lock() in rust_shrink_free_page()
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1c5a3175aecf82cd86dfcbef2a23e8b26d8d8e7cVendor (CNA)
Linux Linux23f9485510c338476b9735d516c1d4aacb810d46Vendor (CNA)
Linux Linux425886b1f8304621b3f16632b274357067d5f13fVendor (CNA)
Linux Linux49a66829dd3653695e60d7cae13521d131362fcdVendor (CNA)
Linux Linux51d2e5d6491447258cb39ff1deb93df15d3c23cbVendor (CNA)
Linux Linuxef668c9a2261ec9287faba6e6ef05a98b391aa2bVendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records