Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-37815misc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 22 days later

    Published

  3. · 13 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-37815, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 79aef6187e16b2d32307c8ff610e9e04f7f86e1f – < 1263d5f581908602c618c6665e683c4436383a09
    • affected 25692750c0259c5b65afec467d97201a485e8a00 – < 62957f58ab3aa7fa792dc6ff3575624062539a4d
    • affected 47d3749ec0cb56b7b98917c190a8c10cb54216fd – < 12cc2193f2b9548e8ea5fbce8201b44158222edf
    • affected 194f9f94a5169547d682e9bbcc5ae6d18a564735 – < 4e02059dc91068bc5017b8546f9ec3b930f6d6a6
    • affected 194f9f94a5169547d682e9bbcc5ae6d18a564735 – < 18eb77c75ed01439f96ae5c0f33461eb5134b907
    • affected 6.1.125 – < 6.1.136
    • affected 6.6.72 – < 6.6.89
    • affected 6.12.10 – < 6.12.26
  • Linux · Linux

    • affected 6.13
    • unaffected < 6.13
    • unaffected 6.1.136 – ≤ 6.1.*
    • unaffected 6.6.89 – ≤ 6.6.*
    • unaffected 6.12.26 – ≤ 6.12.*
    • unaffected 6.14.5 – ≤ 6.14.*
    • unaffected 6.15 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-37815 badge
[![CVE-2025-37815](https://cveledger.app/badge/CVE-2025-37815.svg)](https://cveledger.app/cve/CVE-2025-37815)

Record last updated .