In the Linux kernel, the following vulnerabilities have been resolved: r6040: Fixed the kmemleak in the probe process and removed it. There is a memory leak 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 .................. Backtrace: [] kmallocTrace+0x22/0x60 [] phy_deviceCreate+0x4e/0x90 [] getPhyDevice+0xd2/0x220 [] mdiobusScan+0xa4/0x2e0 [] __mdiobusRegister+0x482/0x8b0 [] r6040InitOne+0x714/0xd2c [r6040] ... The problem occurs in the probe process as follows: r6040InitOne: mdiobusRegister mdiobusScan <- Allocate and register phyDevice; The reference count of phyDevice is 3 r6040_mii_probe phyConnect <- Connect to the first phyDevice; Therefore, the reference count of the first phyDevice is 4, and the others are 3 register_netdev <- Fault injection succeeded; go to error handling path // Error handling path err_out_mdioUnregister: mdiobusUnregister(lp->miiBus); err_out_mdio: mdiobusFree(lp->miiBus); <- The reference count of the first phyDevice is 1; it is not released, and other phyDevices are released // Similarly, the remove process also has the same problem The root cause is traced to the fact that the phyDevice is not disconnected when removing one r6040 device in r6040RemoveOne() or during the error handling path after r6040_mii_probe() is successful. In r6040_mii_probe(), 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. This is the default behavior of the PHY infrastructure to handle everything. Therefore, the phyDevice should be disconnected when removing one r6040 device or during the error handling path. This issue is fixed by adding the phyDisconnect() function when removing one r6040 device or during the error handling path after r6040_mii_probe() is successful.