Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68800: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (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 216afc198484fde110ebeafc017992266f4596ce, 37ca08b35a27ce8fd8e74dd3fd2ae21c23b63b73, 4049a6ace209f4ed150429f86ae796d7d6a4c22b; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1.

Low priority for now. Upgrade to Linux Linux 216afc198484fde110ebeafc017992266f4596ce, 37ca08b35a27ce8fd8e74dd3fd2ae21c23b63b73, 4049a6ace209f4ed150429f86ae796d7d6a4c22b; azl3 kernel 6.6.119.3-3 on Azure Linux 3.0 6.6.121.1-1 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: mlxsw: spectrum_mr: Fix use-after-free when updating multicast route stats Cited commit added a dedicated mutex (instead of RTNL) to protect the multicast route list, so that it will not change while the driver periodically traverses it in order to update the kernel about multicast route stats that were queried from the device. One instance of list entry deletion (during route replace) was missed and it can result in a use-after-free [1]. Fix by acquiring the mutex before deleting the entry from the list and releasing it afterwards. [1] BUG: KASAN: slab-use-after-free in mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum] Read of size 8 at addr ffff8881523c2fa8 by task kworker/2:5/22043 CPU: 2 UID: 0 PID: 22043 Comm: kworker/2:5 Not tainted 6.18.0-rc1-custom-g1a3d6d7cd014 #1 PREEMPT(full) Hardware name: Mellanox Technologies Ltd. MSN2010/SA002610, BIOS 5.6.5 08/24/2017 Workqueue: mlxsw_core mlxsw_sp_mr_stats_update [mlxsw_spectrum] Call Trace: <TASK> dump_stack_lvl+0xba/0x110 print_report+0x174/0x4f5 kasan_report+0xdf/0x110 mlxsw_sp_mr_stats_update+0x4a5/0x540 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:1006 [mlxsw_spectrum] process_one_work+0x9cc/0x18e0 worker_thread+0x5df/0xe40 kthread+0x3b8/0x730 ret_from_fork+0x3e9/0x560 ret_from_fork_asm+0x1a/0x30 </TASK> Allocated by task 29933: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x8f/0xa0 mlxsw_sp_mr_route_add+0xd8/0x4770 [mlxsw_spectrum] mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum] process_one_work+0x9cc/0x18e0 worker_thread+0x5df/0xe40 kthread+0x3b8/0x730 ret_from_fork+0x3e9/0x560 ret_from_fork_asm+0x1a/0x30 Freed by task 29933: kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_save_free_info+0x3b/0x70 __kasan_slab_free+0x43/0x70 kfree+0x14e/0x700 mlxsw_sp_mr_route_add+0x2dea/0x4770 drivers/net/ethernet/mellanox/mlxsw/spectrum_mr.c:444 [mlxsw_spectrum] mlxsw_sp_router_fibmr_event_work+0x371/0xad0 drivers/net/ethernet/mellanox/mlxsw/spectrum_router.c:7965 [mlxsw_spectrum] process_one_work+0x9cc/0x18e0 worker_thread+0x5df/0xe40 kthread+0x3b8/0x730 ret_from_fork+0x3e9/0x560 ret_from_fork_asm+0x1a/0x30

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jan 13, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 4th 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.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

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
  • No public exploit code on record
  • A fix has been released

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

Follow CVE-2025-68800

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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.

—

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.7affected
    • f38656d067257cc43b652958dd154e1ab0773701 and later · before b957366f5611bbaba03dd10ef861283347ddcc88affected · git
    • f38656d067257cc43b652958dd154e1ab0773701 and later · before 6e367c361a523a4b54fe618215c64a0ee189caf0affected · git
    • f38656d067257cc43b652958dd154e1ab0773701 and later · before 37ca08b35a27ce8fd8e74dd3fd2ae21c23b63b73affected · git
    • f38656d067257cc43b652958dd154e1ab0773701 and later · before 5f2831fc593c2b2efbff7dd0dd7441cec76adcd5affected · git
    • f38656d067257cc43b652958dd154e1ab0773701 and later · before 216afc198484fde110ebeafc017992266f4596ceaffected · git
    • f38656d067257cc43b652958dd154e1ab0773701 and later · before 4049a6ace209f4ed150429f86ae796d7d6a4c22baffected · git
    • f38656d067257cc43b652958dd154e1ab0773701 and later · before 8ac1dacec458f55f871f7153242ed6ab60373b90affected · git
    • before 5.7not affected · semver
    • 5.10.248 and later · up to and including 5.10.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.39.1.el10_16.12.0-124.39.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.39.1.el10_16.12.0-124.39.1.el10_1
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

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68795Jan 13, 2026 · ethtool: Avoid overflowing userspace buffer on stats query
    31Monitor
  • ← EarlierCVE-2025-68798Jan 13, 2026 · perf/x86/amd: Check event before enable to avoid GPF
    0Monitor
  • Later →CVE-2025-68801Jan 13, 2026 · mlxsw: spectrum_router: Fix neighbour use-after-free
    31Monitor

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 Linux216afc198484fde110ebeafc017992266f4596ceVendor (CNA)
Linux Linux37ca08b35a27ce8fd8e74dd3fd2ae21c23b63b73Vendor (CNA)
Linux Linux4049a6ace209f4ed150429f86ae796d7d6a4c22bVendor (CNA)
Linux Linux5f2831fc593c2b2efbff7dd0dd7441cec76adcd5Vendor (CNA)
Linux Linux6e367c361a523a4b54fe618215c64a0ee189caf0Vendor (CNA)
Linux Linux8ac1dacec458f55f871f7153242ed6ab60373b90Vendor (CNA)
Linux Linuxb957366f5611bbaba03dd10ef861283347ddcc88Vendor (CNA)
azl3 kernel 6.6.119.3-3 on Azure Linux 3.06.6.121.1-1 · CBL-Mariner ReleasesMicrosoft (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.1.162-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.121.1.el9_4 · Red Hat:rhel_eus:9.4::appstreamPackage registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

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.

Credits

All researchers

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.

  • CVE-2026-63979187 days apartnet/handshake: hand off the pinned file reference to accept_doit
    39Monitor
  • CVE-2026-64523193 days apartnet/handshake: Take a long-lived file reference at submit
    39Monitor
  • CVE-2026-64530194 days apartnet/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle
    39Monitor
  • CVE-2026-64541195 days apartnet/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket
    39Monitor
  • CVE-2026-64564203 days apartsctp: don't free the ASCONF's own transport in DEL-IP processing
    39Monitor
  • CVE-2026-68426209 days apartxfrm: fix stale skb->prev after async crypto steals a GSO segment
    39Monitor

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

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.

The bug in code

The whole CWE-416 class

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

Show all references (6 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records