Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-23140: misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error

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.22% (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 0557e70e2aeba8647bf5a950820b67cfb86533db, 54c9f299ad7d7c4be5d271ed12d01a59e95b8907, 5a4b7181213268c9b07bef8800905528435db44a; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1.

Low priority for now. Upgrade to Linux Linux 0557e70e2aeba8647bf5a950820b67cfb86533db, 54c9f299ad7d7c4be5d271ed12d01a59e95b8907, 5a4b7181213268c9b07bef8800905528435db44a; azl3 kernel 6.6.85.1-4 on Azure Linux 3.0 6.6.92.2-1; azl3 kernel 6.6.92.2-1 on Azure Linux 3.0 6.6.92.2-1 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: misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error After devm_request_irq() fails with error in pci_endpoint_test_request_irq(), the pci_endpoint_test_free_irq_vectors() is called assuming that all IRQs have been released. However, some requested IRQs remain unreleased, so there are still /proc/irq/* entries remaining, and this results in WARN() with the following message: remove_proc_entry: removing non-empty directory 'irq/30', leaking at least 'pci-endpoint-test.0' WARNING: CPU: 0 PID: 202 at fs/proc/generic.c:719 remove_proc_entry +0x190/0x19c To solve this issue, set the number of remaining IRQs to test->num_irqs, and release IRQs in advance by calling pci_endpoint_test_release_irq(). [kwilczynski: commit log]

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 1, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 12th 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.2%

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-23140

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 instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • 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 (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

Running WordPress? Scan your site free with WP Lens

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
debiandebian linux

Affected versions

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

  • debian debian linux11.0
  • linux linux kernel5.5 and later · before 5.10.237
  • linux linux kernel5.11 and later · before 5.15.181
  • linux linux kernel5.16 and later · before 6.1.135
  • linux linux kernel4.19 and later · before 5.4.293
  • linux linux kernel6.7 and later · before 6.12.25
  • linux linux kernel6.13 and later · before 6.14.3
  • linux linux kernel6.2 and later · before 6.6.88

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

    • 4.19affected
    • e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and later · before 705be96504779e4a333ea042b4779ea941f0ace9affected · git
    • e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and later · before e516e187bf32d8decc7c7d0025ae4857cad13c0eaffected · git
    • e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and later · before 54c9f299ad7d7c4be5d271ed12d01a59e95b8907affected · git
    • e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and later · before 9d5118b107b1a2353ed0dff24404aee2e6b7ca0aaffected · git
    • e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and later · before 5a4b7181213268c9b07bef8800905528435db44aaffected · git
    • e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and later · before 0557e70e2aeba8647bf5a950820b67cfb86533dbaffected · git
    • e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and later · before 770407f6173f4f39f4e2c1b54422b79ce6c98bdbaffected · git
    • e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and later · before f6cb7828c8e17520d4f5afb416515d3fae1af9a9affected · git
    • before 4.19not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.135-16.1.135-1
Debian:13linuxbefore 6.12.25-16.12.25-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-2025-37838Apr 18, 2025 · HSI: ssi_protocol: Fix use after free vulnerability in ssi_protocol Driver Due to Race Condition
    31Monitor
  • ← EarlierCVE-2024-58099Apr 29, 2025 · vmxnet3: Fix packet corruption in vmxnet3_xdp_xmit_frame
    22Monitor
  • Later →CVE-2025-23146May 1, 2025 · mfd: ene-kb3930: Fix a potential NULL pointer dereference
    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 Linux0557e70e2aeba8647bf5a950820b67cfb86533dbVendor (CNA)
Linux Linux54c9f299ad7d7c4be5d271ed12d01a59e95b8907Vendor (CNA)
Linux Linux5a4b7181213268c9b07bef8800905528435db44aVendor (CNA)
Linux Linux705be96504779e4a333ea042b4779ea941f0ace9Vendor (CNA)
Linux Linux770407f6173f4f39f4e2c1b54422b79ce6c98bdbVendor (CNA)
Linux Linux9d5118b107b1a2353ed0dff24404aee2e6b7ca0aVendor (CNA)
Linux Linuxe516e187bf32d8decc7c7d0025ae4857cad13c0eVendor (CNA)
Linux Linuxf6cb7828c8e17520d4f5afb416515d3fae1af9a9Vendor (CNA)
azl3 kernel 6.6.85.1-4 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.92.2-1 on Azure Linux 3.06.6.92.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.135-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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

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.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (9 more)

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

All records