🛡️ UBUNTU-CVE-2025-38248
⚪ Unknown ✅ No Known Exploit OSV
N/A
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

In the Linux kernel, the following vulnerability has been resolved: bridge: mcast: Fix use-after-free during router port configuration The bridge maintains a global list of ports behind which a multicast router resides. The list is consulted during forwarding to ensure multicast packets are forwarded to these ports even if the ports are not member in the matching MDB entry. When per-VLAN multicast snooping is enabled, the per-port multicast context is disabled on each port and the port is removed from the global router port list: # ip link add name br1 up type bridge vlan_filtering 1 mcast_snooping 1 # ip link add name dummy1 up master br1 type dummy # ip link set dev dummy1 type bridge_slave mcast_router 2 $ bridge -d mdb show | grep router router ports on br1: dummy1 # ip link set dev br1 type bridge mcast_vlan_snooping 1 $ bridge -d mdb show | grep router However, the port can be re-added to the global list even when per-VLAN multicast snooping is enabled: # ip link set dev dummy1 type bridge_slave mcast_router 0 # ip link set dev dummy1 type bridge_slave mcast_router 2 $ bridge -d mdb show | grep router router ports on br1: dummy1 Since commit 4b30ae9adb04 ("net: bridge: mcast: re-implement br_multicast_{enable, disable}_port functions"), when per-VLAN multicast snooping is enabled, multicast disablement on a port will disable the per-{port, VLAN} multicast contexts and not the per-port one. As a result, a port will remain in the global router port list even after it is deleted. This will lead to a use-after-free [1] when the list is traversed (when adding a new port to the list, for example): # ip link del dev dummy1 # ip link add name dummy2 up master br1 type dummy # ip link set dev dummy2 type bridge_slave mcast_router 2 Similarly, stale entries can also be found in the per-VLAN router port list. When per-VLAN multicast snooping is disabled, the per-{port, VLAN} contexts are disabled on each port and the port is removed from the per-VLAN router port list: # ip link add name br1 up type bridge vlan_filtering 1 mcast_snooping 1 mcast_vlan_snooping 1 # ip link add name dummy1 up master br1 type dummy # bridge vlan add vid 2 dev dummy1 # bridge vlan global set vid 2 dev br1 mcast_snooping 1 # bridge vlan set vid 2 dev dummy1 mcast_router 2 $ bridge vlan global show dev br1 vid 2 | grep router router ports: dummy1 # ip link set dev br1 type bridge mcast_vlan_snooping 0 $ bridge vlan global show dev br1 vid 2 | grep router However, the port can be re-added to the per-VLAN list even when per-VLAN multicast snooping is disabled: # bridge vlan set vid 2 dev dummy1 mcast_router 0 # bridge vlan set vid 2 dev dummy1 mcast_router 2 $ bridge vlan global show dev br1 vid 2 | grep router router ports: dummy1 When the VLAN is deleted from the port, the per-{port, VLAN} multicast context will not be disabled since multicast snooping is not enabled on the VLAN. As a result, the port will remain in the per-VLAN router port list even after it is no longer member in the VLAN. This will lead to a use-after-free [2] when the list is traversed (when adding a new port to the list, for example): # ip link add name dummy2 up master br1 type dummy # bridge vlan add vid 2 dev dummy2 # bridge vlan del vid 2 dev dummy1 # bridge vlan set vid 2 dev dummy2 mcast_router 2 Fix these issues by removing the port from the relevant (global or per-VLAN) router port list in br_multicast_port_ctx_deinit(). The function is invoked during port deletion with the per-port multicast context and during VLAN deletion with the per-{port, VLAN} multicast context. Note that deleting the multicast router timer is not enough as it only takes care of the temporary multicast router states (1 or 3) and not the permanent one (2). [1] BUG: KASAN: slab-out-of-bounds in br_multicast_add_router.part.0+0x3f1/0x560 Write of size 8 at addr ffff888004a67328 by task ip/384 [...] Call Trace: dump_stack ---truncated---

Details

Severity Unknown
CVSS Score N/A
CVSS Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2025-07-09
Updated 2026-06-15
Modified 2026-06-08
Fix URL N/A

Affected Packages

