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-2026-90007scsi: pm8001: Use rollback index when freeing MSI-X vectors

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Use rollback index when freeing MSI-X vectors pm8001_request_msix() unwinds previously registered handlers with free_irq() when request_irq() fails. The rollback loop uses the failing index i for every iteration instead of the already registered vector index j. That passes the wrong IRQ/dev_id pair to free_irq() and leaves the earlier handlers installed. Use j for both pci_irq_vector() and the matching irq_vector entry in the rollback loop.

Timeline

  1. ID reserved

    By Linux

  2. · 5 days later

    Published

  3. · 33 days 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-2026-90007, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% 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: High 7.8.

Affected products

  • Linux · Linux

    • affected a76037ff3479ad333a2505061915f7a21e7f3fb6 – < f39e3ca1f688d7c08954a0794e9bf1e279c83b15
    • affected a76037ff3479ad333a2505061915f7a21e7f3fb6 – < a980dec7c69990e4f119bcf6a2ea093d1c4975e8
    • affected a76037ff3479ad333a2505061915f7a21e7f3fb6 – < 0205db768570f9a46b20912afa581a0c7a63d8b7
    • affected a76037ff3479ad333a2505061915f7a21e7f3fb6 – < 2853ce9c88e0e6dd575f95f28b3a8c2b27164115
    • affected a76037ff3479ad333a2505061915f7a21e7f3fb6 – < fb22a8d2f3ac6665cc8bee197096b6675cac1a9f
    • affected a76037ff3479ad333a2505061915f7a21e7f3fb6 – < dd817463c9b42a3a9e23d15b86c6c77a6cfb809d
    • affected a76037ff3479ad333a2505061915f7a21e7f3fb6 – < e20b16aa3b49f9db5510940740255a987e6f2a6f
    • affected a76037ff3479ad333a2505061915f7a21e7f3fb6 – < 3f92a64545165bdbb36dee8fa35626b295463313
  • Linux · Linux

    • affected 4.11
    • unaffected < 4.11
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.5 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .