CVE-2026-31523

MEDIUMNVD 4.74.7
EchelonGraph scoreMEDIUM confidence

Score 4.7 from GitHub Security Advisory published 2026-04-22. NVD baseline CVSS 4.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
4.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.7Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
4.7
EG Score
4.7(medium)
EG Risk
26(Track)
EG Risk 26/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity47% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

April 22, 2026

Last Modified

April 28, 2026

Advisory Details (8)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

nvme-pci: ensure we're polling a polled queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ba167d5982e2eb6ff9356d409eca592ce99555da
generic

nvme-pci: ensure we're polling a polled queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b96c7b25eb1b748f3e3b1832ebf028b0b223d7e3
generic

nvme-pci: ensure we're polling a polled queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b222680ba55e018426c4535067a008f1d81a5d21
generic

nvme-pci: ensure we're polling a polled queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/acbc72dd1a09df53cafcf577259f4678be6afd6d
generic

nvme-pci: ensure we're polling a polled queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/965e2c943f065122f14282a88d70a8a92e12a4da
generic

nvme-pci: ensure we're polling a polled queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6f12734c4b619f923a4df0b1a46b8098b187d324
generic

nvme-pci: ensure we're polling a polled queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/166e31d7dbf6aa44829b98aa446bda5c9580f12a
generic

nvme-pci: ensure we're polling a polled queue - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0685dd9cb855ab77fcf3577b4702ba1d6df1c98d

