CVE-2026-64032

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
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:

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

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (7)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

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
generic

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
generic

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
generic

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
generic

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
generic

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
generic

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

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 rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 33× in last 7d / 165× 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 216 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64032?
CVE-2026-64032 is a high vulnerability 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 CVE-2026-64032 disclosed?
CVE-2026-64032 was first published in the National Vulnerability Database on July 19, 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-64032 actively exploited?
CVE-2026-64032 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 96.9% of all scored CVEs.
What is the CVSS score of CVE-2026-64032?
CVE-2026-64032 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-64032?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64032, 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-64032

Explore →

Is Your Infrastructure Affected by CVE-2026-64032?

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