CVE-2025-37815: misc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration
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.18% (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 1263d5f581908602c618c6665e683c4436383a09, 12cc2193f2b9548e8ea5fbce8201b44158222edf, 18eb77c75ed01439f96ae5c0f33461eb5134b907.
Low priority for now. Upgrade to Linux Linux 1263d5f581908602c618c6665e683c4436383a09, 12cc2193f2b9548e8ea5fbce8201b44158222edf, 18eb77c75ed01439f96ae5c0f33461eb5134b907 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: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration Resolve kernel panic while accessing IRQ handler associated with the generated IRQ. This is done by acquiring the spinlock and storing the current interrupt state before handling the interrupt request using generic_handle_irq. A previous fix patch was submitted where 'generic_handle_irq' was replaced with 'handle_nested_irq'. However, this change also causes the kernel panic where after determining which GPIO triggered the interrupt and attempting to call handle_nested_irq with the mapped IRQ number, leads to a failure in locating the registered handler.
- Published
- May 8, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 8th percentile
- CWE
- —
Report tools
Action score
22
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.
Is your version affected? Check itNoroxi 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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.1.125 and later · before 6.1.136
- linux linux kernel6.6.72 and later · before 6.6.89
- linux linux kernel6.12.10 and later · before 6.12.26
- linux linux kernel6.13.1 and later · before 6.14.5
- linux linux kernel6.13
- linux linux kernel6.15
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
- 6.13affected
- 79aef6187e16b2d32307c8ff610e9e04f7f86e1f and later · before 1263d5f581908602c618c6665e683c4436383a09affected · git
- 25692750c0259c5b65afec467d97201a485e8a00 and later · before 62957f58ab3aa7fa792dc6ff3575624062539a4daffected · git
- 47d3749ec0cb56b7b98917c190a8c10cb54216fd and later · before 12cc2193f2b9548e8ea5fbce8201b44158222edfaffected · git
- 194f9f94a5169547d682e9bbcc5ae6d18a564735 and later · before 4e02059dc91068bc5017b8546f9ec3b930f6d6a6affected · git
- 194f9f94a5169547d682e9bbcc5ae6d18a564735 and later · before 18eb77c75ed01439f96ae5c0f33461eb5134b907affected · git
- 6.1.125 and later · before 6.1.136affected · semver
- 6.6.72 and later · before 6.6.89affected · semver
- 6.12.10 and later · before 6.12.26affected · semver
- before 6.13not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.137-1 | 6.1.137-1 |
| Debian:13 | linux | before 6.12.27-1 | 6.12.27-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-37812May 8, 2025 · usb: cdns3: Fix deadlock when using NCM gadget22Monitor
- ← EarlierCVE-2025-37814May 8, 2025 · tty: Require CAP_SYS_ADMIN for all usages of TIOCL_SELMOUSEREPORT22Monitor
- Later →CVE-2025-37816May 8, 2025 · mei: vsc: Fix fortify-panic caused by invalid counted_by() use22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1263d5f581908602c618c6665e683c4436383a09 | Vendor (CNA) |
| Linux Linux | 12cc2193f2b9548e8ea5fbce8201b44158222edf | Vendor (CNA) |
| Linux Linux | 18eb77c75ed01439f96ae5c0f33461eb5134b907 | Vendor (CNA) |
| Linux Linux | 4e02059dc91068bc5017b8546f9ec3b930f6d6a6 | Vendor (CNA) |
| Linux Linux | 6.1.136 | Vendor (CNA) |
| Linux Linux | 6.12.26 | Vendor (CNA) |
| Linux Linux | 6.6.89 | Vendor (CNA) |
| Linux Linux | 62957f58ab3aa7fa792dc6ff3575624062539a4d | Vendor (CNA) |
| debian:linux | 6.1.137-1 · Debian:12 | Package 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 researchersFinders, 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/12cc2193f2b9548e8ea5fbce8201b44158222edf
- git.kernel.org/stable/c/18eb77c75ed01439f96ae5c0f33461eb5134b907
- git.kernel.org/stable/c/4e02059dc91068bc5017b8546f9ec3b930f6d6a6
- git.kernel.org/stable/c/62957f58ab3aa7fa792dc6ff3575624062539a4d
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.