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-31523nvme-pci: ensure we're polling a polled queue

Description

In the Linux kernel, the following vulnerability has been resolved: nvme-pci: ensure we're polling a polled queue A user can change the polled queue count at run time. There's a brief window during a reset where a hipri task may try to poll that queue before the block layer has updated the queue maps, which would race with the now interrupt driven queue and may cause double completions.

Timeline

  1. ID reserved

    By Linux

  2. · 44 days later

    Published

  3. · 7 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-2026-31523, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.09% · top 100% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 4b04cc6a8f86c4842314def22332de1f15de8523 – < 965e2c943f065122f14282a88d70a8a92e12a4da
    • affected 4b04cc6a8f86c4842314def22332de1f15de8523 – < ba167d5982e2eb6ff9356d409eca592ce99555da
    • affected 4b04cc6a8f86c4842314def22332de1f15de8523 – < 0685dd9cb855ab77fcf3577b4702ba1d6df1c98d
    • affected 4b04cc6a8f86c4842314def22332de1f15de8523 – < 6f12734c4b619f923a4df0b1a46b8098b187d324
    • affected 4b04cc6a8f86c4842314def22332de1f15de8523 – < acbc72dd1a09df53cafcf577259f4678be6afd6d
    • affected 4b04cc6a8f86c4842314def22332de1f15de8523 – < b96c7b25eb1b748f3e3b1832ebf028b0b223d7e3
    • affected 4b04cc6a8f86c4842314def22332de1f15de8523 – < b222680ba55e018426c4535067a008f1d81a5d21
    • affected 4b04cc6a8f86c4842314def22332de1f15de8523 – < 166e31d7dbf6aa44829b98aa446bda5c9580f12a
  • Linux · Linux

    • affected 5.0
    • unaffected < 5.0
    • unaffected 5.10.253 – ≤ 5.10.*
    • unaffected 5.15.203 – ≤ 5.15.*
    • unaffected 6.1.168 – ≤ 6.1.*
    • unaffected 6.6.131 – ≤ 6.6.*
    • unaffected 6.12.80 – ≤ 6.12.*
    • unaffected 6.18.21 – ≤ 6.18.*
    • unaffected 6.19.11 – ≤ 6.19.*
    • unaffected 7.0 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .