CVE-2026-43093

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. 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

A fix is available — apply it.

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

xsk: tighten UMEM headroom validation to account for tailroom and min frame

The current headroom validation in xdp_umem_reg() could leave us with insufficient space dedicated to even receive minimum-sized ethernet frame. Furthermore if multi-buffer would come to play then skb_shared_info stored at the end of XSK frame would be corrupted.

HW typically works with 128-aligned sizes so let us provide this value as bare minimum.

Multi-buffer setting is known later in the configuration process so besides accounting for 128 bytes, let us also take care of tailroom space upfront.

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 6, 2026

Last Modified

August 5, 2026

Advisory Details (5)

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

xsk: tighten UMEM headroom validation to account for tailroom and min frame - kernel/git/stable/linux.git - Linux kernel stable tree

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

xsk: tighten UMEM headroom validation to account for tailroom and min frame - kernel/git/stable/linux.git - Linux kernel stable tree

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

xsk: tighten UMEM headroom validation to account for tailroom and min frame - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9ea6ba4f3195dcba6e8b3e7b2e748593b7cafb12
generic

xsk: tighten UMEM headroom validation to account for tailroom and min frame - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6523bc1b40e69301f24c14338b762af4739d6d39
generic

xsk: tighten UMEM headroom validation to account for tailroom and min frame - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ec4d3f6e6934deb843b561ae048cd17218e5ad1

Vendor Advisories for CVE-2026-43093(1)

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

Patch Availability(27)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.186.196~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-23ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-23ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-23ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-23ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-23ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-23ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-23ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-23ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-23ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-23ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-23ubuntu
linuxKernel @ 5.10.258osv

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 (54 versions)5.10.259-1
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-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 (129 versions)6.19.14-1

All Vendor Advisories

(25)

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 7× in last 7d / 30× 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 219 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43093?
CVE-2026-43093 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: xsk: tighten UMEM headroom validation to account for tailroom and min frame The current headroom validation in xdpumemreg() could leave us with insufficient space dedicated to even receive minimum-sized ethernet frame. Furthermore…
When was CVE-2026-43093 disclosed?
CVE-2026-43093 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43093 actively exploited?
CVE-2026-43093 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.1% of all scored CVEs.
What is the CVSS score of CVE-2026-43093?
CVE-2026-43093 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43093?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43093, 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-43093

Explore →

Is Your Infrastructure Affected by CVE-2026-43093?

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