Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2021-47416phy: mdio: fix memory leak

Description

In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but device_register() was called In case of device_register() has been called we should call put_device() to correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of MDIOBUS_ALLOCATED state To avoid this behaviour we need to set bus->state to MDIOBUS_UNREGISTERED _before_ calling device_register(), because put_device() should be called even in case of device_register() failure.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 24 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2021-47416, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.23% · top 86% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 46abc02175b3c246dd5141d878f565a8725060c9 – < 25e9f88c7e3cc35f5e3d3db199660d28a15df639
    • affected 46abc02175b3c246dd5141d878f565a8725060c9 – < 2250392d930bd0d989f24d355d6355b0150256e7
    • affected 46abc02175b3c246dd5141d878f565a8725060c9 – < f4f502a04ee1e543825af78f47eb7785015cd9f6
    • affected 46abc02175b3c246dd5141d878f565a8725060c9 – < 2397b9e118721292429fea8807a698e71b94795f
    • affected 46abc02175b3c246dd5141d878f565a8725060c9 – < 414bb4ead1362ef2c8592db723c017258f213988
    • affected 46abc02175b3c246dd5141d878f565a8725060c9 – < 0d2dd40a7be61b89a7c99dae8ee96389d27b413a
    • affected 46abc02175b3c246dd5141d878f565a8725060c9 – < 064c2616234a7394867c924b5c1303974f3a4f4d
    • affected 46abc02175b3c246dd5141d878f565a8725060c9 – < ca6e11c337daf7925ff8a2aac8e84490a8691905
  • Linux · Linux

    • affected 2.6.28
    • unaffected < 2.6.28
    • unaffected 4.4.289 – ≤ 4.4.*
    • unaffected 4.9.287 – ≤ 4.9.*
    • unaffected 4.14.251 – ≤ 4.14.*
    • unaffected 4.19.211 – ≤ 4.19.*
    • unaffected 5.4.153 – ≤ 5.4.*
    • unaffected 5.10.73 – ≤ 5.10.*
    • unaffected 5.14.12 – ≤ 5.14.*
    • unaffected 5.15 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2021-47416 badge
[![CVE-2021-47416](https://cveledger.app/badge/CVE-2021-47416.svg)](https://cveledger.app/cve/CVE-2021-47416)

Record last updated .