The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-987106 advisory.

    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_remove().
    So the memory allocated in phy_device_create() is leaked.

    Second, when mdio_driver_register() fail in dsa_loop_init(),     it just returns and there is no cleanup for phydevs.

    Fix the problems by catching the error of mdio_driver_register()     in dsa_loop_init(), then calling both fixed_phy_unregister() and     phy_device_free() to release phydevs.
    Also add a function for phydevs cleanup to avoid duplacate.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-989728 advisory.

    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_remove().
    So the memory allocated in phy_device_create() is leaked.

    Second, when mdio_driver_register() fail in dsa_loop_init(),     it just returns and there is no cleanup for phydevs.

    Fix the problems by catching the error of mdio_driver_register()     in dsa_loop_init(), then calling both fixed_phy_unregister() and     phy_device_free() to release phydevs.
    Also add a function for phydevs cleanup to avoid duplacate.

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - 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_remove(). So the memory allocated in     phy_device_create() is leaked. Second, when mdio_driver_register() fail in dsa_loop_init(), it just     returns and there is no cleanup for phydevs. Fix the problems by catching the error of     mdio_driver_register() in dsa_loop_init(), then calling both fixed_phy_unregister() and phy_device_free()     to release phydevs. Also add a function for phydevs cleanup to avoid duplacate. (CVE-2022-49926)

Note that Nessus relies on the presence of the package as reported by the vendor.

An update of the linux package has been released.

ID	Name	Product	Family	Published	Updated	Severity
268323	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-987106)	Nessus	Unity Linux Local Security Checks	10/7/2025	10/15/2025	medium
273791	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989728)	Nessus	Unity Linux Local Security Checks	11/5/2025	11/5/2025	medium
246253	Linux Distros Unpatched Vulnerability : CVE-2022-49926	Nessus	Misc.	8/8/2025	10/28/2025	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	7/22/2021	3/23/2026	high

Detections

Analytics

Plugins Search

medium

medium

medium

high