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

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

    wifi: brcmfmac: Check the count value of channel spec to prevent out-of-bounds reads

    This patch fixes slab-out-of-bounds reads in brcmfmac that occur in     brcmf_construct_chaninfo() and brcmf_enable_bw40_2g() when the count     value of channel specifications provided by the device is greater than     the length of 'list->element[]', decided by the size of the 'list'     allocated with kzalloc(). The patch adds checks that make the functions     free the buffer and return -EINVAL if that is the case. Note that the     negative return is handled by the caller, brcmf_setup_wiphybands() or     brcmf_cfg80211_attach().

    Found by a modified version of syzkaller.

    Crash Report from brcmf_construct_chaninfo():
    ==================================================================     BUG: KASAN: slab-out-of-bounds in brcmf_setup_wiphybands+0x1238/0x1430     Read of size 4 at addr ffff888115f24600 by task kworker/0:2/1896

    CPU: 0 PID: 1896 Comm: kworker/0:2 Tainted: G        W  O      5.14.0+ #132     Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org     04/01/2014     Workqueue: usb_hub_wq hub_event     Call Trace:
     dump_stack_lvl+0x57/0x7d      print_address_description.constprop.0.cold+0x93/0x334      kasan_report.cold+0x83/0xdf      brcmf_setup_wiphybands+0x1238/0x1430      brcmf_cfg80211_attach+0x2118/0x3fd0      brcmf_attach+0x389/0xd40      brcmf_usb_probe+0x12de/0x1690      usb_probe_interface+0x25f/0x710      really_probe+0x1be/0xa90
     __driver_probe_device+0x2ab/0x460      driver_probe_device+0x49/0x120
     __device_attach_driver+0x18a/0x250      bus_for_each_drv+0x123/0x1a0
     __device_attach+0x207/0x330      bus_probe_device+0x1a2/0x260      device_add+0xa61/0x1ce0      usb_set_configuration+0x984/0x1770      usb_generic_driver_probe+0x69/0x90      usb_probe_device+0x9c/0x220      really_probe+0x1be/0xa90
     __driver_probe_device+0x2ab/0x460      driver_probe_device+0x49/0x120
     __device_attach_driver+0x18a/0x250      bus_for_each_drv+0x123/0x1a0
     __device_attach+0x207/0x330      bus_probe_device+0x1a2/0x260      device_add+0xa61/0x1ce0      usb_new_device.cold+0x463/0xf66      hub_event+0x10d5/0x3330      process_one_work+0x873/0x13e0      worker_thread+0x8b/0xd10      kthread+0x379/0x450      ret_from_fork+0x1f/0x30

    Allocated by task 1896:
     kasan_save_stack+0x1b/0x40
     __kasan_kmalloc+0x7c/0x90      kmem_cache_alloc_trace+0x19e/0x330      brcmf_setup_wiphybands+0x290/0x1430      brcmf_cfg80211_attach+0x2118/0x3fd0      brcmf_attach+0x389/0xd40      brcmf_usb_probe+0x12de/0x1690      usb_probe_interface+0x25f/0x710      really_probe+0x1be/0xa90
     __driver_probe_device+0x2ab/0x460      driver_probe_device+0x49/0x120
     __device_attach_driver+0x18a/0x250      bus_for_each_drv+0x123/0x1a0
     __device_attach+0x207/0x330      bus_probe_device+0x1a2/0x260      device_add+0xa61/0x1ce0      usb_set_configuration+0x984/0x1770      usb_generic_driver_probe+0x69/0x90      usb_probe_device+0x9c/0x220      really_probe+0x1be/0xa90
     __driver_probe_device+0x2ab/0x460      driver_probe_device+0x49/0x120
     __device_attach_driver+0x18a/0x250      bus_for_each_drv+0x123/0x1a0
     __device_attach+0x207/0x330      bus_probe_device+0x1a2/0x260      device_add+0xa61/0x1ce0      usb_new_device.cold+0x463/0xf66      hub_event+0x10d5/0x3330      process_one_work+0x873/0x13e0      worker_thread+0x8b/0xd10      kthread+0x379/0x450      ret_from_fork+0x1f/0x30

    The buggy address belongs to the object at ffff888115f24000      which belongs to the cache kmalloc-2k of size 2048     The buggy address is located 1536 bytes inside of      2048-byte region [ffff888115f24000, ffff888115f24800)

    Memory state around the buggy address:
     ffff888115f24500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00      ffff888115f24580: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     >ffff888115f24600: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc                        ^      ffff888115f24680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc      ffff888115f24700: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc     ==================================================================

    Crash Report from brcmf_enable_bw40_2g():
    ==========
    ---truncated---

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.

  - wifi: brcmfmac: Check the count value of channel spec to prevent out-of-bounds reads This patch fixes     slab-out-of-bounds reads in brcmfmac that occur in brcmf_construct_chaninfo() and brcmf_enable_bw40_2g()     when the count value of channel specifications provided by the device is greater than the length of     'list->element[]', decided by the size of the 'list' allocated with kzalloc(). The patch adds checks that     make the functions free the buffer and return -EINVAL if that is the case. Note that the negative return     is handled by the caller, brcmf_setup_wiphybands() or brcmf_cfg80211_attach(). Found by a modified version     of syzkaller. Crash Report from brcmf_construct_chaninfo():
    ================================================================== BUG: KASAN: slab-out-of-bounds in     brcmf_setup_wiphybands+0x1238/0x1430 Read of size 4 at addr ffff888115f24600 by task kworker/0:2/1896 CPU:
    0 PID: 1896 Comm: kworker/0:2 Tainted: G W O 5.14.0+ #132 Hardware name: QEMU Standard PC (i440FX + PIIX,     1996), BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org 04/01/2014 Workqueue: usb_hub_wq hub_event Call     Trace: dump_stack_lvl+0x57/0x7d print_address_description.constprop.0.cold+0x93/0x334     kasan_report.cold+0x83/0xdf brcmf_setup_wiphybands+0x1238/0x1430 brcmf_cfg80211_attach+0x2118/0x3fd0     brcmf_attach+0x389/0xd40 brcmf_usb_probe+0x12de/0x1690 usb_probe_interface+0x25f/0x710     really_probe+0x1be/0xa90 __driver_probe_device+0x2ab/0x460 driver_probe_device+0x49/0x120
    __device_attach_driver+0x18a/0x250 bus_for_each_drv+0x123/0x1a0 __device_attach+0x207/0x330     bus_probe_device+0x1a2/0x260 device_add+0xa61/0x1ce0 usb_set_configuration+0x984/0x1770     usb_generic_driver_probe+0x69/0x90 usb_probe_device+0x9c/0x220 really_probe+0x1be/0xa90
    __driver_probe_device+0x2ab/0x460 driver_probe_device+0x49/0x120 __device_attach_driver+0x18a/0x250     bus_for_each_drv+0x123/0x1a0 __device_attach+0x207/0x330 bus_probe_device+0x1a2/0x260     device_add+0xa61/0x1ce0 usb_new_device.cold+0x463/0xf66 hub_event+0x10d5/0x3330     process_one_work+0x873/0x13e0 worker_thread+0x8b/0xd10 kthread+0x379/0x450 ret_from_fork+0x1f/0x30     Allocated by task 1896: kasan_save_stack+0x1b/0x40 __kasan_kmalloc+0x7c/0x90     kmem_cache_alloc_trace+0x19e/0x330 brcmf_setup_wiphybands+0x290/0x1430 brcmf_cfg80211_attach+0x2118/0x3fd0     brcmf_attach+0x389/0xd40 brcmf_usb_probe+0x12de/0x1690 usb_probe_interface+0x25f/0x710     really_probe+0x1be/0xa90 __driver_probe_device+0x2ab/0x460 driver_probe_device+0x49/0x120
    __device_attach_driver+0x18a/0x250 bus_for_each_drv+0x123/0x1a0 __device_attach+0x207/0x330     bus_probe_device+0x1a2/0x260 device_add+0xa61/0x1ce0 usb_set_configuration+0x984/0x1770     usb_generic_driver_probe+0x69/0x90 usb_probe_device+0x9c/0x220 really_probe+0x1be/0xa90
    __driver_probe_device+0x2ab/0x460 driver_probe_device+0x49/0x120 __device_attach_driver+0x18a/0x250     bus_for_each_drv+0x123/0x1a0 __device_attach+0x207/0x330 bus_probe_device+0x1a2/0x260     device_add+0xa61/0x1ce0 usb_new_device.cold+0x463/0xf66 hub_event+0x10d5/0x3330     process_one_work+0x873/0x13e0 worker_thread+0x8b/0xd10 kthread+0x379/0x450 ret_from_fork+0x1f/0x30 The     buggy address belongs to the object at ffff888115f24000 which belongs to the cache kmalloc-2k of size 2048     The buggy address is located 1536 bytes inside of 2048-byte region [ffff888115f24000, ffff888115f24800)     Memory state around the buggy address: ffff888115f24500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ffff888115f24580: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >ffff888115f24600: fc fc fc fc fc fc fc     fc fc fc fc fc fc fc fc fc ^ ffff888115f24680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc     ffff888115f24700: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc     ================================================================== Crash Report from     brcmf_enable_bw40_2g(): ========== ---truncated--- (CVE-2022-49740)

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

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

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

    wifi: brcmfmac: Check the count value of channel spec to prevent out-of-bounds reads

    This patch fixes slab-out-of-bounds reads in brcmfmac that occur in     brcmf_construct_chaninfo() and brcmf_enable_bw40_2g() when the count     value of channel specifications provided by the device is greater than     the length of 'list->element[]', decided by the size of the 'list'     allocated with kzalloc(). The patch adds checks that make the functions     free the buffer and return -EINVAL if that is the case. Note that the     negative return is handled by the caller, brcmf_setup_wiphybands() or     brcmf_cfg80211_attach().

    Found by a modified version of syzkaller.

    Crash Report from brcmf_construct_chaninfo():
    ==================================================================     BUG: KASAN: slab-out-of-bounds in brcmf_setup_wiphybands+0x1238/0x1430     Read of size 4 at addr ffff888115f24600 by task kworker/0:2/1896

    CPU: 0 PID: 1896 Comm: kworker/0:2 Tainted: G        W  O      5.14.0+ #132     Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org     04/01/2014     Workqueue: usb_hub_wq hub_event     Call Trace:
     dump_stack_lvl+0x57/0x7d      print_address_description.constprop.0.cold+0x93/0x334      kasan_report.cold+0x83/0xdf      brcmf_setup_wiphybands+0x1238/0x1430      brcmf_cfg80211_attach+0x2118/0x3fd0      brcmf_attach+0x389/0xd40      brcmf_usb_probe+0x12de/0x1690      usb_probe_interface+0x25f/0x710      really_probe+0x1be/0xa90
     __driver_probe_device+0x2ab/0x460      driver_probe_device+0x49/0x120
     __device_attach_driver+0x18a/0x250      bus_for_each_drv+0x123/0x1a0
     __device_attach+0x207/0x330      bus_probe_device+0x1a2/0x260      device_add+0xa61/0x1ce0      usb_set_configuration+0x984/0x1770      usb_generic_driver_probe+0x69/0x90      usb_probe_device+0x9c/0x220      really_probe+0x1be/0xa90
     __driver_probe_device+0x2ab/0x460      driver_probe_device+0x49/0x120
     __device_attach_driver+0x18a/0x250      bus_for_each_drv+0x123/0x1a0
     __device_attach+0x207/0x330      bus_probe_device+0x1a2/0x260      device_add+0xa61/0x1ce0      usb_new_device.cold+0x463/0xf66      hub_event+0x10d5/0x3330      process_one_work+0x873/0x13e0      worker_thread+0x8b/0xd10      kthread+0x379/0x450      ret_from_fork+0x1f/0x30

    Allocated by task 1896:
     kasan_save_stack+0x1b/0x40
     __kasan_kmalloc+0x7c/0x90      kmem_cache_alloc_trace+0x19e/0x330      brcmf_setup_wiphybands+0x290/0x1430      brcmf_cfg80211_attach+0x2118/0x3fd0      brcmf_attach+0x389/0xd40      brcmf_usb_probe+0x12de/0x1690      usb_probe_interface+0x25f/0x710      really_probe+0x1be/0xa90
     __driver_probe_device+0x2ab/0x460      driver_probe_device+0x49/0x120
     __device_attach_driver+0x18a/0x250      bus_for_each_drv+0x123/0x1a0
     __device_attach+0x207/0x330      bus_probe_device+0x1a2/0x260      device_add+0xa61/0x1ce0      usb_set_configuration+0x984/0x1770      usb_generic_driver_probe+0x69/0x90      usb_probe_device+0x9c/0x220      really_probe+0x1be/0xa90
     __driver_probe_device+0x2ab/0x460      driver_probe_device+0x49/0x120
     __device_attach_driver+0x18a/0x250      bus_for_each_drv+0x123/0x1a0
     __device_attach+0x207/0x330      bus_probe_device+0x1a2/0x260      device_add+0xa61/0x1ce0      usb_new_device.cold+0x463/0xf66      hub_event+0x10d5/0x3330      process_one_work+0x873/0x13e0      worker_thread+0x8b/0xd10      kthread+0x379/0x450      ret_from_fork+0x1f/0x30

    The buggy address belongs to the object at ffff888115f24000      which belongs to the cache kmalloc-2k of size 2048     The buggy address is located 1536 bytes inside of      2048-byte region [ffff888115f24000, ffff888115f24800)

    Memory state around the buggy address:
     ffff888115f24500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00      ffff888115f24580: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     >ffff888115f24600: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc                        ^      ffff888115f24680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc      ffff888115f24700: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc     ==================================================================

    Crash Report from brcmf_enable_bw40_2g():
    ==========
    ---truncated---

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.

