CVE-2022-50545

Source
https://cve.org/CVERecord?id=CVE-2022-50545
Import Source
https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-50545.json
JSON Data
https://api.test.osv.dev/v1/vulns/CVE-2022-50545
Downstream
Related
Published
2025-10-07T15:21:09.288Z
Modified
2026-03-20T11:47:31.336173Z
Summary
r6040: Fix kmemleak in probe and remove
Details

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>] kmalloctrace+0x22/0x60 [<ffffffff827e20ee>] phydevicecreate+0x4e/0x90 [<ffffffff827e6072>] getphydevice+0xd2/0x220 [<ffffffff827e7844>] mdiobusscan+0xa4/0x2e0 [<ffffffff827e8be2>] _mdiobusregister+0x482/0x8b0 [<ffffffffa01f5d24>] r6040initone+0x714/0xd2c [r6040] ...

The problem occurs in probe process as follows: r6040initone: mdiobusregister mdiobusscan <- alloc and register phydevice, the reference count of phydevice is 3 r6040miiprobe phyconnect <- connect to the first phydevice, so the reference count of the first phydevice is 4, others are 3 registernetdev <- 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 phydevice is not disconnected when removes one r6040 device in r6040removeone() or on error handling path after r6040mii probed successfully. In r6040miiprobe(), a net ethernet device is connected to the first PHY device of miibus, 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 phydevice should be disconnected when removes one r6040 device or on error handling path.

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

Database specific
{
    "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50545.json",
    "cna_assigner": "Linux"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
3831861b4ad8fd0ad7110048eb3e155628799d2b
Fixed
a04707f4596952049da05756c27398c34d9a1d36
Fixed
b4448816e6a565e08236a6009c6bf48c6836cdfd
Fixed
2ce242e1b9ad31c1f68496b3548e407a8cb2c07d
Fixed
b0a61359026b57a287a48fbb4ba1d097023eca3e
Fixed
3d5f83a62e8235d235534b3dc6f197d8a822c269
Fixed
9b5b50329e2e966831a7237dd6949e7b5362a49a
Fixed
ad2c8f25457ca9a81e7e958148cbc26600ce3071
Fixed
5944c25c67de54e0aa53623e1e1af3bf8b16ed44
Fixed
7e43039a49c2da45edc1d9d7c9ede4003ab45a5f

Database specific

source
"https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2022-50545.json"