CVE-2024-42072

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-07-29. 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:

bpf: Fix may_goto with negative offset.

Zac's syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It's not correct to prune exploration of the program at this point. Note, that this check doesn't limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit.

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

Published

July 29, 2024

Last Modified

August 5, 2026

Advisory Details (2)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

bpf: Fix may_goto with negative offset. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2b2efe1937ca9f8815884bd4dcd5b32733025103
generic

bpf: Fix may_goto with negative offset. - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/175827e04f4be53f3dfb57edf12d0d49b18fd939

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.9.8—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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.9.8-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.9.8-1—

All Vendor Advisories

(1)

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 / 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 171 total refreshes for this CVE.

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

Related CVEs(same product)

Frequently asked(5)

What is CVE-2024-42072?
CVE-2024-42072 is a high vulnerability published on July 29, 2024. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix may_goto with negative offset. Zac's syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the…
When was CVE-2024-42072 disclosed?
CVE-2024-42072 was first published in the National Vulnerability Database on July 29, 2024, 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-2024-42072 actively exploited?
CVE-2024-42072 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 86.2% of all scored CVEs.
What is the CVSS score of CVE-2024-42072?
CVE-2024-42072 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-42072?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-42072, 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-2024-42072

Explore →

Is Your Infrastructure Affected by CVE-2024-42072?

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

Start Free Scan →Browse All CVEs