Vendor Advisories for CVE-2026-31523(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 5.10.253osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)6.1.170-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 4× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 190 total refreshes for this CVE.

  1. 2026-09-13 16:47 UTCEPSS rescore
  2. 2026-09-11 14:52 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-04 05:06 UTCEPSS rescore
  7. 2026-09-02 02:38 UTCOSV refresh
  8. 2026-09-01 13:53 UTCEPSS rescore
  9. 2026-09-01 04:39 UTCEPSS rescore
  10. 2026-09-01 04:39 UTCEPSS rescore
  11. 2026-08-30 19:17 UTCEPSS rescore
  12. 2026-08-30 01:22 UTCEPSS rescore
  13. 2026-08-28 21:41 UTCEPSS rescore
  14. 2026-08-27 14:25 UTCEPSS rescore
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-24 14:17 UTCEPSS rescore
  18. 2026-08-19 17:03 UTCEPSS rescore
  19. 2026-08-18 13:48 UTCEPSS rescore
  20. 2026-08-17 13:47 UTCEPSS rescore
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 05:58 UTCEG score recompute
  23. 2026-08-16 05:58 UTCVendor advisory
  24. 2026-08-16 05:58 UTCGHSA enrichment
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 75 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 04:18 UTCVendor advisory
  3. 2026-08-14 04:18 UTCGHSA enrichment
  4. 2026-08-12 18:30 UTCEG score recompute
  5. 2026-08-12 18:30 UTCVendor advisory
  6. 2026-08-12 18:30 UTCGHSA enrichment
  7. 2026-08-12 13:50 UTCEPSS rescore
  8. 2026-08-11 16:45 UTCEG score recompute
  9. 2026-08-11 16:45 UTCVendor advisory
  10. 2026-08-11 16:45 UTCGHSA enrichment
  11. 2026-08-11 00:00 UTCEPSS rescore
  12. 2026-08-10 12:10 UTCVendor advisory
  13. 2026-08-10 12:10 UTCGHSA enrichment
  14. 2026-08-09 12:41 UTCEG score recompute
  15. 2026-08-09 12:41 UTCVendor advisory
  16. 2026-08-09 12:41 UTCGHSA enrichment
  17. 2026-08-08 16:37 UTCEPSS rescore
  18. 2026-08-08 12:27 UTCEG score recompute
  19. 2026-08-08 12:27 UTCVendor advisory
  20. 2026-08-08 12:27 UTCGHSA enrichment
  21. 2026-08-07 12:47 UTCEG score recompute
  22. 2026-08-07 12:47 UTCVendor advisory
  23. 2026-08-07 12:47 UTCGHSA enrichment
  24. 2026-08-06 13:46 UTCEPSS rescore
  25. 2026-08-05 23:04 UTCEG score recompute
  26. 2026-08-05 23:04 UTCVendor advisory
  27. 2026-08-05 23:04 UTCGHSA enrichment
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-04 15:10 UTCEPSS rescore
  30. 2026-08-03 21:14 UTCEG score recompute
  31. 2026-08-03 21:14 UTCVendor advisory
  32. 2026-08-03 21:14 UTCGHSA enrichment
  33. 2026-08-03 10:36 UTCEPSS rescore
  34. 2026-08-02 12:08 UTCEG score recompute
  35. 2026-08-02 12:08 UTCVendor advisory
  36. 2026-08-02 12:08 UTCGHSA enrichment
  37. 2026-08-02 02:27 UTCEPSS rescore
  38. 2026-08-01 04:16 UTCEPSS rescore
  39. 2026-07-30 16:27 UTCEPSS rescore
  40. 2026-07-30 01:30 UTCEPSS rescore
  41. 2026-07-28 15:36 UTCEPSS rescore
  42. 2026-07-26 14:54 UTCEPSS rescore
  43. 2026-07-26 14:54 UTCEPSS rescore
  44. 2026-07-25 14:18 UTCEPSS rescore
  45. 2026-07-25 14:17 UTCEPSS rescore
  46. 2026-07-24 14:17 UTCEPSS rescore
  47. 2026-07-23 03:08 UTCEG score recompute
  48. 2026-07-22 14:08 UTCEPSS rescore
  49. 2026-07-22 14:08 UTCEPSS rescore
  50. 2026-07-20 17:08 UTCEPSS rescore
  51. 2026-07-20 17:08 UTCEPSS rescore
  52. 2026-07-19 23:48 UTCOSV refresh
  53. 2026-07-19 02:29 UTCEPSS rescore
  54. 2026-07-18 10:04 UTCEPSS rescore
  55. 2026-07-18 10:04 UTCEPSS rescore
  56. 2026-07-16 17:03 UTCEPSS rescore
  57. 2026-07-16 17:03 UTCEPSS rescore
  58. 2026-07-15 16:57 UTCEPSS rescore
  59. 2026-07-15 16:57 UTCEPSS rescore
  60. 2026-07-15 02:00 UTCEPSS rescore
  61. 2026-07-15 02:00 UTCEPSS rescore
  62. 2026-07-12 05:46 UTCEPSS rescore
  63. 2026-07-11 08:27 UTCEPSS rescore
  64. 2026-07-08 15:15 UTCEPSS rescore
  65. 2026-07-07 13:46 UTCEPSS rescore
  66. 2026-07-06 16:27 UTCEPSS rescore
  67. 2026-07-06 16:27 UTCEPSS rescore
  68. 2026-07-06 02:23 UTCEPSS rescore
  69. 2026-07-06 02:23 UTCEPSS rescore
  70. 2026-07-05 02:30 UTCEPSS rescore
  71. 2026-07-04 06:31 UTCEPSS rescore
  72. 2026-07-01 15:06 UTCEPSS rescore
  73. 2026-06-28 14:07 UTCEPSS rescore
  74. 2026-06-28 14:07 UTCEPSS rescore
  75. 2026-06-28 04:56 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-31523?
CVE-2026-31523 is a medium vulnerability published on April 22, 2026. 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…
When was CVE-2026-31523 disclosed?
CVE-2026-31523 was first published in the National Vulnerability Database on April 22, 2026, with the most recent update on April 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-31523 actively exploited?
CVE-2026-31523 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.5% of all scored CVEs.
What is the CVSS score of CVE-2026-31523?
CVE-2026-31523 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-31523?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-31523, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-31523

Explore →

Is Your Infrastructure Affected by CVE-2026-31523?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.