nday
CVE-2022-50545

r6040: Fix kmemleak in probe and remove

Linux / Linux

CVE 공개: . nday가 아직 패치 근거를 수집하지 않았습니다. 패치가 없다는 뜻은 아닙니다. PoC 출처 4곳 모두 미등재. 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
현재 단계
DIS
공개
CVSS
점수 없음

생명주기

가로축 UTC. 점 = 분 단위, 넓은 막대 = 날짜만, 빈 표시 = 불명 또는 추정.
시점 알 수 없음
DIS공개
2025-10-07T15:21Z
PAT패치
아직 기록 없음
ANA분석
아직 기록 없음
POCPoC
아직 기록 없음
ITW악용
아직 기록 없음
KEVKEV
아직 기록 없음

요약

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.

이벤트 로그

+DISCVE 공개

CVE 레코드 공개(CNA: Linux).

출처 cvelist · nday 일괄 수집 · 원본
{
  "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.

연구자 논의

최근 7일간 연구자 0명이 언급

목록의 연구자가 X에서 이 CVE를 언급한 게시물입니다. 원문 그대로 보여 주며 nday는 검증하지 않습니다.

명단의 연구자가 X에서 이 CVE를 언급한 게시물은 아직 수집되지 않았습니다.

Discussion

0 comments

No comments yet.