CVE-2026-52975

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-06-24. 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

Also known asEUVD-2026-38843 (ENISA EUVD) · GHSA-24f9-69r4-vr33 (GitHub Security Advisories)Source: ENISA EUVD

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: 3ad: implement proper RCU rules for port->aggregator

syzbot found a data-race in bond_3ad_get_active_agg_info / bond_3ad_state_machine_handler [1] which hints at lack of proper RCU implementation.

Add __rcu qualifier to port->aggregator, and add proper RCU API.

[1]

BUG: KCSAN: data-race in bond_3ad_get_active_agg_info / bond_3ad_state_machine_handler

write to 0xffff88813cf5c4b0 of 8 bytes by task 36 on cpu 0: ad_port_selection_logic drivers/net/bonding/bond_3ad.c:1659 [inline] bond_3ad_state_machine_handler+0x9d5/0x2d60 drivers/net/bonding/bond_3ad.c:2569 process_one_work kernel/workqueue.c:3302 [inline] process_scheduled_works+0x4f0/0x9c0 kernel/workqueue.c:3385 worker_thread+0x58a/0x780 kernel/workqueue.c:3466 kthread+0x22a/0x280 kernel/kthread.c:436 ret_from_fork+0x146/0x330 arch/x86/kernel/process.c:158 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245

read to 0xffff88813cf5c4b0 of 8 bytes by task 22063 on cpu 1: __bond_3ad_get_active_agg_info drivers/net/bonding/bond_3ad.c:2858 [inline] bond_3ad_get_active_agg_info+0x8c/0x230 drivers/net/bonding/bond_3ad.c:2881 bond_fill_info+0xe0f/0x10f0 drivers/net/bonding/bond_netlink.c:853 rtnl_link_info_fill net/core/rtnetlink.c:906 [inline] rtnl_link_fill+0x1d7/0x4e0 net/core/rtnetlink.c:927 rtnl_fill_ifinfo+0xf8e/0x1380 net/core/rtnetlink.c:2168 rtmsg_ifinfo_build_skb+0x11c/0x1b0 net/core/rtnetlink.c:4453 rtmsg_ifinfo_event net/core/rtnetlink.c:4486 [inline] rtmsg_ifinfo+0x6d/0x110 net/core/rtnetlink.c:4495 __dev_notify_flags+0x76/0x390 net/core/dev.c:9790 netif_change_flags+0xac/0xd0 net/core/dev.c:9823 do_setlink+0x905/0x2950 net/core/rtnetlink.c:3180 rtnl_group_changelink net/core/rtnetlink.c:3813 [inline] __rtnl_newlink net/core/rtnetlink.c:3981 [inline] rtnl_newlink+0xf55/0x1400 net/core/rtnetlink.c:4109 rtnetlink_rcv_msg+0x64b/0x720 net/core/rtnetlink.c:6995 netlink_rcv_skb+0x123/0x220 net/netlink/af_netlink.c:2550 rtnetlink_rcv+0x1c/0x30 net/core/rtnetlink.c:7022 netlink_unicast_kernel net/netlink/af_netlink.c:1318 [inline] netlink_unicast+0x5a8/0x680 net/netlink/af_netlink.c:1344 netlink_sendmsg+0x5c8/0x6f0 net/netlink/af_netlink.c:1894 sock_sendmsg_nosec net/socket.c:787 [inline] __sock_sendmsg net/socket.c:802 [inline] ____sys_sendmsg+0x563/0x5b0 net/socket.c:2698 ___sys_sendmsg+0x195/0x1e0 net/socket.c:2752 __sys_sendmsg net/socket.c:2784 [inline] __do_sys_sendmsg net/socket.c:2789 [inline] __se_sys_sendmsg net/socket.c:2787 [inline] __x64_sys_sendmsg+0xd4/0x160 net/socket.c:2787 x64_sys_call+0x194c/0x3020 arch/x86/include/generated/asm/syscalls_64.h:47 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x12c/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f

value changed: 0x0000000000000000 -> 0xffff88813cf5c400

Reported by Kernel Concurrency Sanitizer on: CPU: 1 UID: 0 PID: 22063 Comm: syz.0.31122 Tainted: G W syzkaller #0 PREEMPT(full) Tainted: [W]=WARN Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/18/2026

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
1st
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-27). 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

June 24, 2026

Last Modified

October 19, 2026

Advisory Details (5)

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

bonding: 3ad: implement proper RCU rules for port->aggregator - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c4f050ce06c56cfb5993268af4a5cb66ed1cd04e
Web page

bonding: 3ad: implement proper RCU rules for port->aggregator - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c169c5837525ad842df6a542facf52b6f866a519
Web page

bonding: 3ad: implement proper RCU rules for port->aggregator - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ba2272be04f0cb1e74e1e355ff32ef95df280731
Web page

bonding: 3ad: implement proper RCU rules for port->aggregator - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/78f409fd34fe9de2b24ad8e9dca1b4608a48ed3d
Web page

bonding: 3ad: implement proper RCU rules for port->aggregator - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b7265b3a82f40d2357c4004b26eb794a095b186

Vendor Advisories for CVE-2026-52975(2)

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

Patch Availability(26)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-27ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-10-27ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-10-27ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-136.136.2~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-10-27ubuntu
linuxKernel @ 6.1.175 (fixes >=3.13.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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)
  • every version up to 6.12.95-1: fixed in 6.12.95-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)
  • every version up to 7.0.10-1: fixed in 7.0.10-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

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 11× in last 7d / 52× 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 346 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 246 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-52975?
CVE-2026-52975 is a high-severity vulnerability; its CVE record was published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: bonding: 3ad: implement proper RCU rules for port->aggregator syzbot found a data-race in bond3adgetactiveagg_info / bond3adstatemachinehandler [1] which hints at lack of proper RCU implementation. Add rcu qualifier to…
When was the CVE record for CVE-2026-52975 published?
The CVE record for CVE-2026-52975 was published on June 24, 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-52975 actively exploited?
CVE-2026-52975 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-52975?
CVE-2026-52975 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-52975?
A fix for CVE-2026-52975 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-52975 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-52975

Explore →

Is Your Infrastructure Affected by CVE-2026-52975?

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

Book a Demo →Browse All CVEs