CVE-2026-72307 — mlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace()
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ fc922bb0dd9406dd9897fd47df958789891c380e and < c2c75c45b54f3b12eafb28a4eb47f8821512c1aa≥ fc922bb0dd9406dd9897fd47df958789891c380e and < 7203ac71d3895fa5948b319dd724f0e1cffbc4a1≥ fc922bb0dd9406dd9897fd47df958789891c380e and < f6454a5fbf2224ad30ec70e686a6c592561da1f2≥ fc922bb0dd9406dd9897fd47df958789891c380e and < 220d41bdce41fe5a39a7f419faab1e907b4093c2≥ fc922bb0dd9406dd9897fd47df958789891c380e and < 9e4a6185679922305ea1df68403f00ccc512656b≥ fc922bb0dd9406dd9897fd47df958789891c380e and < 3a2b47d1b4b3de54d030a7fdb6a322c970513ee3≥ fc922bb0dd9406dd9897fd47df958789891c380e and < 8adebf07b46df79a0e49a6d4ae384f0db7c91db6≥ fc922bb0dd9406dd9897fd47df958789891c380e and < 21cf8dc478a49e8de039c2739b1646a774cb1944 and 1 moreversion 4.14 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 29, 2026 · 14 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/8adebf07b46df79a0e49a6d4ae384f0db7c91db6
- git.kernel.org/stable/c/c2c75c45b54f3b12eafb28a4eb47f8821512c1aa
- git.kernel.org/stable/c/7203ac71d3895fa5948b319dd724f0e1cffbc4a1
- git.kernel.org/stable/c/21cf8dc478a49e8de039c2739b1646a774cb1944
- git.kernel.org/stable/c/f6454a5fbf2224ad30ec70e686a6c592561da1f2
- git.kernel.org/stable/c/3a2b47d1b4b3de54d030a7fdb6a322c970513ee3
- git.kernel.org/stable/c/9e4a6185679922305ea1df68403f00ccc512656b
- git.kernel.org/stable/c/220d41bdce41fe5a39a7f419faab1e907b4093c2
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-72307 is "mlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.