CVE-2026-43006

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

A fix is available — apply it.

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

io_uring/rsrc: reject zero-length fixed buffer import

validate_fixed_range() admits buf_addr at the exact end of the registered region when len is zero, because the check uses strict greater-than (buf_end > imu->ubuf + imu->len). io_import_fixed() then computes offset == imu->len, which causes the bvec skip logic to advance past the last bio_vec entry and read bv_offset from out-of-bounds slab memory.

Return early from io_import_fixed() when len is zero. A zero-length import has no data to transfer and should not walk the bvec array at all.

BUG: KASAN: slab-out-of-bounds in io_import_reg_buf+0x697/0x7f0 Read of size 4 at addr ffff888002bcc254 by task poc/103 Call Trace: io_import_reg_buf+0x697/0x7f0 io_write_fixed+0xd9/0x250 __io_issue_sqe+0xad/0x710 io_issue_sqe+0x7d/0x1100 io_submit_sqes+0x86a/0x23c0 __do_sys_io_uring_enter+0xa98/0x1590 Allocated by task 103: The buggy address is located 12 bytes to the right of allocated 584-byte region [ffff888002bcc000, ffff888002bcc248)

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
2.5%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 12, 2026

Advisory Details (3)

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

io_uring/rsrc: reject zero-length fixed buffer import - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/40170fc1a79c1b2e68f09ae6aac687b7305ae6f4
generic

io_uring/rsrc: reject zero-length fixed buffer import - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/111a12b422a8cfa93deabaef26fec48237163214
generic

io_uring/rsrc: reject zero-length fixed buffer import - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/040a1e7e0e2f01851fec1dd2d96906f8636a9f75

Vendor Advisories for CVE-2026-43006(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-211.18.1.el10_22026-05-28redhat
linuxKernel @ 6.18.22—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.

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43006?
CVE-2026-43006 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: io_uring/rsrc: reject zero-length fixed buffer import validatefixedrange() admits buf_addr at the exact end of the registered region when len is zero, because the check uses strict greater-than (bufend > imu->ubuf + imu->len).…
When was CVE-2026-43006 disclosed?
CVE-2026-43006 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43006 actively exploited?
CVE-2026-43006 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43006?
CVE-2026-43006 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-43006?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43006, 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-43006

Explore →

Is Your Infrastructure Affected by CVE-2026-43006?

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

Start Free Scan →Browse All CVEs