CVE-2026-45970

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 27, 2026

Last Modified

October 19, 2026

Advisory Details (8)

Auto-updated Jun 4, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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(5)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1029.30) @ noble2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-10-19ubuntu
ubuntulinux-virtual-6.8 (6.8.0-134.134) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1058.61.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-134.134.1) @ noble2026-10-19ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-134.134+fips1) @ noble2026-10-19ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1032.33) @ noble2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-10-19ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-19ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2049.50) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-19ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-19ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-19ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1117.102) @ jammy2026-10-19ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-19ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-19ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1106.110~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-raspi-6.8 (6.8.0-1060.64) @ noble2026-10-19ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1112.122~20.04.1) @ focal2026-10-19ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-19ubuntu
redhatkernel-0:5.14.0-687.44.1.el9_82026-09-04redhat
redhatkernel-rt-0:4.18.0-553.159.1.rt7.500.el8_102026-09-03redhat
redhatkernel-0:4.18.0-553.159.1.el8_102026-09-03redhat
redhatkernel-0:6.12.0-211.50.1.el10_22026-09-01redhat
linuxKernel @ 5.10.252 (fixes >=3.0.0)—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (53 versions)
  • every version up to 5.10.257-1: fixed in 5.10.257-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (104 versions)
  • every version up to 6.18.14-1: fixed in 6.18.14-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(21)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 20× in last 7d / 41× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 306 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 206 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-45970?
CVE-2026-45970 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-45970 published?
The CVE record for CVE-2026-45970 was published on May 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-45970 actively exploited?
CVE-2026-45970 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45970?
CVE-2026-45970 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-45970?
A fix for CVE-2026-45970 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45970 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs