CVE-2022-49926

/// Technical description

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

net: dsa: Fix possible memory leaks in dsa_loop_init()

kmemleak reported memory leaks in dsa_loop_init():

kmemleak: 12 new suspected memory leaks

unreferenced object 0xffff8880138ce000 (size 2048):

comm "modprobe", pid 390, jiffies 4295040478 (age 238.976s)

backtrace:

[<000000006a94f1d5>] kmalloc_trace+0x26/0x60

[<00000000a9c44622>] phy_device_create+0x5d/0x970

[<00000000d0ee2afc>] get_phy_device+0xf3/0x2b0

[<00000000dca0c71f>] __fixed_phy_register.part.0+0x92/0x4e0

[<000000008a834798>] fixed_phy_register+0x84/0xb0

[<0000000055223fcb>] dsa_loop_init+0xa9/0x116 [dsa_loop]

...

There are two reasons for memleak in dsa_loop_init().

First, fixed_phy_register() create and register phy_device:

fixed_phy_register()

get_phy_device()

phy_device_create() # freed by phy_device_free()

phy_device_register() # freed by phy_device_remove()

But fixed_phy_unregister() only calls phy_device

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References