CVE-2026-45970

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
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:

bonding: alb: fix UAF in rlb_arp_recv during bond up/down

The ALB RX path may access rx_hashtbl concurrently with bond teardown. During rapid bond up/down cycles, rlb_deinitialize() frees rx_hashtbl while RX handlers are still running, leading to a null pointer dereference detected by KASAN.

However, the root cause is that rlb_arp_recv() can still be accessed after setting recv_probe to NULL, which is actually a use-after-free (UAF) issue. That is the reason for using the referenced commit in the Fixes tag.

[ 214.174138] Oops: general protection fault, probably for non-canonical address 0xdffffc000000001d: 0000 [#1] SMP KASAN PTI [ 214.186478] KASAN: null-ptr-deref in range [0x00000000000000e8-0x00000000000000ef] [ 214.194933] CPU: 30 UID: 0 PID: 2375 Comm: ping Kdump: loaded Not tainted 6.19.0-rc8+ #2 PREEMPT(voluntary) [ 214.205907] Hardware name: Dell Inc. PowerEdge R730/0WCJNT, BIOS 2.14.0 01/14/2022 [ 214.214357] RIP: 0010:rlb_arp_recv+0x505/0xab0 [bonding] [ 214.220320] Code: 0f 85 2b 05 00 00 48 b8 00 00 00 00 00 fc ff df 40 0f b6 ed 48 c1 e5 06 49 03 ad 78 01 00 00 48 8d 7d 28 48 89 fa 48 c1 ea 03 <0f> b6 04 02 84 c0 74 06 0f 8e 12 05 00 00 80 7d 28 00 0f 84 8c 00 [ 214.241280] RSP: 0018:ffffc900073d8870 EFLAGS: 00010206 [ 214.247116] RAX: dffffc0000000000 RBX: ffff888168556822 RCX: ffff88816855681e [ 214.255082] RDX: 000000000000001d RSI: dffffc0000000000 RDI: 00000000000000e8 [ 214.263048] RBP: 00000000000000c0 R08: 0000000000000002 R09: ffffed11192021c8 [ 214.271013] R10: ffff8888c9010e43 R11: 0000000000000001 R12: 1ffff92000e7b119 [ 214.278978] R13: ffff8888c9010e00 R14: ffff888168556822 R15: ffff888168556810 [ 214.286943] FS: 00007f85d2d9cb80(0000) GS:ffff88886ccb3000(0000) knlGS:0000000000000000 [ 214.295966] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 214.302380] CR2: 00007f0d047b5e34 CR3: 00000008a1c2e002 CR4: 00000000001726f0 [ 214.310347] Call Trace: [ 214.313070] [ 214.315318] ? __pfx_rlb_arp_recv+0x10/0x10 [bonding] [ 214.320975] bond_handle_frame+0x166/0xb60 [bonding] [ 214.326537] ? __pfx_bond_handle_frame+0x10/0x10 [bonding] [ 214.332680] __netif_receive_skb_core.constprop.0+0x576/0x2710 [ 214.339199] ? __pfx_arp_process+0x10/0x10 [ 214.343775] ? sched_balance_find_src_group+0x98/0x630 [ 214.349513] ? __pfx___netif_receive_skb_core.constprop.0+0x10/0x10 [ 214.356513] ? arp_rcv+0x307/0x690 [ 214.360311] ? __pfx_arp_rcv+0x10/0x10 [ 214.364499] ? __lock_acquire+0x58c/0xbd0 [ 214.368975] __netif_receive_skb_one_core+0xae/0x1b0 [ 214.374518] ? __pfx___netif_receive_skb_one_core+0x10/0x10 [ 214.380743] ? lock_acquire+0x10b/0x140 [ 214.385026] process_backlog+0x3f1/0x13a0 [ 214.389502] ? process_backlog+0x3aa/0x13a0 [ 214.394174] __napi_poll.constprop.0+0x9f/0x370 [ 214.399233] net_rx_action+0x8c1/0xe60 [ 214.403423] ? __pfx_net_rx_action+0x10/0x10 [ 214.408193] ? lock_acquire.part.0+0xbd/0x260 [ 214.413058] ? sched_clock_cpu+0x6c/0x540 [ 214.417540] ? mark_held_locks+0x40/0x70 [ 214.421920] handle_softirqs+0x1fd/0x860 [ 214.426302] ? __pfx_handle_softirqs+0x10/0x10 [ 214.431264] ? __neigh_event_send+0x2d6/0xf50 [ 214.436131] do_softirq+0xb1/0xf0 [ 214.439830]

The issue is reproducible by repeatedly running ip link set bond0 up/down while receiving ARP messages, where rlb_arp_recv() can race with rlb_deinitialize() and dereference a freed rx_hashtbl entry.

Fix this by setting recv_probe to NULL and then calling synchronize_net() to wait for any concurrent RX processing to finish. This ensures that no RX handler can access rx_hashtbl after it is freed in bond_alb_deinitialize().

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

Last Modified

August 5, 2026

Advisory Details (8)

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

bonding: alb: fix UAF in rlb_arp_recv during bond up/down - kernel/git/stable/linux.git - Linux kernel stable tree

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

bonding: alb: fix UAF in rlb_arp_recv during bond up/down - kernel/git/stable/linux.git - Linux kernel stable tree

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

bonding: alb: fix UAF in rlb_arp_recv during bond up/down - kernel/git/stable/linux.git - Linux kernel stable tree

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

bonding: alb: fix UAF in rlb_arp_recv during bond up/down - kernel/git/stable/linux.git - Linux kernel stable tree

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

bonding: alb: fix UAF in rlb_arp_recv during bond up/down - kernel/git/stable/linux.git - Linux kernel stable tree

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

bonding: alb: fix UAF in rlb_arp_recv during bond up/down - kernel/git/stable/linux.git - Linux kernel stable tree

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

bonding: alb: fix UAF in rlb_arp_recv during bond up/down - kernel/git/stable/linux.git - Linux kernel stable tree

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

bonding: alb: fix UAF in rlb_arp_recv during bond up/down - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c65cdf46ce340c9c00fbbaf84599d2daff43626e

Vendor Advisories for CVE-2026-45970(4)

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

Patch Availability(24)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-134.134.1~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-08-25ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-08-25ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-08-25ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-08-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-08-25ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-08-25ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-08-25ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1055.56~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-08-25ubuntu

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)5.10.257-1—
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.18~rc7-1~exp1 (100 versions)6.18.14-1—

Weakness Classification(1)

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

All Vendor Advisories

(24)

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 5× in last 7d / 82× 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 249 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-45970?
CVE-2026-45970 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: bonding: alb: fix UAF in rlbarprecv during bond up/down The ALB RX path may access rx_hashtbl concurrently with bond teardown. During rapid bond up/down cycles, rlb_deinitialize() frees rx_hashtbl while RX handlers are still…
When was CVE-2026-45970 disclosed?
CVE-2026-45970 was first published in the National Vulnerability Database on May 27, 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-45970 actively exploited?
CVE-2026-45970 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-45970?
CVE-2026-45970 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-45970?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45970, 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-45970

Explore →

Is Your Infrastructure Affected by CVE-2026-45970?

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

Start Free Scan →Browse All CVEs