Software From version Fixed in
linux 6.8.0-100.100
linux-allwinner-5.19
linux-aws 6.8.0-1046.49
linux-aws-5.0
linux-aws-5.11
linux-aws-5.13
linux-aws-5.15 5.15.0-1100.107~20.04.2
linux-aws-5.19
linux-aws-5.3
linux-aws-5.8
linux-aws-6.14 6.14.0-1015.15~24.04.1
linux-aws-6.2
linux-aws-6.5
linux-aws-6.8 6.8.0-1046.49~22.04.1
linux-aws-fips 6.8.0-1046.49+fips1
linux-azure 6.8.0-1046.52
linux-azure-5.11
linux-azure-5.13
linux-azure-5.15 5.15.0-1110.119~20.04.1
linux-azure-5.19
linux-azure-5.3
linux-azure-5.8
linux-azure-6.11
linux-azure-6.14 6.14.0-1014.14~24.04.1
linux-azure-6.2
linux-azure-6.5
linux-azure-6.8 6.8.0-1051.57~22.04.1
linux-azure-edge
linux-azure-fde
linux-azure-fde-5.19
linux-azure-fde-6.17
linux-azure-fde-6.2
linux-azure-fde-6.8
linux-azure-fips 6.8.0-1046.52+fips1
linux-azure-nvidia
linux-azure-nvidia-6.14 6.14.0-1007.7
linux-bluefield
linux-fips 6.8.0-100.100+fips1
linux-gcp 6.8.0-1047.50
linux-gcp-5.11
linux-gcp-5.13
linux-gcp-5.15 5.15.0-1100.109~20.04.1
linux-gcp-5.19
linux-gcp-5.3
linux-gcp-5.8
linux-gcp-6.11
linux-gcp-6.14 6.14.0-1018.19~24.04.1
linux-gcp-6.2
linux-gcp-6.5
linux-gcp-6.8 6.8.0-1047.50~22.04.2
linux-gcp-fips 6.8.0-1047.50+fips1
linux-gke 6.8.0-1043.48
linux-gke-4.15
linux-gke-5.15
linux-gke-5.4
linux-gkeop 6.8.0-1030.33
linux-gkeop-5.15
linux-gkeop-5.4
linux-hwe
linux-hwe-5.11
linux-hwe-5.13
linux-hwe-5.15 5.15.0-170.180~20.04.3
linux-hwe-5.19
linux-hwe-5.8
linux-hwe-6.11
linux-hwe-6.2
linux-hwe-6.5
linux-hwe-6.8 6.8.0-100.100~22.04.1
linux-hwe-edge
linux-ibm 6.8.0-1044.44
linux-ibm-5.15 5.15.0-1094.97~20.04.1
linux-ibm-6.8 6.8.0-1044.44~22.04.1
linux-intel
linux-intel-5.13
linux-intel-iot-realtime 5.15.0-1092.94
linux-intel-iotg 5.15.0-1095.101
linux-intel-iotg-5.15 5.15.0-1095.101~20.04.1
linux-kvm 5.15.0-1092.97
linux-lowlatency 6.8.0-100.100.1
linux-lowlatency-hwe-5.15 5.15.0-170.180~20.04.1
linux-lowlatency-hwe-5.19
linux-lowlatency-hwe-6.11
linux-lowlatency-hwe-6.2
linux-lowlatency-hwe-6.5
linux-lowlatency-hwe-6.8 6.8.0-100.100.1~22.04.1
linux-nvidia 6.8.0-1046.49
linux-nvidia-6.11
linux-nvidia-6.2
linux-nvidia-6.5
linux-nvidia-6.8 6.8.0-1046.49~22.04.1
linux-nvidia-lowlatency 6.8.0-1046.49.1
linux-nvidia-tegra 6.8.0-1020.20
linux-nvidia-tegra-5.15 5.15.0-1052.52~20.04.2
linux-nvidia-tegra-igx 5.15.0-1041.41
linux-oem
linux-oem-5.10
linux-oem-5.13
linux-oem-5.14
linux-oem-5.17
linux-oem-5.6
linux-oem-6.0
linux-oem-6.1
linux-oem-6.11
linux-oem-6.14 6.14.0-1014.14
linux-oem-6.5
linux-oem-6.8
linux-oracle 6.8.0-1043.44
linux-oracle-5.0
linux-oracle-5.11
linux-oracle-5.13
linux-oracle-5.15 5.15.0-1097.103~20.04.1
linux-oracle-5.3
linux-oracle-5.8
linux-oracle-6.14 6.14.0-1015.15~24.04.1
linux-oracle-6.5
linux-oracle-6.8 6.8.0-1043.44~22.04.1
linux-raspi 6.8.0-1047.51
linux-raspi-realtime 6.8.0-2037.38
linux-raspi2
linux-realtime 6.8.1-1041.42
linux-realtime-6.14 6.14.0-1014.14~24.04.1
linux-realtime-6.8 6.8.1-1041.42~22.04.1
linux-riscv
linux-riscv-5.11
linux-riscv-5.15 5.15.0-1095.99~20.04.1
linux-riscv-5.19
linux-riscv-5.8
linux-riscv-6.14 6.14.0-34.34.1~24.04.1
linux-riscv-6.5
linux-riscv-6.8 6.8.0-100.100~22.04.1
linux-starfive-5.19
linux-starfive-6.2
linux-starfive-6.5
linux-xilinx 6.8.0-1023.24
linux-xilinx-zynqmp 5.15.0-1064.68

References

Similar Threats

Site Security Check

Concerned your site may already be targeted?

BotEraser analyzes incoming traffic patterns and helps identify bot behavior consistent with known exploit attempts.

Check My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.