CVE-2026-72391: net: phy: sfp: free mii_bus in sfp_i2c_mdiobus_destroy
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.21% (FIRST EPSS).
- Fixed version: Linux Linux 2381bf3f484e8e4fd89a225445872ec14e036ab5, 3183b6f5510c876a1c4b4a6bdc3d0ad8940fe742, 86d379fcf1b79bdf4bc2ac891297f30f63d041d8.
Low priority for now. Upgrade to Linux Linux 2381bf3f484e8e4fd89a225445872ec14e036ab5, 3183b6f5510c876a1c4b4a6bdc3d0ad8940fe742, 86d379fcf1b79bdf4bc2ac891297f30f63d041d8 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: net: phy: sfp: free mii_bus in sfp_i2c_mdiobus_destroy sfp_i2c_mdiobus_create() allocates the I2C MDIO bus with mdio_i2c_alloc(), a plain (non-devm) allocation, and registers it. sfp_i2c_mdiobus_destroy() only unregisters the bus and clears sfp->i2c_mii without calling mdiobus_free(). As the only reference to the bus is then cleared, the struct mii_bus is leaked. This is hit whenever a copper/RollBall SFP module that instantiated an MDIO bus is removed: sfp_sm_main() takes the global teardown path and calls sfp_i2c_mdiobus_destroy(). sfp_cleanup(), on driver unbind, frees sfp->i2c_mii directly, which is why the leak only triggered on module hot-removal and not on unbind. Free the bus in sfp_i2c_mdiobus_destroy() to match the allocation done in sfp_i2c_mdiobus_create().
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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
- 6.1affected
- e85b1347ace677c3822c12d9332dfaaffe594da6 and later · before 92dd9a522f01ef57f633a8c1953cf6d48ef2bcd5affected · git
- e85b1347ace677c3822c12d9332dfaaffe594da6 and later · before d2c37f26d1a37f8177be5f354537f8ee3ec31cc2affected · git
- e85b1347ace677c3822c12d9332dfaaffe594da6 and later · before 3183b6f5510c876a1c4b4a6bdc3d0ad8940fe742affected · git
- e85b1347ace677c3822c12d9332dfaaffe594da6 and later · before 86d379fcf1b79bdf4bc2ac891297f30f63d041d8affected · git
- e85b1347ace677c3822c12d9332dfaaffe594da6 and later · before 2381bf3f484e8e4fd89a225445872ec14e036ab5affected · git
- e85b1347ace677c3822c12d9332dfaaffe594da6 and later · before 8f31efff9206f9f0adb853cad6916086aac4d5efaffected · git
- before 6.1not affected · semver
- 6.1.178 and later · up to and including 6.1.*not affected · semver
- 6.6.145 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-72386Aug 15, 2026 · drm/panthor: Fix a leak when a group is evicted before the tiler OOM is serviced0Monitor
- ← EarlierCVE-2026-72387Aug 15, 2026 · drm/panthor: Fix potential invalid pointer deref in group_process_tiler_oom()0Monitor
- Later →CVE-2026-72393Aug 15, 2026 · eth: fbnic: don't cache shinfo across skb realloc39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2381bf3f484e8e4fd89a225445872ec14e036ab5 | Vendor (CNA) |
| Linux Linux | 3183b6f5510c876a1c4b4a6bdc3d0ad8940fe742 | Vendor (CNA) |
| Linux Linux | 86d379fcf1b79bdf4bc2ac891297f30f63d041d8 | Vendor (CNA) |
| Linux Linux | 8f31efff9206f9f0adb853cad6916086aac4d5ef | Vendor (CNA) |
| Linux Linux | 92dd9a522f01ef57f633a8c1953cf6d48ef2bcd5 | Vendor (CNA) |
| Linux Linux | d2c37f26d1a37f8177be5f354537f8ee3ec31cc2 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · Debian:12 | Package 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.
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 researchersFinders, 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/3183b6f5510c876a1c4b4a6bdc3d0ad8940fe742
- git.kernel.org/stable/c/86d379fcf1b79bdf4bc2ac891297f30f63d041d8
- git.kernel.org/stable/c/8f31efff9206f9f0adb853cad6916086aac4d5ef
- git.kernel.org/stable/c/92dd9a522f01ef57f633a8c1953cf6d48ef2bcd5
- git.kernel.org/stable/c/d2c37f26d1a37f8177be5f354537f8ee3ec31cc2
Vendor advisories and official records. Exploit/PoC links are deliberately left out.