CVE-2026-64032

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-07-19. 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.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

bridge: mcast: Fix a possible use-after-free when removing a bridge port

When per-VLAN multicast snooping is enabled, the bridge iterates over all the bridge ports, disables the per-port multicast context on each port and enables the per-{port, VLAN} multicast contexts instead. The reverse happens when per-VLAN multicast snooping is disabled.

When global multicast snooping is enabled, the bridge iterates over all the bridge ports and enables the per-port multicast context on each port. The reverse happens when multicast snooping is disabled.

The above scheme can result in a situation where both types of contexts (per-port and per-{port, VLAN}) are enabled on a single bridge port:

# ip link add name br1 up type bridge mcast_snooping 1 mcast_querier 1 vlan_filtering 1 # ip link add name dummy1 up master br1 type dummy # ip link set dev br1 type bridge mcast_vlan_snooping 1 # ip link set dev br1 type bridge mcast_snooping 0 # ip link set dev br1 type bridge mcast_snooping 1

This is not intended and it is a problem since the commit cited below. Prior to this commit, when removing a bridge port, br_multicast_disable_port() would disable the per-port multicast context and the per-{port, VLAN} multicast contexts would get disabled when flushing VLANs.

After this commit, br_multicast_disable_port() only disables the per-port multicast context if per-VLAN multicast snooping is disabled. If both types of contexts were enabled on the port when it was removed, the per-port multicast context would remain enabled when freeing the bridge port, leading to a use-after-free [1].

Fix by preventing the bridge from enabling / disabling the per-port multicast contexts when toggling global multicast snooping if per-VLAN multicast snooping is enabled.

[1] ODEBUG: free active (active state 0) object: ffff88810f8bda78 object type: timer_list hint: br_ip6_multicast_port_query_expired (net/bridge/br_multicast.c:1927) WARNING: lib/debugobjects.c:629 at debug_print_object+0x1b1/0x3e0, CPU#5: swapper/5/0 [...] Call Trace:

__debug_check_no_obj_freed (lib/debugobjects.c:1116) kfree (mm/slub.c:2620 mm/slub.c:6250 mm/slub.c:6565) kobject_cleanup (lib/kobject.c:689) rcu_do_batch (kernel/rcu/tree.c:2617) rcu_core (kernel/rcu/tree.c:2869) handle_softirqs (kernel/softirq.c:622) __irq_exit_rcu (kernel/softirq.c:656 kernel/softirq.c:496 kernel/softirq.c:735) irq_exit_rcu (kernel/softirq.c:752) sysvec_apic_timer_interrupt (arch/x86/kernel/apic/apic.c:1061 (discriminator 47) arch/x86/kernel/apic/apic.c:1061 (discriminator 47))

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 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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.2%
EPSS %ILE
5th
KEV
Not listed

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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

July 19, 2026

Last Modified

October 13, 2026

Advisory Details (7)

Auto-updated Jul 21, 2026
Patch available.
Web page

bridge: mcast: Fix a possible use-after-free when removing a bridge port - kernel/git/stable/linux.git - Linux kernel stable tree

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

bridge: mcast: Fix a possible use-after-free when removing a bridge port - kernel/git/stable/linux.git - Linux kernel stable tree

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

bridge: mcast: Fix a possible use-after-free when removing a bridge port - kernel/git/stable/linux.git - Linux kernel stable tree

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

bridge: mcast: Fix a possible use-after-free when removing a bridge port - kernel/git/stable/linux.git - Linux kernel stable tree

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

bridge: mcast: Fix a possible use-after-free when removing a bridge port - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7213256c91ed778a0997c2029c152b18dc50e4fd
Web page

bridge: mcast: Fix a possible use-after-free when removing a bridge port - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4df78ff02629c7729168f0696a7a2123c389818d
Web page

bridge: mcast: Fix a possible use-after-free when removing a bridge port - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1900ca8acb92fbea8bf9abef9927c7fed03db7fc

Vendor Advisories for CVE-2026-64032(1)

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-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-13ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-10-13ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-13ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1109.105) @ jammy2026-10-13ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1117.126) @ jammy2026-10-13ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1064.67+fips1) @ noble2026-10-13ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-10-13ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1109.115~20.04.1) @ focal2026-10-13ubuntu
ubuntulinux-tools-intel-iot-realtime-5.15 (5.15.0.1104.108) @ jammy2026-10-13ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1107.106) @ jammy2026-10-13ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-10-13ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-10-13ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1067.75) @ noble2026-10-13ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2053.55) @ noble2026-10-13ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1067.75+fips1) @ noble2026-10-13ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-13ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1106.104) @ jammy2026-10-13ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1036.37) @ noble2026-10-13ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1067.75~22.04.1) @ jammy2026-10-13ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1061.64) @ noble2026-10-13ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-139.139.1~22.04.1) @ jammy2026-10-13ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.66~20.04.1) @ focal2026-10-13ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-10-13ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1075 (5.15.0-1075.79) @ jammy2026-10-13ubuntu
ubuntulinux-virtual-6.8 (6.8.0-139.139) @ noble2026-10-13ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1107.107) @ jammy2026-10-13ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1064.64) @ jammy2026-10-13ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-10-13ubuntu
ubuntulinux-tools-ibm-edge (6.8.0-1066.67~22.04.1) @ jammy2026-10-13ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1064.67) @ noble2026-10-13ubuntu

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

(3 across 3 ecosystems)
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.94-1~bpo12+1 (27 versions)
  • every version up to 6.12.94-1: fixed in 6.12.94-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (142 versions)
  • every version up to 7.0.12-1: fixed in 7.0.12-1
—

Weakness Classification(1)

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

All Vendor Advisories

(25)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64032?
CVE-2026-64032 is a high-severity vulnerability; its CVE record was published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: bridge: mcast: Fix a possible use-after-free when removing a bridge port When per-VLAN multicast snooping is enabled, the bridge iterates over all the bridge ports, disables the per-port multicast context on each port and enables…
When was the CVE record for CVE-2026-64032 published?
The CVE record for CVE-2026-64032 was published on July 19, 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 13, 2026; the record at its source may have been updated since.
Is CVE-2026-64032 actively exploited?
CVE-2026-64032 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-64032?
CVE-2026-64032 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-64032?
A fix for CVE-2026-64032 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64032 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-64032

Explore →

Is Your Infrastructure Affected by CVE-2026-64032?

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

Book a Demo →Browse All CVEs