CVE-2026-43009

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 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 incorrect pruning due to atomic fetch precision tracking

When backtrack_insn encounters a BPF_STX instruction with BPF_ATOMIC and BPF_FETCH, the src register (or r0 for BPF_CMPXCHG) also acts as a destination, thus receiving the old value from the memory location.

The current backtracking logic does not account for this. It treats atomic fetch operations the same as regular stores where the src register is only an input. This leads the backtrack_insn to fail to propagate precision to the stack location, which is then not marked as precise!

Later, the verifier's path pruning can incorrectly consider two states equivalent when they differ in terms of stack state. Meaning, two branches can be treated as equivalent and thus get pruned when they should not be seen as such.

Fix it as follows: Extend the BPF_LDX handling in backtrack_insn to also cover atomic fetch operations via is_atomic_fetch_insn() helper. When the fetch dst register is being tracked for precision, clear it, and propagate precision over to the stack slot. For non-stack memory, the precision walk stops at the atomic instruction, same as regular BPF_LDX. This covers all fetch variants.

Before:

0: (b7) r1 = 8 ; R1=8 1: (7b) *(u64 *)(r10 -8) = r1 ; R1=8 R10=fp0 fp-8=8 2: (b7) r2 = 0 ; R2=0 3: (db) r2 = atomic64_fetch_add((u64 *)(r10 -8), r2) ; R2=8 R10=fp0 fp-8=mmmmmmmm 4: (bf) r3 = r10 ; R3=fp0 R10=fp0 5: (0f) r3 += r2 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r2 stack= before 4: (bf) r3 = r10 mark_precise: frame0: regs=r2 stack= before 3: (db) r2 = atomic64_fetch_add((u64 *)(r10 -8), r2) mark_precise: frame0: regs=r2 stack= before 2: (b7) r2 = 0 6: R2=8 R3=fp8 6: (b7) r0 = 0 ; R0=0 7: (95) exit

After:

0: (b7) r1 = 8 ; R1=8 1: (7b) *(u64 *)(r10 -8) = r1 ; R1=8 R10=fp0 fp-8=8 2: (b7) r2 = 0 ; R2=0 3: (db) r2 = atomic64_fetch_add((u64 *)(r10 -8), r2) ; R2=8 R10=fp0 fp-8=mmmmmmmm 4: (bf) r3 = r10 ; R3=fp0 R10=fp0 5: (0f) r3 += r2 mark_precise: frame0: last_idx 5 first_idx 0 subseq_idx -1 mark_precise: frame0: regs=r2 stack= before 4: (bf) r3 = r10 mark_precise: frame0: regs=r2 stack= before 3: (db) r2 = atomic64_fetch_add((u64 *)(r10 -8), r2) mark_precise: frame0: regs= stack=-8 before 2: (b7) r2 = 0 mark_precise: frame0: regs= stack=-8 before 1: (7b) *(u64 *)(r10 -8) = r1 mark_precise: frame0: regs=r1 stack= before 0: (b7) r1 = 8 6: R2=8 R3=fp8 6: (b7) r0 = 0 ; R0=0 7: (95) exit

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
3.3%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 7, 2026

Advisory Details (2)

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

bpf: Fix incorrect pruning due to atomic fetch precision tracking - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7ffbe45b1d227e24659998a91cfd4c27af457e71
generic

bpf: Fix incorrect pruning due to atomic fetch precision tracking - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/179ee84a89114b854ac2dd1d293633a7f6c8dac1

Vendor Advisories for CVE-2026-43009(1)

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

Data Freshness Timeline

(refreshed 6× 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 124 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43009?
CVE-2026-43009 is a high vulnerability published on May 1, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix incorrect pruning due to atomic fetch precision tracking When backtrackinsn encounters a BPFSTX instruction with BPF_ATOMIC and BPFFETCH, the src register (or r0 for BPFCMPXCHG) also acts as a destination, thus receiving…
When was CVE-2026-43009 disclosed?
CVE-2026-43009 was first published in the National Vulnerability Database on May 1, 2026, with the most recent update on May 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43009 actively exploited?
CVE-2026-43009 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43009?
CVE-2026-43009 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43009?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43009, 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-43009

Explore →

Is Your Infrastructure Affected by CVE-2026-43009?

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