Linux Kernel up to 7.1.4 mlxsw mlxsw_sp_vrs_lpm_tree_replace reference count

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.5$0-$5k0.00

Summaryinfo

A vulnerability identified as very critical has been detected in Linux Kernel up to 7.1.4. Affected by this issue is the function mlxsw_sp_vrs_lpm_tree_replace of the component mlxsw. This manipulation causes reference count. This vulnerability is handled as CVE-2026-72307. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability has been found in Linux Kernel up to 7.1.4 and classified as very critical. Affected by this vulnerability is the function mlxsw_sp_vrs_lpm_tree_replace of the component mlxsw. The manipulation with an unknown input leads to a reference count vulnerability. The CWE definition for the vulnerability is CWE-911. The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-72307 since 08/09/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/15/2026).

Upgrading to version 5.10.261, 5.15.212, 6.1.178, 6.6.145, 6.12.97, 6.18.40, 7.1.5 or 7.2-rc1 eliminates this vulnerability. Applying the patch c2c75c45b54f3b12eafb28a4eb47f8821512c1aa/7203ac71d3895fa5948b319dd724f0e1cffbc4a1/f6454a5fbf2224ad30ec70e686a6c592561da1f2/220d41bdce41fe5a39a7f419faab1e907b4093c2/9e4a6185679922305ea1df68403f00ccc512656b/3a2b47d1b4b3de54d030a7fdb6a322c970513ee3/8adebf07b46df79a0e49a6d4ae384f0db7c91db6/21cf8dc478a49e8de039c2739b1646a774cb1944 is able to eliminate this problem.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.5

VulDB Base Score: 10.0
VulDB Temp Score: 9.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Reference count
CWE: CWE-911 / CWE-664
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.10.261/5.15.212/6.1.178/6.6.145/6.12.97/6.18.40/7.1.5/7.2-rc1
Patch: c2c75c45b54f3b12eafb28a4eb47f8821512c1aa/7203ac71d3895fa5948b319dd724f0e1cffbc4a1/f6454a5fbf2224ad30ec70e686a6c592561da1f2/220d41bdce41fe5a39a7f419faab1e907b4093c2/9e4a6185679922305ea1df68403f00ccc512656b/3a2b47d1b4b3de54d030a7fdb6a322c970513ee3/8adebf07b46df79a0e49a6d4ae384f0db7c91db6/21cf8dc478a49e8de039c2739b1646a774cb1944

Timelineinfo

08/09/2026 CVE reserved
08/15/2026 +6 days Advisory disclosed
08/15/2026 +0 days VulDB entry created
08/15/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-72307 (🔒)
GCVE (CVE): GCVE-0-2026-72307
GCVE (VulDB): GCVE-100-390721

Entryinfo

Created: 08/15/2026 14:25
Changes: 08/15/2026 14:25 (59)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!