CVE-2026-53321

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 5.5; sources differ by 0.0.

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

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

io_uring/napi: cap busy_poll_to 10 msec

Currently there's no cap on the maximum amount of time that napi is allowed to poll if no events are found, which can lead to kernel complaints on a task being stuck as there's no conditional rescheduling done within that loop.

Just cap it to 10 msec in total, that's already way above any kind of sane value that will reap any benefits, yet low enough that it's nowhere near being able to trigger preemption complaints.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 6, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

io_uring/napi: cap busy_poll_to 10 msec - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring/napi: cap busy_poll_to 10 msec - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring/napi: cap busy_poll_to 10 msec - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/39767f944a8c9e696566c37ad5b20131406c4b8d

Vendor Advisories for CVE-2026-53321(1)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-06ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-06ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-06ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-06ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-06ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-06ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-06ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-06ubuntu

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (174 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 63× 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 171 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53321?
CVE-2026-53321 is a medium vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: iouring/napi: cap busypoll_to 10 msec Currently there's no cap on the maximum amount of time that napi is allowed to poll if no events are found, which can lead to kernel complaints on a task being stuck as there's no conditional…
When was CVE-2026-53321 disclosed?
CVE-2026-53321 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53321 actively exploited?
CVE-2026-53321 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 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-53321?
CVE-2026-53321 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53321?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53321, 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-53321

Explore →

Is Your Infrastructure Affected by CVE-2026-53321?

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

Start Free Scan →Browse All CVEs