Strix
56.7K

CVE-2026-72307

UnknownEPSS 0.22%

Last modified

CVE-2026-72307 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.22% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.22%

12.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= fc922bb0dd9406dd9897fd47df958789891c380e, < c2c75c45b54f3b12eafb28a4eb47f8821512c1aa; >= fc922bb0dd9406dd9897fd47df958789891c380e, < 7203ac71d3895fa5948b319dd724f0e1cffbc4a1; >= fc922bb0dd9406dd9897fd47df958789891c380e, < f6454a5fbf2224ad30ec70e686a6c592561da1f2; >= fc922bb0dd9406dd9897fd47df958789891c380e, < 220d41bdce41fe5a39a7f419faab1e907b4093c2; >= fc922bb0dd9406dd9897fd47df958789891c380e, < 9e4a6185679922305ea1df68403f00ccc512656b; >= fc922bb0dd9406dd9897fd47df958789891c380e, < 3a2b47d1b4b3de54d030a7fdb6a322c970513ee3; >= fc922bb0dd9406dd9897fd47df958789891c380e, < 8adebf07b46df79a0e49a6d4ae384f0db7c91db6; >= fc922bb0dd9406dd9897fd47df958789891c380e, < 21cf8dc478a49e8de039c2739b1646a774cb1944
LinuxLinux4.14

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-72307?
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.
How severe is CVE-2026-72307?
Severity scoring for CVE-2026-72307 is pending analysis. The EPSS model estimates a 0.22% probability of exploitation in the next 30 days.
How do I fix CVE-2026-72307?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-72307?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST