CVE-2026-72307

mlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace()

N/A
Published: August 15, 2026 at 05:55 AM UTC
Updated: August 17, 2026 at 06:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: mlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace() When mlxsw_sp_vrs_lpm_tree_replace() fails after replacing some VRs, the error rollback loop does not correctly revert the preceding replacements. The loop decrements the index but fails to update the vr pointer, which still points to the VR that caused the failure. As a result, the condition and the rollback call always operate on the same VR, potentially calling mlxsw_sp_vr_lpm_tree_replace() multiple times on it while never rolling back the earlier VRs. Those VRs continue to hold a reference to new_tree acquired via mlxsw_sp_lpm_tree_hold(), leaking the reference count of new_tree. Fix by reinitializing vr inside the error loop with the updated index: vr = &mlxsw_sp->router->vrs[i]; so that the loop correctly iterates over all VRs that were actually replaced.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.14 ≤ v < 5.10.2614.14 ≤ v < 5.15.2124.14 ≤ v < 6.1.1784.14 ≤ v < 6.12.974.14 ≤ v < 6.18.404.14 ≤ v < 6.6.1454.14 ≤ v < 7.1.54.14 ≤ v < 7.24.14fc922bb0dd9406dd9897fd47df958789891c380e
Vendor states this is fixed in 21cf8dc478a49e8de039c2739b1646a774cb1944 (fixed)
Vendor states this is fixed in 220d41bdce41fe5a39a7f419faab1e907b4093c2 (fixed)
Vendor states this is fixed in 3a2b47d1b4b3de54d030a7fdb6a322c970513ee3 (fixed)
Vendor states this is fixed in 7203ac71d3895fa5948b319dd724f0e1cffbc4a1 (fixed)
Vendor states this is fixed in 8adebf07b46df79a0e49a6d4ae384f0db7c91db6 (fixed)
Vendor states this is fixed in 9e4a6185679922305ea1df68403f00ccc512656b (fixed)
Vendor states this is fixed in c2c75c45b54f3b12eafb28a4eb47f8821512c1aa (fixed)
Vendor states this is fixed in f6454a5fbf2224ad30ec70e686a6c592561da1f2 (fixed)
Vendor states this is fixed in 4.14 (unaffected)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card