An update of the linux package has been released.

The AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1786350974 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: isofs: Fix out of bound access for     corrupted isofs image When isofs image is suitably corrupted isofs_read_inode() can read data beyond the     end of buffer. Sanity-check the directory entry length before using it. (CVE-2021-47478)

  - In the Linux kernel, the following vulnerability has been resolved: ubi: Fix race condition between     ctrl_cdev_ioctl and ubi_cdev_ioctl Hulk Robot reported a KASAN report about use-after-free:
    ================================================================== BUG: KASAN: use-after-free in
    __list_del_entry_valid+0x13d/0x160 Read of size 8 at addr ffff888035e37d98 by task ubiattach/1385 [...]     Call Trace: klist_dec_and_del+0xa7/0x4a0 klist_put+0xc7/0x1a0 device_del+0x4d4/0xed0     cdev_device_del+0x1a/0x80 ubi_attach_mtd_dev+0x2951/0x34b0 [ubi] ctrl_cdev_ioctl+0x286/0x2f0 [ubi]     Allocated by task 1414: device_add+0x60a/0x18b0 cdev_device_add+0x103/0x170     ubi_create_volume+0x1118/0x1a10 [ubi] ubi_cdev_ioctl+0xb7f/0x1ba0 [ubi] Freed by task 1385:
    cdev_device_del+0x1a/0x80 ubi_remove_volume+0x438/0x6c0 [ubi] ubi_cdev_ioctl+0xbf4/0x1ba0 [ubi] [...]     ================================================================== The lock held by ctrl_cdev_ioctl is     ubi_devices_mutex, but the lock held by ubi_cdev_ioctl is ubi->device_mutex. Therefore, the two locks can     be concurrent. ctrl_cdev_ioctl contains two operations: ubi_attach and ubi_detach. ubi_detach is bug-free     because it uses reference counting to prevent concurrency. However, uif_init and uif_close in ubi_attach     may race with ubi_cdev_ioctl. uif_init will race with ubi_cdev_ioctl as in the following stack. cpu1 cpu2     cpu3 _______________________|________________________|______________________ ctrl_cdev_ioctl     ubi_attach_mtd_dev uif_init ubi_cdev_ioctl ubi_create_volume cdev_device_add ubi_add_volume // sysfs exist     kill_volumes ubi_cdev_ioctl ubi_remove_volume cdev_device_del // first free ubi_free_volume cdev_del //     double free cdev_device_del And uif_close will race with ubi_cdev_ioctl as in the following stack. cpu1     cpu2 cpu3 _______________________|________________________|______________________ ctrl_cdev_ioctl     ubi_attach_mtd_dev uif_init ubi_cdev_ioctl ubi_create_volume cdev_device_add ubi_debugfs_init_dev //error     goto out_uif; uif_close kill_volumes ubi_cdev_ioctl ubi_remove_volume cdev_device_del // first free     ubi_free_volume // double free The cause of this problem is that commit 714fb87e8bc0 make device     available before it becomes accessible via sysfs. Therefore, we roll back the modification. We will fix     the race condition between ubi device creation and udev by removing ubi_get_device in vol_attribute_show     and dev_attribute_show.This avoids accessing uninitialized ubi_devices[ubi_num]. ubi_get_device is used to     prevent devices from being deleted during sysfs execution. However, now kernfs ensures that devices will     not be deleted before all reference counting are released. The key process is shown in the following     stack. device_del device_remove_attrs device_remove_groups sysfs_remove_groups sysfs_remove_group     remove_files kernfs_remove_by_name kernfs_remove_by_name_ns __kernfs_remove kernfs_drain (CVE-2021-47634)

  - In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix memory leak in
    __qlt_24xx_handle_abts() Commit 8f394da36a36 (scsi: qla2xxx: Drop TARGET_SCF_LOOKUP_LUN_FROM_TAG) made     the __qlt_24xx_handle_abts() function return early if tcm_qla2xxx_find_cmd_by_tag() didn't find a command,     but it missed to clean up the allocated memory for the management command. (CVE-2022-48650)

  - In the Linux kernel, the following vulnerability has been resolved: ubi: ubi_create_volume: Fix use-after-     free when volume creation failed There is an use-after-free problem for 'eba_tbl' in ubi_create_volume()'s     error handling path: ubi_eba_replace_table(vol, eba_tbl) vol->eba_tbl = tbl out_mapping:
    ubi_eba_destroy_table(eba_tbl) // Free 'eba_tbl' out_unlock: put_device(&vol->dev) vol_release     kfree(tbl->entries) // UAF Fix it by removing redundant 'eba_tbl' releasing. Fetch a reproducer in [Link].
    (CVE-2022-49388)

  - In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3: Fix error handling in     gic_populate_ppi_partitions of_get_child_by_name() returns a node pointer with refcount incremented, we     should use of_node_put() on it when not need anymore. When kcalloc fails, it missing of_node_put() and     results in refcount leak. Fix this by goto out_put_node label. (CVE-2022-49716)

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

