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>] kmalloc_trace+0x22/0x60 [<ffffffff827e20ee>] phy_device_create+0x4e/0x90 [<ffffffff827e6072>] get_phy_device+0xd2/0x220 [<ffffffff827e7844>] mdiobus_scan+0xa4/0x2e0 [<ffffffff827e8be2>] __mdiobus_register+0x482/0x8b0 [<ffffffffa01f5d24>] r6040_init_one+0x714/0xd2c [r6040] ... The problem occurs in probe process as follows: r6040_init_one: mdiobus_register mdiobus_scan <- alloc and register phy_device, the reference count of phy_device is 3 r6040_mii_probe phy_connect <- connect to the first phy_device, so the reference count of the first phy_device is 4, others are 3 register_netdev <- 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 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.

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

    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>] kmalloc_trace+0x22/0x60           [<ffffffff827e20ee>] phy_device_create+0x4e/0x90           [<ffffffff827e6072>] get_phy_device+0xd2/0x220           [<ffffffff827e7844>] mdiobus_scan+0xa4/0x2e0           [<ffffffff827e8be2>] __mdiobus_register+0x482/0x8b0           [<ffffffffa01f5d24>] r6040_init_one+0x714/0xd2c [r6040]           ...

    The problem occurs in probe process as follows:
      r6040_init_one:
        mdiobus_register           mdiobus_scan    <- alloc and register phy_device,                              the reference count of phy_device is 3         r6040_mii_probe           phy_connect     <- connect to the first phy_device,                              so the reference count of the first                              phy_device is 4, others are 3         register_netdev   <- 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 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.

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-2026-006932 advisory.

    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>] kmalloc_trace+0x22/0x60           [<ffffffff827e20ee>] phy_device_create+0x4e/0x90           [<ffffffff827e6072>] get_phy_device+0xd2/0x220           [<ffffffff827e7844>] mdiobus_scan+0xa4/0x2e0           [<ffffffff827e8be2>] __mdiobus_register+0x482/0x8b0           [<ffffffffa01f5d24>] r6040_init_one+0x714/0xd2c [r6040]           ...

    The problem occurs in probe process as follows:
      r6040_init_one:
        mdiobus_register           mdiobus_scan    <- alloc and register phy_device,                              the reference count of phy_device is 3         r6040_mii_probe           phy_connect     <- connect to the first phy_device,                              so the reference count of the first                              phy_device is 4, others are 3         register_netdev   <- 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 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.

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 remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:4320-1 advisory.

    The SUSE Linux Enterprise 15 SP5 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2022-50327: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value (bsc#1249859).
    - CVE-2022-50334: hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() (bsc#1249857).
    - CVE-2022-50490: bpf: Propagate error from htab_lock_bucket() to userspace (bsc#1251164).
    - CVE-2022-50516: fs: dlm: fix invalid derefence of sb_lvbptr (bsc#1251741).
    - CVE-2023-53365: ip6mr: Fix skb_under_panic in ip6mr_cache_report() (bsc#1249988).
    - CVE-2023-53500: xfrm: fix slab-use-after-free in decode_session6 (bsc#1250816).
    - CVE-2023-53559: ip_vti: fix potential slab-use-after-free in decode_session6 (bsc#1251052).
    - CVE-2023-53574: wifi: rtw88: delete timer and free skb queue when unloading (bsc#1251222).
    - CVE-2023-53619: netfilter: conntrack: Avoid nf_ct_helper_hash uses after free (bsc#1251743).
    - CVE-2023-53673: Bluetooth: hci_event: call disconnect callback before deleting conn (bsc#1251763).
    - CVE-2023-53705: ipv6: Fix out-of-bounds access in ipv6_find_tlv() (bsc#1252554).
    - CVE-2025-37885: KVM: x86: Reset IRTE to host control if *new* route isn't postable (bsc#1242960).
    - CVE-2025-38084: hugetlb: unshare some PMDs when splitting VMAs (bsc#1245498).
    - CVE-2025-38085: mm/hugetlb: fix huge_pmd_unshare() vs GUP-fast race (bsc#1245499).
    - CVE-2025-38476: rpl: Fix use-after-free in rpl_do_srh_inline() (bsc#1247317).
    - CVE-2025-39742: RDMA: hfi1: fix possible divide-by-zero in find_hw_thread_mask() (bsc#1249479).
    - CVE-2025-39797: xfrm: Duplicate SPI Handling (bsc#1249608).
    - CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task (bsc#1251230).
    - CVE-2025-39967: fbcon: fix integer overflow in fbcon_do_set_font (bsc#1252033).
    - CVE-2025-39968: i40e: add max boundary check for VF filters (bsc#1252047).
    - CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035).
    - CVE-2025-39978: octeontx2-pf: Fix potential use after free in otx2_tc_add_flow() (bsc#1252069).
    - CVE-2025-39981: Bluetooth: MGMT: Fix possible UAFs (bsc#1252060).
    - CVE-2025-40018: ipvs: Defer ip_vs_ftp unregister during netns cleanup (bsc#1252688).
    - CVE-2025-40044: fs: udf: fix OOB read in lengthAllocDescs handling (bsc#1252785).

    The following non security issues were fixed:

    - NFS: remove revoked delegation from server's delegation list (bsc#1246211).
    - NFSv4: Allow FREE_STATEID to clean up delegations (bsc#1246211).
    - fbcon: Fix OOB access in font allocation (bsc#1252033)
    - kabi fix for NFSv4: Allow FREE_STATEID to clean up delegations (bsc#1246211).
    - kernel-subpackage-spec: Do not doubly-sign modules (bsc#1251930).
    - mm: avoid unnecessary page fault retires on shared memory types (bsc#1251823).
    - net: hv_netvsc: fix loss of early receive events from host during channel open (bsc#1252265).
    - net: mana: Switch to page pool for jumbo frames (bsc#1248754).
    - net: mana: Use page pool fragments for RX buffers instead of full pages to improve memory efficiency     (bsc#1248754).
    - netfilter: nft_objref: validate objref and objrefmap expressions (bsc#1250237).
    - rpm/check-for-config-changes: ignore CONFIG_SCHED_PROXY_EXEC, too (bsc#1250946)

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

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

The remote SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:4515-1 advisory.

    The SUSE Linux Enterprise 12 SP5 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2022-50364: i2c: mux: reg: check return value after calling platform_get_resource() (bsc#1250083).
    - CVE-2022-50368: drm/msm/dsi: fix memory corruption with too many bridges (bsc#1250009).
    - CVE-2022-50494: thermal: intel_powerclamp: Use get_cpu() instead of smp_processor_id() to avoid crash     (bsc#1251173).
    - CVE-2022-50545: r6040: Fix kmemleak in probe and remove (bsc#1251285).
    - CVE-2022-50551: wifi: brcmfmac: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request()     (bsc#1251322).
    - CVE-2022-50569: xfrm: Update ipcomp_scratches with NULL when freed (bsc#1252640).
    - CVE-2022-50578: class: fix possible memory leak in __class_register() (bsc#1252519).
    - CVE-2023-53229: wifi: mac80211: fix invalid drv_sta_pre_rcu_remove calls for non-uploaded sta     (bsc#1249650).
    - CVE-2023-53369: net: dcb: choose correct policy to parse DCB_ATTR_BCN (bsc#1250206).
    - CVE-2023-53431: scsi: ses: Don't attach if enclosure has no components (bsc#1250374).
    - CVE-2023-53542: ARM: dts: exynos: Use Exynos5420 compatible for the MIPI video phy (bsc#1251154).
    - CVE-2023-53597: cifs: fix mid leak during reconnection after timeout threshold (bsc#1251159).
    - CVE-2023-53641: wifi: ath9k: hif_usb: fix memory leak of remain_skbs (bsc#1251728).
    - CVE-2023-53676: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() (bsc#1251786).
    - CVE-2025-38436: drm/scheduler: signal scheduled fence when kill job (bsc#1247227).
    - CVE-2025-39819: fs/smb: Fix inconsistent refcnt update (bsc#1250176).
    - CVE-2025-39967: fbcon: fix integer overflow in fbcon_do_set_font (bsc#1252033).
    - CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue (bsc#1252303).
    - CVE-2025-40027: net/9p: fix double req put in p9_fd_cancelled (bsc#1252763).
    - CVE-2025-40030: pinctrl: check the return value of pinmux_ops::get_function_name() (bsc#1252773).
    - CVE-2025-40040: mm/ksm: fix flag-dropping behavior in ksm_madvise (bsc#1252780).
    - CVE-2025-40048: uio_hv_generic: Let userspace take care of interrupt mask (bsc#1252862).
    - CVE-2025-40055: ocfs2: fix double free in user_cluster_connect() (bsc#1252821).
    - CVE-2025-40070: pps: fix warning in pps_register_cdev when register device fail (bsc#1252836).
    - CVE-2025-40083: net/sched: sch_qfq: Fix null-deref in agg_dequeue (bsc#1252912).
    - CVE-2025-40173: net/ip6_tunnel: Prevent perpetual tunnel growth (bsc#1253421).
    - CVE-2025-40204: sctp: Fix MAC comparison to be constant-time (bsc#1253436).
    - CVE-2025-40205: btrfs: avoid potential out-of-bounds in btrfs_encode_fh() (bsc#1253456).


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

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

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:4111-1 advisory.

    The SUSE Linux Enterprise 15 SP4 kernel was updated to fix various security issues

    The following security issues were fixed:

    - CVE-2022-50327: ACPI: processor: idle: Check acpi_fetch_acpi_dev() return value (bsc#1249859).
    - CVE-2022-50334: hugetlbfs: fix null-ptr-deref in hugetlbfs_parse_param() (bsc#1249857).
    - CVE-2022-50490: bpf: Propagate error from htab_lock_bucket() to userspace (bsc#1251164).
    - CVE-2022-50516: fs: dlm: fix invalid derefence of sb_lvbptr (bsc#1251741).
    - CVE-2023-53365: ip6mr: Fix skb_under_panic in ip6mr_cache_report() (bsc#1249988).
    - CVE-2023-53500: xfrm: fix slab-use-after-free in decode_session6 (bsc#1250816).
    - CVE-2023-53559: ip_vti: fix potential slab-use-after-free in decode_session6 (bsc#1251052).
    - CVE-2023-53574: wifi: rtw88: delete timer and free skb queue when unloading (bsc#1251222).
    - CVE-2023-53619: netfilter: conntrack: Avoid nf_ct_helper_hash uses after free (bsc#1251743).
    - CVE-2023-53673: Bluetooth: hci_event: call disconnect callback before deleting conn (bsc#1251763).
    - CVE-2023-53705: ipv6: Fix out-of-bounds access in ipv6_find_tlv() (bsc#1252554).
    - CVE-2025-39742: RDMA: hfi1: fix possible divide-by-zero in find_hw_thread_mask() (bsc#1249479).
    - CVE-2025-39945: cnic: Fix use-after-free bugs in cnic_delete_task (bsc#1251230).
    - CVE-2025-39967: fbcon: fix integer overflow in fbcon_do_set_font (bsc#1252033).
    - CVE-2025-39968: i40e: add max boundary check for VF filters (bsc#1252047).
    - CVE-2025-39973: i40e: add validation for ring_len param (bsc#1252035).
    - CVE-2025-39978: octeontx2-pf: Fix potential use after free in otx2_tc_add_flow() (bsc#1252069).
    - CVE-2025-40018: ipvs: Defer ip_vs_ftp unregister during netns cleanup (bsc#1252688).
    - CVE-2025-40044: fs: udf: fix OOB read in lengthAllocDescs handling (bsc#1252785).
    - CVE-2025-40088: hfsplus: fix slab-out-of-bounds read in hfsplus_strcasecmp() (bsc#1252904).
    - CVE-2025-40102: KVM: arm64: Prevent access to vCPU events before init (bsc#1252919).

    The following non security issues were fixed:

    - fbcon: Fix OOB access in font allocation (bsc#1252033)
    - mm: avoid unnecessary page fault retires on shared memory types (bsc#1251823).
    - net: hv_netvsc: fix loss of early receive events from host during channel open (bsc#1252265).

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

Note that Nessus has not tested for these issues 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.

  - 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>] kmalloc_trace+0x22/0x60     [<ffffffff827e20ee>] phy_device_create+0x4e/0x90 [<ffffffff827e6072>] get_phy_device+0xd2/0x220     [<ffffffff827e7844>] mdiobus_scan+0xa4/0x2e0 [<ffffffff827e8be2>] __mdiobus_register+0x482/0x8b0     [<ffffffffa01f5d24>] r6040_init_one+0x714/0xd2c [r6040] ... The problem occurs in probe process as     follows: r6040_init_one: mdiobus_register mdiobus_scan <- alloc and register phy_device, the reference     count of phy_device is 3 r6040_mii_probe phy_connect <- connect to the first phy_device, so the reference     count of the first phy_device is 4, others are 3 register_netdev <- 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 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. (CVE-2022-50545)

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	Severity
308478	Unity Linux 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-011097)	Nessus	Unity Linux Local Security Checks	medium
308340	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2026-006932)	Nessus	Unity Linux Local Security Checks	medium
280691	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:4320-1)	Nessus	SuSE Local Security Checks	high
279908	SUSE SLES12 Security Update : kernel (SUSE-SU-2025:4515-1)	Nessus	SuSE Local Security Checks	high
275594	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:4111-1)	Nessus	SuSE Local Security Checks	high
270260	Linux Distros Unpatched Vulnerability : CVE-2022-50545	Nessus	Misc.	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	high

Detections

Analytics

CVE-2022-50545

medium

Tenable Plugins

medium

medium

high

high

high

medium

high