CVE-2026-43366

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-08. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: 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:

io_uring/kbuf: check if target buffer list is still legacy on recycle

There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring provided type. This can happen if the request is forced via io-wq. The legacy recycling is missing checking if the buffer_list still exists, and if it's of the correct type. Add those checks.

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

Published

May 8, 2026

Last Modified

May 15, 2026

Advisory Details (6)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

io_uring/kbuf: check if target buffer list is still legacy on recycle - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring/kbuf: check if target buffer list is still legacy on recycle - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring/kbuf: check if target buffer list is still legacy on recycle - kernel/git/stable/linux.git - Linux kernel stable tree

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

io_uring/kbuf: check if target buffer list is still legacy on recycle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/97b57f69fee1b61b41acbf37e7720cac9d389fa4
generic

io_uring/kbuf: check if target buffer list is still legacy on recycle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50ad880db3013c6fee0ef13781762a39e2e7ef83
generic

io_uring/kbuf: check if target buffer list is still legacy on recycle - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/439a6728ec4641ffad1ca796622c19bc525e570f

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.1.167—osv

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.

Data Freshness Timeline

(refreshed 9× in last 7d / 29× 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 117 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43366?
CVE-2026-43366 is a high vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: check if target buffer list is still legacy on recycle There's a gap between when the buffer was grabbed and when it potentially gets recycled, where if the list is empty, someone could've upgraded it to a ring…
When was CVE-2026-43366 disclosed?
CVE-2026-43366 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43366 actively exploited?
CVE-2026-43366 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 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-43366?
CVE-2026-43366 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43366?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43366, 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

Explore the affected products and dependency analysis for CVE-2026-43366

Explore →

Is Your Infrastructure Affected by CVE-2026-43366?

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

Start Free Scan →Browse All CVEs