The CentOS Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS7:CLSA-2026:1783337441 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: IB/qib: Protect from buffer overflow     in struct qib_user_sdma_pkt fields Overflowing either addrlimit or bytes_togo can allow userspace to     trigger a buffer overflow of kernel memory. Check for overflows in all the places doing math on user     controlled buffers. (CVE-2021-47485)

  - In the Linux kernel, the following vulnerability has been resolved: nfsd: fix use-after-free due to     delegation race A delegation break could arrive as soon as we've called vfs_setlease. A delegation break     runs a callback which immediately (in nfsd4_cb_recall_prepare) adds the delegation to del_recall_lru. If     we then exit nfs4_set_delegation without hashing the delegation, it will be freed as soon as the callback     is done with it, without ever being removed from del_recall_lru. Symptoms show up later as use-after-free     or list corruption warnings, usually in the laundromat thread. I suspect aba2072f4523 nfsd: grant read     delegations to clients holding writes made this bug easier to hit, but I looked as far back as v3.0 and     it looks to me it already had the same problem. So I'm not sure where the bug was introduced; it may have     been there from the beginning. (CVE-2021-47506)

  - In the Linux kernel, the following vulnerability has been resolved: proc/vmcore: fix clearing user buffer     by properly using clear_user() To clear a user buffer we cannot simply use memset, we have to use     clear_user(). With a virtio-mem device that registers a vmcore_cb and has some logically unplugged memory     inside an added Linux memory block, I can easily trigger a BUG by copying the vmcore via cp: systemd[1]:
    Starting Kdump Vmcore Save Service... kdump[420]: Kdump is using the default log level(3). kdump[453]:
    saving to /sysroot/var/crash/127.0.0.1-2021-11-11-14:59:22/ kdump[458]: saving vmcore-dmesg.txt to     /sysroot/var/crash/127.0.0.1-2021-11-11-14:59:22/ kdump[465]: saving vmcore-dmesg.txt complete kdump[467]:
    saving vmcore BUG: unable to handle page fault for address: 00007f2374e01000 #PF: supervisor write access     in kernel mode #PF: error_code(0x0003) - permissions violation PGD 7a523067 P4D 7a523067 PUD 7a528067 PMD     7a525067 PTE 800000007048f867 Oops: 0003 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 468 Comm: cp Not tainted     5.15.0+ #6 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS     rel-1.14.0-27-g64f37cc530f1-prebuilt.qemu.org 04/01/2014 RIP: 0010:read_from_oldmem.part.0.cold+0x1d/0x86     Code: ff ff ff e8 05 ff fe ff e9 b9 e9 7f ff 48 89 de 48 c7 c7 38 3b 60 82 e8 f1 fe fe ff 83 fd 08 72 3c     49 8d 7d 08 4c 89 e9 89 e8 <49> c7 45 00 00 00 00 00 49 c7 44 05 f8 00 00 00 00 48 83 e7 f81 RSP:
    0018:ffffc9000073be08 EFLAGS: 00010212 RAX: 0000000000001000 RBX: 00000000002fd000 RCX: 00007f2374e01000     RDX: 0000000000000001 RSI: 00000000ffffdfff RDI: 00007f2374e01008 RBP: 0000000000001000 R08:
    0000000000000000 R09: ffffc9000073bc50 R10: ffffc9000073bc48 R11: ffffffff829461a8 R12: 000000000000f000     R13: 00007f2374e01000 R14: 0000000000000000 R15: ffff88807bd421e8 FS: 00007f2374e12140(0000)     GS:ffff88807f000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2:
    00007f2374e01000 CR3: 000000007a4aa000 CR4: 0000000000350eb0 Call Trace: read_vmcore+0x236/0x2c0     proc_reg_read+0x55/0xa0 vfs_read+0x95/0x190 ksys_read+0x4f/0xc0 do_syscall_64+0x3b/0x90     entry_SYSCALL_64_after_hwframe+0x44/0xae Some x86-64 CPUs have a CPU feature called Supervisor Mode     Access Prevention (SMAP), which is used to detect wrong access from the kernel to user buffers like this:
    SMAP triggers a permissions violation on wrong access. In the x86-64 variant of clear_user(), SMAP is     properly handled via clac()+stac(). To fix, properly use clear_user() when we're dealing with a user     buffer. (CVE-2021-47566)

  - In the Linux kernel, the following vulnerability has been resolved: staging: rtl8192e: Fix use after free     in _rtl92e_pci_disconnect() The free_rtllib() function frees the dev pointer so there is use after free     on the next line. Re-arrange things to avoid that. (CVE-2021-47571)

  - In the Linux kernel, the following vulnerability has been resolved: scsi: scsi_debug: Sanity check block     descriptor length in resp_mode_select() In resp_mode_select() sanity check the block descriptor len to     avoid UAF. BUG: KASAN: use-after-free in resp_mode_select+0xa4c/0xb40 drivers/scsi/scsi_debug.c:2509 Read     of size 1 at addr ffff888026670f50 by task scsicmd/15032 CPU: 1 PID: 15032 Comm: scsicmd Not tainted     5.15.0-01d0625 #15 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Call Trace: <TASK>     dump_stack_lvl+0x89/0xb5 lib/dump_stack.c:107 print_address_description.constprop.9+0x28/0x160     mm/kasan/report.c:257 kasan_report.cold.14+0x7d/0x117 mm/kasan/report.c:443
    __asan_report_load1_noabort+0x14/0x20 mm/kasan/report_generic.c:306 resp_mode_select+0xa4c/0xb40     drivers/scsi/scsi_debug.c:2509 schedule_resp+0x4af/0x1a10 drivers/scsi/scsi_debug.c:5483     scsi_debug_queuecommand+0x8c9/0x1e70 drivers/scsi/scsi_debug.c:7537 scsi_queue_rq+0x16b4/0x2d10     drivers/scsi/scsi_lib.c:1521 blk_mq_dispatch_rq_list+0xb9b/0x2700 block/blk-mq.c:1640
    __blk_mq_sched_dispatch_requests+0x28f/0x590 block/blk-mq-sched.c:325     blk_mq_sched_dispatch_requests+0x105/0x190 block/blk-mq-sched.c:358 __blk_mq_run_hw_queue+0xe5/0x150     block/blk-mq.c:1762 __blk_mq_delay_run_hw_queue+0x4f8/0x5c0 block/blk-mq.c:1839     blk_mq_run_hw_queue+0x18d/0x350 block/blk-mq.c:1891 blk_mq_sched_insert_request+0x3db/0x4e0 block/blk-mq-     sched.c:474 blk_execute_rq_nowait+0x16b/0x1c0 block/blk-exec.c:63 sg_common_write.isra.18+0xeb3/0x2000     drivers/scsi/sg.c:837 sg_new_write.isra.19+0x570/0x8c0 drivers/scsi/sg.c:775 sg_ioctl_common+0x14d6/0x2710     drivers/scsi/sg.c:941 sg_ioctl+0xa2/0x180 drivers/scsi/sg.c:1166 __x64_sys_ioctl+0x19d/0x220 fs/ioctl.c:52     do_syscall_64+0x3a/0x80 arch/x86/entry/common.c:50 entry_SYSCALL_64_after_hwframe+0x44/0xae     arch/x86/entry/entry_64.S:113 (CVE-2021-47576)

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:1293-1 advisory.

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

    The following security bugs were fixed:

    - CVE-2021-46925: Fixed kernel panic caused by race of smc_sock (bsc#1220466).
    - CVE-2021-47645: media: staging: media: zoran: calculate the right buffer number for zoran_reap_stat_com     (bsc#1237767).
    - CVE-2021-47648: gpu: host1x: Fix a memory leak in 'host1x_remove()' (bsc#1237725).
    - CVE-2022-49046: i2c: dev: check return value when calling dev_set_name() (bsc#1237842).
    - CVE-2022-49051: net: usb: aqc111: Fix out-of-bounds accesses in RX fixup (bsc#1237903).
    - CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
    - CVE-2022-49059: nfc: nci: add flush_workqueue to prevent uaf (bsc#1238007).
    - CVE-2022-49074: irqchip/gic-v3: Fix GICR_CTLR.RWP polling (bsc#1237728).
    - CVE-2022-49075: btrfs: fix qgroup reserve overflow the qgroup limit (bsc#1237733).
    - CVE-2022-49084: qede: confirm skb is allocated before using (bsc#1237751).
    - CVE-2022-49107: ceph: fix memory leak in ceph_readdir when note_last_dentry returns error (bsc#1237973).
    - CVE-2022-49109: ceph: fix inode reference leakage in ceph_get_snapdir() (bsc#1237836).
    - CVE-2022-49119: scsi: pm8001: Fix memory leak in pm8001_chip_fw_flash_update_req() (bsc#1237925).
    - CVE-2022-49120: scsi: pm8001: Fix task leak in pm8001_send_abort_all() (bsc#1237969).
    - CVE-2022-49209: bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full (bsc#1238252).
    - CVE-2022-49220: dax: make sure inodes are flushed before destroy cache (bsc#1237936).
    - CVE-2022-49275: can: m_can: m_can_tx_handler(): fix use after free of skb (bsc#1238719).
    - CVE-2022-49286: tpm: use try_get_ops() in tpm-space.c (bsc#1238647).
    - CVE-2022-49292: ALSA: oss: Fix PCM OSS buffer allocation overflow (bsc#1238625).
    - CVE-2022-49308: extcon: Modify extcon device to be created after driver data is set (bsc#1238654).
    - CVE-2022-49331: nfc: st21nfca: fix memory leaks in EVT_TRANSACTION handling (bsc#1237813).
    - CVE-2022-49344: af_unix: Fix a data-race in unix_dgram_peer_wake_me() (bsc#1237988).
    - CVE-2022-49367: net: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register (bsc#1238447).
    - CVE-2022-49370: firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle (bsc#1238467).
    - CVE-2022-49372: tcp: tcp_rtx_synack() can be called from process context (bsc#1238251).
    - CVE-2022-49388: ubi: ubi_create_volume: Fix use-after-free when volume creation failed (bsc#1237934).
    - CVE-2022-49395: um: Fix out-of-bounds read in LDT setup (bsc#1237953).
    - CVE-2022-49397: phy: qcom-qmp: fix struct clk leak on probe errors (bsc#1237823).
    - CVE-2022-49404: RDMA/hfi1: Fix potential integer multiplication overflow errors (bsc#1238430).
    - CVE-2022-49416: wifi: mac80211: fix use-after-free in chanctx code (bsc#1238293).
    - CVE-2022-49433: RDMA/hfi1: Prevent use of lock before it is initialized (bsc#1238268).
    - CVE-2022-49472: net: phy: micrel: Allow probing without .driver_data (bsc#1238951).
    - CVE-2022-49488: drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock (bsc#1238600).
    - CVE-2022-49495: drm/msm/hdmi: check return value after calling platform_get_resource_byname()     (bsc#1237932).
    - CVE-2022-49497: net: remove two BUG() from skb_checksum_help() (bsc#1238946).
    - CVE-2022-49505: NFC: NULL out the dev->rfkill to prevent UAF (bsc#1238615).
    - CVE-2022-49516: ice: always check VF VSI pointer values (bsc#1238953).
    - CVE-2022-49519: ath10k: skip ath10k_halt during suspend for driver state RESTARTING (bsc#1238943).
    - CVE-2022-49524: media: pci: cx23885: Fix the error handling in cx23885_initdev() (bsc#1238949).
    - CVE-2022-49530: drm/amd/pm: fix double free in si_parse_power_table() (bsc#1238944).
    - CVE-2022-49538: ALSA: jack: Fix mutex call in snd_jack_report() (bsc#1238843).
    - CVE-2022-49544: ipw2x00: Fix potential NULL dereference in libipw_xmit() (bsc#1238721).
    - CVE-2022-49545: ALSA: usb-audio: Cancel pending work at closing a MIDI substream (bsc#1238729).
    - CVE-2022-49546: x86/kexec: Fix double-free of elf header buffer (bsc#1238750).
    - CVE-2022-49563: crypto: qat - add param check for RSA (bsc#1238787).
    - CVE-2022-49564: crypto: qat - add param check for DH (bsc#1238789).
    - CVE-2022-49578: ip: Fix data-races around sysctl_ip_prot_sock. (bsc#1238794).
    - CVE-2022-49581: be2net: Fix buffer overflow in be_get_module_eeprom (bsc#1238540).
    - CVE-2022-49589: kABI: protect mr_ifc_count change (bsc#1238598).
    - CVE-2022-49605: igc: Reinstate IGC_REMOVED logic and implement it properly (bsc#1238433).
    - CVE-2022-49607: perf/core: Fix data race between perf_event_set_output() and perf_mmap_close()     (bsc#1238817).
    - CVE-2022-49610: KVM: VMX: Prevent RSB underflow before vmenter (bsc#1238952).
    - CVE-2022-49619: net: sfp: fix memory leak in sfp_probe() (bsc#1239003).
    - CVE-2022-49620: net: tipc: fix possible refcount leak in tipc_sk_create() (bsc#1239002).
    - CVE-2022-49640: sysctl: Fix data races in proc_douintvec_minmax() (bsc#1237782).
    - CVE-2022-49641: sysctl: Fix data races in proc_douintvec() (bsc#1237831).
    - CVE-2022-49667: net: bonding: fix use-after-free after 802.3ad slave unbind (bsc#1238282).
    - CVE-2022-49672: net: tun: unlink NAPI from device on destruction (bsc#1238816).
    - CVE-2022-49711: bus: fsl-mc-bus: fix KASAN use-after-free in fsl_mc_bus_remove() (bsc#1238416).
    - CVE-2022-49727: ipv6: Fix signed integer overflow in l2tp_ip6_sendmsg (bsc#1239059).
    - CVE-2022-49740: wifi: brcmfmac: Check the count value of channel spec to prevent out-of-bounds reads     (bsc#1240233).
    - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
    - CVE-2023-52997: ipv4: prevent potential spectre v1 gadget in ip_metrics_convert() (bsc#1240303).
    - CVE-2023-53010: bnxt: Do not read past the end of test names (bsc#1240290).
    - CVE-2023-53019: net: mdio: validate parameter addr in mdiobus_get_phy() (bsc#1240286).
    - CVE-2024-35910: kABI fix for tcp: properly terminate timers for kernel sockets (bsc#1224489).
    - CVE-2024-36968: Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init() (bsc#1226130).
    - CVE-2024-38559: scsi: qedf: Ensure the copied buf is NUL terminated (bsc#1226785).
    - CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
    - CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg     (bsc#1235733).
    - CVE-2024-49935: ACPI: PAD: fix crash in exit_round_robin() (bsc#1232370).
    - CVE-2024-49940: l2tp: prevent possible tunnel refcount underflow (bsc#1232812).
    - CVE-2024-50269: usb: musb: sunxi: Fix accessing an released usb phy (bsc#1233458).
    - CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
    - CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
    - CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
    - CVE-2024-56640: net/smc: fix LGR and link use-after-free issue (bsc#1235436).
    - CVE-2024-56770: net/sched: netem: account for backlog updates from child qdisc (bsc#1235637).
    - CVE-2024-57900: ila: serialize calls to nf_register_net_hooks() (bsc#1235973).
    - CVE-2024-57973: rdma/cxgb4: Prevent potential integer overflow on 32bit (bsc#1238531).
    - CVE-2024-57979: kABI workaround for pps changes (bsc#1238521).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2024-58052: drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table     (bsc#1238986).
    - CVE-2024-58071: team: prevent adding a device which is already a team device lower (bsc#1238970)
    - CVE-2024-58072: wifi: rtlwifi: remove unused check_buddy_priv (bsc#1238964).
    - CVE-2024-58083: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (bsc#1239036).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-21708: net: usb: rtl8150: enable basic endpoint checking (bsc#1239087).
    - CVE-2025-21744: wifi: brcmfmac: fix NULL pointer dereference in brcmf_txfinalize() (bsc#1238903).
    - CVE-2025-21759: ipv6: mcast: extend RCU protection in igmp6_send() (bsc#1238738).
    - CVE-2025-21760: ndisc: extend RCU protection in ndisc_send_skb() (bsc#1238763).
    - CVE-2025-21762: arp: use RCU protection in arp_xmit() (bsc#1238780).
    - CVE-2025-21763: neighbour: use RCU protection in __neigh_notify() (bsc#1237897).
    - CVE-2025-21765: ipv6: use RCU protection in ip6_default_advmss() (bsc#1237906).
    - CVE-2025-21766: ipv4: use RCU protection in __ip_rt_update_pmtu() (bsc#1238754).
    - CVE-2025-21776: USB: hub: Ignore non-compliant devices with too many configs or interfaces     (bsc#1238909).
    - CVE-2025-21782: orangefs: fix a oob in orangefs_debug_write (bsc#1239117).
    - CVE-2025-21785: arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array (bsc#1238747).
    - CVE-2025-21791: vrf: use RCU protection in l3mdev_l3_out() (bsc#1238512).
    - CVE-2025-21796: nfsd: clear acl_access/acl_default after releasing them (bsc#1238716).
    - CVE-2025-21802: net: hns3: fix oops when unload drivers paralleling (bsc#1238751).
    - CVE-2025-21821: fbdev: omap: use threaded IRQ for LCD DMA (bsc#1239174).
    - CVE-2025-21831: PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 (bsc#1239039).
    - CVE-2025-21846: acct: perform last write from workqueue (bsc#1239508).
    - CVE-2025-21848: nfp: bpf: Add check for nfp_app_ctrl_msg_alloc() (bsc#1239479).
    - CVE-2025-21865: gtp: Suppress list corruption splat in gtp_net_exit_batch_rtnl() (bsc#1239481).
    - CVE-2025-21871: tee: optee: Fix supplicant wait loop (bsc#1240183).
    - CVE-2025-21877: usbnet: gl620a: fix endpoint checking in genelink_bind() (bsc#1240172).
    - CVE-2025-21891: ipvlan: ensure network headers are in skb linear part (bsc#1240186).
    - CVE-2025-21916: usb: atm: cxacru: fix a flaw in existing endpoint checks (bsc#1240582).
    - CVE-2025-21922: ppp: Fix KMSAN uninit-value warning with bpf (bsc#1240639).
    - CVE-2025-21934: rapidio: fix an API misues when rio_add_net() fails (bsc#1240708).
    - CVE-2025-21935: rapidio: add check for rio_add_net() in rio_scan_alloc_net() (bsc#1240700).
    - CVE-2025-21969: Bluetooth: L2CAP: Fix build errors in some archs (bsc#1240784).
    - CVE-2025-21993: iscsi_ibft: Fix UBSAN shift-out-of-bounds warning in ibft_attr_show_nic() (bsc#1240797).
    - CVE-2025-21996: drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse() (bsc#1240801).
    - CVE-2025-22007: Bluetooth: Fix error code in chan_alloc_skb_cb() (bsc#1240582).


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.

ID	Name	Product	Family	Published	Updated	Severity
271082	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-987686)	Nessus	Unity Linux Local Security Checks	10/21/2025	10/21/2025	high
245547	Linux Distros Unpatched Vulnerability : CVE-2022-49740	Nessus	Misc.	8/7/2025	9/30/2026	high
272902	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989681)	Nessus	Unity Linux Local Security Checks	11/5/2025	11/5/2025	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	7/22/2021	10/9/2026	high
360716	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1786350974)	Nessus	Alma Linux Local Security Checks	10/1/2026	10/1/2026	high
352867	CentOS Linux 7 [TuxCare] Security Update: bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / etc Multiple Vulnerabilities (CENTOS7:CLSA-2026:1783337441)	Nessus	CentOS Local Security Checks	9/30/2026	9/30/2026	high
234545	SUSE SLES12: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:1293-1)	Nessus	SuSE Local Security Checks	4/17/2025	6/25/2026	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high