Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38248: bridge: mcast: Fix use-after-free during router port configuration

Noroxi assessment

Priority: Monitor (action score 31/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 4d3c2a1d4c7c33103f1ddfdbc5cfe1ea4f6d0dcd, 5df2d582f6e8a81e7ab066464845b38b2fb04094, 7544f3f5b0b58c396f374d060898b5939da31709; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.

Low priority for now. Upgrade to Linux Linux 4d3c2a1d4c7c33103f1ddfdbc5cfe1ea4f6d0dcd, 5df2d582f6e8a81e7ab066464845b38b2fb04094, 7544f3f5b0b58c396f374d060898b5939da31709; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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: <TASK> dump_stack ---truncated---

HighCVSS 7.8 · v3.1—Proof of concept Fix available
Published
Jul 9, 2025
Updated
Oct 30, 2026
EPSS
0.3% · 22th percentile

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.8
CNA · Linux
7.8
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-38248

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.15 and later · before 6.15.5
  • linux linux kernel6.16

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.15affected
    • 2796d846d74a18cc6563e96eff8bf28c5e06f912 and later · before 5df2d582f6e8a81e7ab066464845b38b2fb04094affected · git
    • 2796d846d74a18cc6563e96eff8bf28c5e06f912 and later · before 7bb080340bb5ffc928f47c563a9ca1528ce54911affected · git
    • 2796d846d74a18cc6563e96eff8bf28c5e06f912 and later · before 4d3c2a1d4c7c33103f1ddfdbc5cfe1ea4f6d0dcdaffected · git
    • 2796d846d74a18cc6563e96eff8bf28c5e06f912 and later · before bdced577da71b118b6ed4242ebd47f81bf54d406affected · git
    • 2796d846d74a18cc6563e96eff8bf28c5e06f912 and later · before f05a4f9e959e0fc098046044c650acf897ea52d2affected · git
    • 2796d846d74a18cc6563e96eff8bf28c5e06f912 and later · before 7544f3f5b0b58c396f374d060898b5939da31709affected · git
    • before 5.15not affected · semver
    • 5.15.224 and later · up to and including 5.15.*not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38245Jul 9, 2025 · atm: Release atm_dev_mutex after removing procfs in atm_dev_deregister().
    31Monitor
  • ← EarlierCVE-2025-38246Jul 9, 2025 · bnxt: properly flush XDP redirect lists
    22Monitor
  • Later →CVE-2025-38249Jul 9, 2025 · ALSA: usb-audio: Fix out-of-bounds read in snd_usb_get_audioformat_uac3()
    28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux4d3c2a1d4c7c33103f1ddfdbc5cfe1ea4f6d0dcdVendor (CNA)
Linux Linux5df2d582f6e8a81e7ab066464845b38b2fb04094Vendor (CNA)
Linux Linux7544f3f5b0b58c396f374d060898b5939da31709Vendor (CNA)
Linux Linux7bb080340bb5ffc928f47c563a9ca1528ce54911Vendor (CNA)
Linux Linuxbdced577da71b118b6ed4242ebd47f81bf54d406Vendor (CNA)
Linux Linuxf05a4f9e959e0fc098046044c650acf897ea52d2Vendor (CNA)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.107.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.12.69-1 · Debian:13Package registry (OSV)
red hat:bpftool0:4.18.0-553.107.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.107.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.107.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.107.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.107.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.107.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.107.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-553.107.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-553.107.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-553.107.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+2

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:02026-01-22

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+197 d
  3. TodayNov 8, 2026+487 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records