nday
CVE-2022-50545

r6040: Fix kmemleak in probe and remove

Linux / Linux

Disclosed . nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it. Not in CISA KEV.

tags weakness typeresource exhaustion accesslocalno user interaction productLinux kernel product typeoperating system
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

resource exhaustion
CWE-401, stated by NVD's analysts
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (CVSS 3.1) from NVD's analysts
Linux kernel
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernel
operating system
affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
2025-10-07T15:21Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet

Summary

In the Linux kernel, the following vulnerability has been resolved:

r6040: Fix kmemleak in probe and remove

There is a memory leaks reported by kmemleak:

unreferenced object 0xffff888116111000 (size 2048):
  comm "modprobe", pid 817, jiffies 4294759745 (age 76.502s)
  hex dump (first 32 bytes):
    00 c4 0a 04 81 88 ff ff 08 10 11 16 81 88 ff ff  ................
    08 10 11 16 81 88 ff ff 00 00 00 00 00 00 00 00  ................
  backtrace:
    [<ffffffff815bcd82>] kmalloc_trace+0x22/0x60
    [<ffffffff827e20ee>] phy_device_create+0x4e/0x90
    [<ffffffff827e6072>] get_phy_device+0xd2/0x220
    [<ffffffff827e7844>] mdiobus_scan+0xa4/0x2e0
    [<ffffffff827e8be2>] __mdiobus_register+0x482/0x8b0
    [<ffffffffa01f5d24>] r6040_init_one+0x714/0xd2c [r6040]
    ...

The problem occurs in probe process as follows:

r6040_init_one:
  mdiobus_register
    mdiobus_scan    <- alloc and register phy_device,

the reference count of phy_device is 3

r6040_mii_probe
  phy_connect     <- connect to the first phy_device,

so the reference count of the first

                     phy_device is 4, others are 3
register_netdev   <- fault inject succeeded, goto error handling path

// error handling path
err_out_mdio_unregister:
  mdiobus_unregister(lp->mii_bus);
err_out_mdio:
  mdiobus_free(lp->mii_bus);    <- the reference count of the first

phy_device is 1, it is not released and other phy_devices are released // similarly, the remove process also has the same problem

The root cause is traced to the phy_device is not disconnected when removes one r6040 device in r6040_remove_one() or on error handling path after r6040_mii probed successfully. In r6040_mii_probe(), a net ethernet device is connected to the first PHY device of mii_bus, in order to notify the connected driver when the link status changes, which is the default behavior of the PHY infrastructure to handle everything. Therefore the phy_device should be disconnected when removes one r6040 device or on error handling path.

Fix it by adding phy_disconnect() when removes one r6040 device or on error handling path after r6040_mii probed successfully.

Original text of the CVE record (cvelist), shown as published.

Event log

+DISdisclosed

CVE record published by Linux.

src cvelist · nday , bulk import · raw
{
  "id": 279767,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2022-50545",
  "occurred_at": "2025-10-07T15:21:09.288Z",
  "observed_at": "2026-11-13T05:37:51.196939Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2025-10-07T15:21:09.288Z",
    "assigner_short_name": "Linux"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.