CVE-2026-43030

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-01. the CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
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:

bpf: Fix regsafe() for pointers to packet

In case rold->reg->range == BEYOND_PKT_END && rcur->reg->range == N regsafe() may return true which may lead to current state with valid packet range not being explored. Fix the bug.

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

Last Modified

September 8, 2026

Advisory Details (8)

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

bpf: Fix regsafe() for pointers to packet - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix regsafe() for pointers to packet - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix regsafe() for pointers to packet - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix regsafe() for pointers to packet - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix regsafe() for pointers to packet - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8aebe18069394f4a79d2d82080a0f806da449996
generic

bpf: Fix regsafe() for pointers to packet - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7241da033fdc507b920e092dab1f97b945cb0370
generic

bpf: Fix regsafe() for pointers to packet - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/37db6b9726d0bcf91cbdf9d63b558c50da49f968
generic

bpf: Fix regsafe() for pointers to packet - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/015a74476dc1ab6923d89f1ee009aaf43faa7185

Vendor Advisories for CVE-2026-43030(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-virtual-hwe-20.04-edge (5.15.0.186.196~20.04.1) @ focal2026-09-08ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-09-08ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-09-08ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-09-08ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-09-08ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-09-08ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-09-08ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-09-08ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-09-08ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-09-08ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-09-08ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-09-08ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-09-08ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-09-08ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-09-08ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-09-08ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-09-08ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-09-08ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-09-08ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-09-08ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-09-08ubuntu
linuxKernel @ 5.10.253—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.

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

Frequently asked(5)

What is CVE-2026-43030?
CVE-2026-43030 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix regsafe() for pointers to packet In case rold->reg->range == BEYONDPKTEND && rcur->reg->range == N regsafe() may return true which may lead to current state with valid packet range not being explored. Fix the bug.
When was CVE-2026-43030 disclosed?
CVE-2026-43030 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43030 actively exploited?
CVE-2026-43030 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 96.7% of all scored CVEs.
What is the CVSS score of CVE-2026-43030?
CVE-2026-43030 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-43030?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43030, 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-43030

Explore →

Is Your Infrastructure Affected by CVE-2026-43030?

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

Start Free Scan →Browse All CVEs