Skip to content
Noroxi
CVE-2026-72307· NVD / CVE Program· CNA Linux

mlxsw: fix refcount leak in mlxsw_sp_vrs_lpm_tree_replace()

Noroxi assessment

Priority: Monitor (action score 0/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.22% (FIRST EPSS).
  • Fixed version: Linux Linux 21cf8dc478a49e8de039c2739b1646a774cb1944, 220d41bdce41fe5a39a7f419faab1e907b4093c2, 3a2b47d1b4b3de54d030a7fdb6a322c970513ee3.

Low priority for now. Upgrade to Linux Linux 21cf8dc478a49e8de039c2739b1646a774cb1944, 220d41bdce41fe5a39a7f419faab1e907b4093c2, 3a2b47d1b4b3de54d030a7fdb6a322c970513ee3 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: 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.

—No exploit Fix available
Published
Aug 15, 2026
Updated
Aug 17, 2026
EPSS
0.2% · 11th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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-2026-72307

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

    • 4.14affected
    • fc922bb0dd9406dd9897fd47df958789891c380e and later · before c2c75c45b54f3b12eafb28a4eb47f8821512c1aaaffected · git
    • fc922bb0dd9406dd9897fd47df958789891c380e and later · before 7203ac71d3895fa5948b319dd724f0e1cffbc4a1affected · git
    • fc922bb0dd9406dd9897fd47df958789891c380e and later · before f6454a5fbf2224ad30ec70e686a6c592561da1f2affected · git
    • fc922bb0dd9406dd9897fd47df958789891c380e and later · before 220d41bdce41fe5a39a7f419faab1e907b4093c2affected · git
    • fc922bb0dd9406dd9897fd47df958789891c380e and later · before 9e4a6185679922305ea1df68403f00ccc512656baffected · git
    • fc922bb0dd9406dd9897fd47df958789891c380e and later · before 3a2b47d1b4b3de54d030a7fdb6a322c970513ee3affected · git
    • fc922bb0dd9406dd9897fd47df958789891c380e and later · before 8adebf07b46df79a0e49a6d4ae384f0db7c91db6affected · git
    • fc922bb0dd9406dd9897fd47df958789891c380e and later · before 21cf8dc478a49e8de039c2739b1646a774cb1944affected · git
    • before 4.14not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-1

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-2026-72305Aug 15, 2026 · VDUSE: avoid leaking information to userspace
    0Monitor
  • ← EarlierCVE-2026-72306Aug 15, 2026 · vduse: Fix race in vduse_dev_msg_sync and vduse_dev_read_iter
    0Monitor
  • Later →CVE-2026-72308Aug 15, 2026 · mlxsw: fix refcount leak in mlxsw_sp_port_lag_join()
    0Monitor

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 Linux21cf8dc478a49e8de039c2739b1646a774cb1944Vendor (CNA)
Linux Linux220d41bdce41fe5a39a7f419faab1e907b4093c2Vendor (CNA)
Linux Linux3a2b47d1b4b3de54d030a7fdb6a322c970513ee3Vendor (CNA)
Linux Linux7203ac71d3895fa5948b319dd724f0e1cffbc4a1Vendor (CNA)
Linux Linux8adebf07b46df79a0e49a6d4ae384f0db7c91db6Vendor (CNA)
Linux Linux9e4a6185679922305ea1df68403f00ccc512656bVendor (CNA)
Linux Linuxc2c75c45b54f3b12eafb28a4eb47f8821512c1aaVendor (CNA)
Linux Linuxf6454a5fbf2224ad30ec70e686a6c592561da1f2Vendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

No nightly-computed relations.

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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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 (7 more)

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

All records