CVE-2022-50545
published 2025-10-07CVE-2022-50545: 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…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.20%
9.5th percentile
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:
[] kmalloc_trace+0x22/0x60
[] phy_device_create+0x4e/0x90
[] get_phy_device+0xd2/0x220
[] mdiobus_scan+0xa4/0x2e0
[] __mdiobus_register+0x482/0x8b0
[] r6040_init_one+0x714/0xd2c [r6040]
...
The problem occurs in probe process as follows:
r6040_init_one:
mdiobus_register
mdiobus_scan 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.
Affected
23 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.4-1 (bookworm) | linux 6.1.4-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 3831861b4ad8fd0ad7110048eb3e155628799d2b < a04707f4596952049da05756c27398c34d9a1d36 | a04707f4596952049da05756c27398c34d9a1d36 |
| linux | linux | >= 3831861b4ad8fd0ad7110048eb3e155628799d2b < b4448816e6a565e08236a6009c6bf48c6836cdfd | b4448816e6a565e08236a6009c6bf48c6836cdfd |
| linux | linux | >= 3831861b4ad8fd0ad7110048eb3e155628799d2b < 2ce242e1b9ad31c1f68496b3548e407a8cb2c07d | 2ce242e1b9ad31c1f68496b3548e407a8cb2c07d |
| linux | linux | >= 3831861b4ad8fd0ad7110048eb3e155628799d2b < b0a61359026b57a287a48fbb4ba1d097023eca3e | b0a61359026b57a287a48fbb4ba1d097023eca3e |
| linux | linux | >= 3831861b4ad8fd0ad7110048eb3e155628799d2b < 3d5f83a62e8235d235534b3dc6f197d8a822c269 | 3d5f83a62e8235d235534b3dc6f197d8a822c269 |
| linux | linux | >= 3831861b4ad8fd0ad7110048eb3e155628799d2b < 9b5b50329e2e966831a7237dd6949e7b5362a49a | 9b5b50329e2e966831a7237dd6949e7b5362a49a |
| linux | linux | >= 3831861b4ad8fd0ad7110048eb3e155628799d2b < ad2c8f25457ca9a81e7e958148cbc26600ce3071 | ad2c8f25457ca9a81e7e958148cbc26600ce3071 |
| linux | linux | >= 3831861b4ad8fd0ad7110048eb3e155628799d2b < 5944c25c67de54e0aa53623e1e1af3bf8b16ed44 | 5944c25c67de54e0aa53623e1e1af3bf8b16ed44 |
| linux | linux | >= 3831861b4ad8fd0ad7110048eb3e155628799d2b < 7e43039a49c2da45edc1d9d7c9ede4003ab45a5f | 7e43039a49c2da45edc1d9d7c9ede4003ab45a5f |
| linux | linux_kernel | >= 0 < 5.10.178-1 | 5.10.178-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 0 < 6.1.4-1 | 6.1.4-1 |
| linux | linux_kernel | >= 2.6.36 < 4.9.337 | 4.9.337 |
| linux | linux_kernel | >= 4.10 < 4.14.303 | 4.14.303 |
| linux | linux_kernel | >= 4.15 < 4.19.270 | 4.19.270 |
| linux | linux_kernel | >= 4.20 < 5.4.229 | 5.4.229 |
| linux | linux_kernel | >= 5.11 < 5.15.86 | 5.15.86 |
| linux | linux_kernel | >= 5.16 < 6.0.16 | 6.0.16 |
| linux | linux_kernel | >= 5.5 < 5.10.163 | 5.10.163 |
| linux | linux_kernel | >= 6.1 < 6.1.2 | 6.1.2 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: r6040: Fix kmemleak in probe and remove
vendor_redhat·2025-10-07·CVSS 5.5
CVE-2022-50545 [MEDIUM] kernel: r6040: Fix kmemleak in probe and remove
kernel: r6040: Fix kmemleak in probe and remove
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:
[] kmalloc_trace+0x22/0x60
[] phy_device_create+0x4e/0x90
[] get_phy_device+0xd2/0x220
[] mdiobus_scan+0xa4/0x2e0
[] __mdiobus_register+0x482/0x8b0
[] r6040_init_one+0x714/0xd2c [r6040]
...
The problem occurs in probe process as follows:
r6040_init_one:
mdiobus_register
mdiobus_scan mii_bus);
err_out_mdio:
mdiobus_fr
Debian
CVE-2022-50545: linux - In the Linux kernel, the following vulnerability has been resolved: r6040: Fix ...
vendor_debian·2022·CVSS 5.5
CVE-2022-50545 [MEDIUM] CVE-2022-50545: linux - In the Linux kernel, the following vulnerability has been resolved: r6040: Fix ...
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: [] kmalloc_trace+0x22/0x60 [] phy_device_create+0x4e/0x90 [] get_phy_device+0xd2/0x220 [] mdiobus_scan+0xa4/0x2e0 [] __mdiobus_register+0x482/0x8b0 [] r6040_init_one+0x714/0xd2c [r6040] ... The problem occurs in probe process as follows: r6040_init_one: mdiobus_register mdiobus_scan mii_bus); err_out_mdio: mdiobus_free(lp->mii_bus); <- the reference count of the fi
VulDB
Linux Kernel up to 6.1.1 r6040_remove_one reference count (EUVD-2025-32019 / Nessus ID 279908)
vuldb·2026-04-20·CVSS 5.5
CVE-2022-50545 [MEDIUM] Linux Kernel up to 6.1.1 r6040_remove_one reference count (EUVD-2025-32019 / Nessus ID 279908)
A vulnerability was found in Linux Kernel up to 6.1.1. It has been rated as critical. This affects the function r6040_remove_one. This manipulation causes improper update of reference count.
The identification of this vulnerability is CVE-2022-50545. The attack needs to be done within the local network. There is no exploit available.
Upgrading the affected component is advised.
GHSA
GHSA-2q87-gcq9-5rfq: In the Linux kernel, the following vulnerability has been resolved:
r6040: Fix kmemleak in probe and remove
There is a memory leaks reported by kmem
ghsa_unreviewed·2025-10-07
CVE-2022-50545 [MEDIUM] CWE-401 GHSA-2q87-gcq9-5rfq: In the Linux kernel, the following vulnerability has been resolved:
r6040: Fix kmemleak in probe and remove
There is a memory leaks reported by kmem
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:
[] kmalloc_trace+0x22/0x60
[] phy_device_create+0x4e/0x90
[] get_phy_device+0xd2/0x220
[] mdiobus_scan+0xa4/0x2e0
[] __mdiobus_register+0x482/0x8b0
[] r6040_init_one+0x714/0xd2c [r6040]
...
The problem occurs in probe process as follows:
r6040_init_one:
mdiobus_register
mdiobus_scan mii_bus);
err_out_mdio:
mdiobus_free(lp->mii_bus); <- the reference count of th
OSV
CVE-2022-50545: In the Linux kernel, the following vulnerability has been resolved: r6040: Fix kmemleak in probe and remove There is a memory leaks reported by kmemle
osv·2025-10-07·CVSS 5.5
CVE-2022-50545 [MEDIUM] CVE-2022-50545: In the Linux kernel, the following vulnerability has been resolved: r6040: Fix kmemleak in probe and remove There is a memory leaks reported by kmemle
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: [] kmalloc_trace+0x22/0x60 [] phy_device_create+0x4e/0x90 [] get_phy_device+0xd2/0x220 [] mdiobus_scan+0xa4/0x2e0 [] __mdiobus_register+0x482/0x8b0 [] r6040_init_one+0x714/0xd2c [r6040] ... The problem occurs in probe process as follows: r6040_init_one: mdiobus_register mdiobus_scan mii_bus); err_out_mdio: mdiobus_free(lp->mii_bus); <- the reference count of the fi
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/2ce242e1b9ad31c1f68496b3548e407a8cb2c07dhttps://git.kernel.org/stable/c/3d5f83a62e8235d235534b3dc6f197d8a822c269https://git.kernel.org/stable/c/5944c25c67de54e0aa53623e1e1af3bf8b16ed44https://git.kernel.org/stable/c/7e43039a49c2da45edc1d9d7c9ede4003ab45a5fhttps://git.kernel.org/stable/c/9b5b50329e2e966831a7237dd6949e7b5362a49ahttps://git.kernel.org/stable/c/a04707f4596952049da05756c27398c34d9a1d36https://git.kernel.org/stable/c/ad2c8f25457ca9a81e7e958148cbc26600ce3071https://git.kernel.org/stable/c/b0a61359026b57a287a48fbb4ba1d097023eca3ehttps://git.kernel.org/stable/c/b4448816e6a565e08236a6009c6bf48c6836cdfd
2025-10-07
Published