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

  - sctp: fix memory leak in sctp_stream_outq_migrate() When sctp_stream_outq_migrate() is called to release     stream out resources, the memory pointed to by prio_head in stream out is not released. The memory leak     information is as follows: unreferenced object 0xffff88801fe79f80 (size 64): comm sctp_repo, pid 7957,     jiffies 4294951704 (age 36.480s) hex dump (first 32 bytes): 80 9f e7 1f 80 88 ff ff 80 9f e7 1f 80 88 ff     ff ................ 90 9f e7 1f 80 88 ff ff 90 9f e7 1f 80 88 ff ff ................ backtrace:
    [<ffffffff81b215c6>] kmalloc_trace+0x26/0x60 [<ffffffff88ae517c>] sctp_sched_prio_set+0x4cc/0x770     [<ffffffff88ad64f2>] sctp_stream_init_ext+0xd2/0x1b0 [<ffffffff88aa2604>]     sctp_sendmsg_to_asoc+0x1614/0x1a30 [<ffffffff88ab7ff1>] sctp_sendmsg+0xda1/0x1ef0 [<ffffffff87f765ed>]     inet_sendmsg+0x9d/0xe0 [<ffffffff8754b5b3>] sock_sendmsg+0xd3/0x120 [<ffffffff8755446a>]
    __sys_sendto+0x23a/0x340 [<ffffffff87554651>] __x64_sys_sendto+0xe1/0x1b0 [<ffffffff89978b49>]     do_syscall_64+0x39/0xb0 [<ffffffff89a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd (CVE-2022-49013)

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

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

    sctp: fix memory leak in sctp_stream_outq_migrate()

    When sctp_stream_outq_migrate() is called to release stream out resources,     the memory pointed to by prio_head in stream out is not released.

    The memory leak information is as follows:
     unreferenced object 0xffff88801fe79f80 (size 64):
       comm sctp_repo, pid 7957, jiffies 4294951704 (age 36.480s)        hex dump (first 32 bytes):
         80 9f e7 1f 80 88 ff ff 80 9f e7 1f 80 88 ff ff  ................
         90 9f e7 1f 80 88 ff ff 90 9f e7 1f 80 88 ff ff  ................
       backtrace:
         [<ffffffff81b215c6>] kmalloc_trace+0x26/0x60          [<ffffffff88ae517c>] sctp_sched_prio_set+0x4cc/0x770          [<ffffffff88ad64f2>] sctp_stream_init_ext+0xd2/0x1b0          [<ffffffff88aa2604>] sctp_sendmsg_to_asoc+0x1614/0x1a30          [<ffffffff88ab7ff1>] sctp_sendmsg+0xda1/0x1ef0          [<ffffffff87f765ed>] inet_sendmsg+0x9d/0xe0          [<ffffffff8754b5b3>] sock_sendmsg+0xd3/0x120          [<ffffffff8755446a>] __sys_sendto+0x23a/0x340          [<ffffffff87554651>] __x64_sys_sendto+0xe1/0x1b0          [<ffffffff89978b49>] do_syscall_64+0x39/0xb0          [<ffffffff89a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

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 version of kernel installed on the remote host is prior to 5.10.162-141.675. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2023-025 advisory.

    A vulnerability classified as problematic has been found in Linux Kernel. This affects the function     fib_nh_match of the file net/ipv4/fib_semantics.c of the component IPv4 Handler. The manipulation leads to     out-of-bounds read. It is possible to initiate the attack remotely. It is recommended to apply a patch to     fix this issue. The identifier VDB-210357 was assigned to this vulnerability. (CVE-2022-3435)

    A vulnerability was found in Linux Kernel. It has been declared as problematic. Affected by this     vulnerability is the function follow_page_pte of the file mm/gup.c of the component BPF. The manipulation     leads to race condition. The attack can be launched remotely. It is recommended to apply a patch to fix     this issue. The identifier VDB-211921 was assigned to this vulnerability. (CVE-2022-3623)

    Guests can trigger NIC interface reset/abort/crash via netback It is possible for a guest to trigger a NIC     interface reset/abort/crash in a Linux based network backend by sending certain kinds of packets. It     appears to be an (unwritten?) assumption in the rest of the Linux network stack that packet protocol     headers are all contained within the linear section of the SKB and some NICs behave badly if this is not     the case. This has been reported to occur with Cisco (enic) and Broadcom NetXtrem II BCM5780 (bnx2x)     though it may be an issue with other NICs/drivers as well. In case the frontend is sending requests with     split headers, netback will forward those violating above mentioned assumption to the networking core,     resulting in said misbehavior. (CVE-2022-3643)

    Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs;
    the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced     another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the     XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock     could occur in case of netpoll being active for the interface the xen-netback driver is connected to     (CVE-2022-42329). (CVE-2022-42328)

    Guests can trigger deadlock in Linux netback driver T[his CNA information record relates to multiple CVEs;
    the text explains which aspects/vulnerabilities correspond to which CVE.] The patch for XSA-392 introduced     another issue which might result in a deadlock when trying to free the SKB of a packet dropped due to the     XSA-392 handling (CVE-2022-42328). Additionally when dropping packages for other reasons the same deadlock     could occur in case of netpoll being active for the interface the xen-netback driver is connected to     (CVE-2022-42329). (CVE-2022-42329)

    A stack overflow flaw was found in the Linux kernel's SYSCTL subsystem in how a user changes certain     kernel parameters and variables. This flaw allows a local user to crash or potentially escalate their     privileges on the system. (CVE-2022-4378)

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

    udf: Fix preallocation discarding at indirect extent boundary (CVE-2022-48946)

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

    igb: Initialize mailbox message for VF reset (CVE-2022-48949)

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

    ipv6: avoid use-after-free in ip6_fragment() (CVE-2022-48956)

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

    xen-netfront: Fix NULL sring after live migration (CVE-2022-48969)

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

    af_unix: Get user_ns from in_skb in unix_diag_get_exact(). (CVE-2022-48970)

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

    mac802154: fix missing INIT_LIST_HEAD in ieee802154_if_add() (CVE-2022-48972)

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

    can: af_can: fix NULL pointer dereference in can_rcv_filter (CVE-2022-48977)

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

    HID: core: fix shift-out-of-bounds in hid_report_raw_event (CVE-2022-48978)

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

    drm/shmem-helper: Remove errant put in error path (CVE-2022-48981)

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

    mm/gup: fix gup_pud_range() for dax (CVE-2022-48986)

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

    media: v4l2-dv-timings.c: fix too strict blanking sanity checks (CVE-2022-48987)

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

    memcg: fix possible use-after-free in memcg_write_event_control() (CVE-2022-48988)

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

    mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths (CVE-2022-48991)

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

    char: tpm: Protect tpm_pm_suspend with locks (CVE-2022-48997)

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

    ipv4: Handle attempt to delete multipath route when fib_info contains an nh reference (CVE-2022-48999)

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

    iommu/vt-d: Fix PCI device refcount leak in has_external_pci() (CVE-2022-49000)

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

    iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init() (CVE-2022-49002)

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

    tracing: Free buffers when a used dynamic event is removed (CVE-2022-49006)

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

    nilfs2: fix NULL pointer dereference in nilfs_palloc_commit_free_entry() (CVE-2022-49007)

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

    sctp: fix memory leak in sctp_stream_outq_migrate() (CVE-2022-49013)

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

    net: tun: Fix use-after-free in tun_detach() (CVE-2022-49014)

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

    net: hsr: Fix potential use-after-free (CVE-2022-49015)

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

    tipc: re-fetch skb cb after tipc_msg_validate (CVE-2022-49017)

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

    net: phy: fix null-ptr-deref while probe() failed (CVE-2022-49021)

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

    net/mlx5e: Fix use-after-free when reverting termination table (CVE-2022-49025)

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

    iavf: Fix error handling in iavf_init_module() (CVE-2022-49027)

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

    ixgbevf: Fix resource leak in ixgbevf_init_module() (CVE-2022-49028)

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

    libbpf: Handle size overflow for ringbuf mmap (CVE-2022-49030)

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

    btrfs: qgroup: fix sleep from invalid context bug in btrfs_qgroup_inherit() (CVE-2022-49033)

    A time-of-check to time-of-use issue exists in io_uring subsystem's IORING_OP_CLOSE operation in the Linux     kernel's versions 5.6 - 5.11 (inclusive), which allows a local user to elevate their privileges to root.
    Introduced in b5dba59e0cf7e2cc4d3b3b1ac5fe81ddf21959eb, patched in     9eac1904d3364254d622bf2c771c4f85cd435fc2, backported to stable in     788d0824269bef539fe31a785b1517882eafed93. (CVE-2023-1295)

    A null pointer dereference issue was found in the can protocol in net/can/af_can.c in the Linux Kernel.
    ml_priv may not be initialized in the receive path of CAN frames. This issue could allow a local user to     crash the system or cause a denial of service. (CVE-2023-2166)

Tenable has extracted the preceding description block directly from the tested product 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 version of kernel installed on the remote host is prior to 5.4.226-129.415. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2024-071 advisory.

    A flaw was found in the Linux kernel. A denial of service flaw may occur if there is a consecutive request     of the NVME_IOCTL_RESET and the NVME_IOCTL_SUBSYS_RESET through the device file of the driver, resulting     in a PCIe link disconnect. (CVE-2022-3169)

    A vulnerability classified as problematic has been found in Linux Kernel. This affects the function     fib_nh_match of the file net/ipv4/fib_semantics.c of the component IPv4 Handler. The manipulation leads to     out-of-bounds read. It is possible to initiate the attack remotely. It is recommended to apply a patch to     fix this issue. The identifier VDB-210357 was assigned to this vulnerability. (CVE-2022-3435)

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

    char: tpm: Protect tpm_pm_suspend with locks (CVE-2022-48997)

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

    ipv4: Handle attempt to delete multipath route when fib_info contains an nh reference (CVE-2022-48999)

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

    iommu/vt-d: Fix PCI device refcount leak in dmar_dev_scope_init() (CVE-2022-49002)

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

    tracing: Free buffers when a used dynamic event is removed (CVE-2022-49006)

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

    nilfs2: fix NULL pointer dereference in nilfs_palloc_commit_free_entry() (CVE-2022-49007)

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

    sctp: fix memory leak in sctp_stream_outq_migrate() (CVE-2022-49013)

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

    net: tun: Fix use-after-free in tun_detach() (CVE-2022-49014)

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

    net: hsr: Fix potential use-after-free (CVE-2022-49015)

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

    net: phy: fix null-ptr-deref while probe() failed (CVE-2022-49021)

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

    net/mlx5e: Fix use-after-free when reverting termination table (CVE-2022-49025)

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

    btrfs: qgroup: fix sleep from invalid context bug in btrfs_qgroup_inherit() (CVE-2022-49033)

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

    ntfs: check overflow when iterating ATTR_RECORDs (CVE-2022-49762)

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

    ntfs: fix use-after-free in ntfs_attr_find() (CVE-2022-49763)

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

    gfs2: Check sb_bsize_shift after reading superblock (CVE-2022-49769)

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

    ceph: avoid putting the realm twice when decoding snaps fails (CVE-2022-49770)

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

    dm ioctl: fix misbehavior if list_versions races with module loading (CVE-2022-49771)

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

    macvlan: enforce a consistent minimal mtu (CVE-2022-49776)

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

    Input: i8042 - fix leaking of platform device on module removal (CVE-2022-49777)

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

    kprobes: Skip clearing aggrprobe's post_handler in kprobe-on-ftrace case (CVE-2022-49779)

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

    scsi: target: tcm_loop: Fix possible name leak in tcm_loop_setup_hba_bus() (CVE-2022-49780)

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

    mmc: sdhci-pci: Fix possible memory leak caused by missing pci_dev_put() (CVE-2022-49787)

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

    misc/vmw_vmci: fix an infoleak in vmci_host_do_receive_datagram() (CVE-2022-49788)

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

    ftrace: Fix null pointer dereference in ftrace_add_mod() (CVE-2022-49802)

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

    drbd: use after free in drbd_create_device() (CVE-2022-49811)

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

    kcm: close race conditions on sk_receive_queue (CVE-2022-49814)

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

    ata: libata-transport: fix double ata_host_put() in ata_tport_add() (CVE-2022-49826)

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

    pinctrl: devicetree: fix null pointer dereferencing in pinctrl_dt_to_map (CVE-2022-49832)

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

    nilfs2: fix use-after-free bug of ns_writer on remount (CVE-2022-49834)

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

    bpf, test_run: Fix alignment problem in bpf_prog_test_run_skb() (CVE-2022-49840)

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

    ASoC: core: Fix use-after-free in snd_soc_exit() (CVE-2022-49842)

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

    can: j1939: j1939_send_one(): fix missing CAN header initialization (CVE-2022-49845)

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

    udf: Fix a slab-out-of-bounds write bug in udf_find_entry() (CVE-2022-49846)

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

    nilfs2: fix deadlock in nilfs_count_free_blocks() (CVE-2022-49850)

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

    net: macvlan: fix memory leaks of macvlan_common_newlink (CVE-2022-49853)

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

    tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header (CVE-2022-49862)

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

    can: af_can: fix NULL pointer dereference in can_rx_register() (CVE-2022-49863)

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

    ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network (CVE-2022-49865)

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

    bnxt_en: Fix possible crash in bnxt_hwrm_set_coal() (CVE-2022-49869)

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

    capabilities: fix undefined behavior in bit shift for CAP_TO_MASK (CVE-2022-49870)

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

    net: tun: Fix memory leaks of napi_get_frags (CVE-2022-49871)

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

    net: gso: fix panic on frag_list with mixed head alloc types (CVE-2022-49872)

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

    HID: hyperv: fix possible memory leak in mousevsc_probe() (CVE-2022-49874)

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

    bpf, sockmap: Fix the sk->sk_forward_alloc warning of sk_stream_kill_queues (CVE-2022-49877)

    In the Linux kernel 6.0.8, there is an out-of-bounds read in ntfs_attr_find in fs/ntfs/attrib.c.
    (CVE-2023-26607)

Tenable has extracted the preceding description block directly from the tested product 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 version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2025:0437 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2024-46732:
    In the Linux kernel, the following vulnerability has been resolved:

    drm/amd/display: Assign linear_pitch_alignment even for VM

    [Description]     Assign linear_pitch_alignment so we don't cause a divide by 0     error in VM environments

    CVE-2024-46730:
    In the Linux kernel, the following vulnerability has been resolved:

    drm/amd/display: Ensure array index tg_inst won't be -1

    [WHY & HOW]     tg_inst will be a negative if timing_generator_count equals 0, which     should be checked before used.

    This fixes 2 OVERRUN issues reported by Coverity.

    CVE-2024-24861:
    A race condition was found in the Linux kernel's media/xc4000 device driver in xc4000     xc4000_get_frequency() function. This can result in return value overflow issue, possibly leading to     malfunction or denial of service issue.






    CVE-2024-38559:
    In the Linux kernel, the following vulnerability has been resolved:

    scsi: qedf: Ensure the copied buf is NUL terminated

    Currently, we allocate a count-sized kernel buffer and copy count from     userspace to that buffer. Later, we use kstrtouint on this buffer but we     don't ensure that the string is terminated inside the buffer, this can     lead to OOB read when using kstrtouint. Fix this issue by using     memdup_user_nul instead of memdup_user.

    CVE-2024-26937:
    In the Linux kernel, the following vulnerability has been resolved:

    drm/i915/gt: Reset queue_priority_hint on parking

    Originally, with strict in order execution, we could complete execution     only when the queue was empty. Preempt-to-busy allows replacement of an     active request that may complete before the preemption is processed by     HW. If that happens, the request is retired from the queue, but the     queue_priority_hint remains set, preventing direct submission until     after the next CS interrupt is processed.

    This preempt-to-busy race can be triggered by the heartbeat, which will     also act as the power-management barrier and upon completion allow us to     idle the HW. We may process the completion of the heartbeat, and begin     parking the engine before the CS event that restores the     queue_priority_hint, causing us to fail the assertion that it is MIN.

    <3>[  166.210729] __engine_park:283 GEM_BUG_ON(engine->sched_engine->queue_priority_hint != (-((int)(~0U     >> 1)) - 1))     <0>[  166.210781] Dumping ftrace buffer:
    <0>[  166.210795] ---------------------------------     ...
    <0>[  167.302811] drm_fdin-1097      2..s1. 165741070us : trace_ports: 0000:00:02.0 rcs0: promote {     ccid:20 1217:2 prio 0 }     <0>[  167.302861] drm_fdin-1097      2d.s2. 165741072us : execlists_submission_tasklet: 0000:00:02.0 rcs0:
    preempting last=1217:2, prio=0, hint=2147483646     <0>[  167.302928] drm_fdin-1097      2d.s2. 165741072us : __i915_request_unsubmit: 0000:00:02.0 rcs0:
    fence 1217:2, current 0     <0>[  167.302992] drm_fdin-1097      2d.s2. 165741073us : __i915_request_submit: 0000:00:02.0 rcs0: fence     3:4660, current 4659     <0>[  167.303044] drm_fdin-1097      2d.s1. 165741076us : execlists_submission_tasklet: 0000:00:02.0 rcs0:
    context:3 schedule-in, ccid:40     <0>[  167.303095] drm_fdin-1097      2d.s1. 165741077us : trace_ports: 0000:00:02.0 rcs0: submit { ccid:40     3:4660* prio 2147483646 }     <0>[  167.303159] kworker/-89       11..... 165741139us : i915_request_retire.part.0: 0000:00:02.0 rcs0:
    fence c90:2, current 2     <0>[  167.303208] kworker/-89       11..... 165741148us : __intel_context_do_unpin: 0000:00:02.0 rcs0:
    context:c90 unpin     <0>[  167.303272] kworker/-89       11..... 165741159us : i915_request_retire.part.0: 0000:00:02.0 rcs0:
    fence 1217:2, current 2     <0>[  167.303321] kworker/-89       11..... 165741166us : __intel_context_do_unpin: 0000:00:02.0 rcs0:
    context:1217 unpin     <0>[  167.303384] kworker/-89       11..... 165741170us : i915_request_retire.part.0: 0000:00:02.0 rcs0:
    fence 3:4660, current 4660     <0>[  167.303434] kworker/-89       11d..1. 165741172us : __intel_context_retire: 0000:00:02.0 rcs0:
    context:1216 retire runtime: { total:56028ns, avg:56028ns }     <0>[  167.303484] kworker/-89       11..... 165741198us : __engine_park: 0000:00:02.0 rcs0: parked     <0>[  167.303534]   <idle>-0         5d.H3. 165741207us : execlists_irq_handler: 0000:00:02.0 rcs0:
    semaphore yield: 00000040     <0>[  167.303583] kworker/-89       11..... 165741397us : __intel_context_retire: 0000:00:02.0 rcs0:
    context:1217 retire runtime: { total:325575ns, avg:0ns }     <0>[  167.303756] kworker/-89       11..... 165741777us : __intel_context_retire: 0000:00:02.0 rcs0:
    context:c90 retire runtime: { total:0ns, avg:0ns }     <0>[  167.303806] kworker/-89       11..... 165742017us : __engine_park: __engine_park:283     GEM_BUG_ON(engine->sched_engine->queue_priority_hint != (-((int)(~0U >> 1)) - 1))     <0>[  167.303811] ---------------------------------     <4>[  167.304722] ------------[ cut here ]------------     <2>[  167.304725] kernel BUG at drivers/gpu/drm/i915/gt/intel_engine_pm.c:283!     <4>[  167.304731] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI     <4>[  167.304734] CPU: 11 PID: 89 Comm: kworker/11:1 Tainted: G        W     6.8.0-rc2-CI_DRM_14193-gc655e0fd2804+ #1     <4>[  167.304736] Hardware name: Intel Corporation Rocket Lake Client Platform/RocketLake S UDIMM 6L RVP,     BIOS RKLSFWI1.R00.3173.A03.2204210138 04/21/2022     <4>[  167.304738] Workqueue: i915-unordered retire_work_handler [i915]     <4>[  16
    ---truncated---

    CVE-2024-26935:
    In the Linux kernel, the following vulnerability has been resolved:

    scsi: core: Fix unremoved procfs host directory regression

    Commit fc663711b944 (scsi: core: Remove the /proc/scsi/${proc_name}     directory earlier) fixed a bug related to modules loading/unloading, by     adding a call to scsi_proc_hostdir_rm() on scsi_remove_host(). But that led     to a potential duplicate call to the hostdir_rm() routine, since it's also     called from scsi_host_dev_release(). That triggered a regression report,     which was then fixed by commit be03df3d4bfe (scsi: core: Fix a procfs host     directory removal regression). The fix just dropped the hostdir_rm() call     from dev_release().

    But it happens that this proc directory is created on scsi_host_alloc(),     and that function pairs with scsi_host_dev_release(), while     scsi_remove_host() pairs with scsi_add_host(). In other words, it seems the     reason for removing the proc directory on dev_release() was meant to cover     cases in which a SCSI host structure was allocated, but the call to     scsi_add_host() didn't happen. And that pattern happens to exist in some     error paths, for example.

    Syzkaller causes that by using USB raw gadget device, error'ing on     usb-storage driver, at usb_stor_probe2(). By checking that path, we can see     that the BadDevice label leads to a scsi_host_put() after a SCSI host     allocation, but there's no call to scsi_add_host() in such path. That leads     to messages like this in dmesg (and a leak of the SCSI host proc     structure):

    usb-storage 4-1:87.51: USB Mass Storage device detected     proc_dir_entry 'scsi/usb-storage' already registered     WARNING: CPU: 1 PID: 3519 at fs/proc/generic.c:377 proc_register+0x347/0x4e0 fs/proc/generic.c:376

    The proper fix seems to still call scsi_proc_hostdir_rm() on dev_release(),     but guard that with the state check for SHOST_CREATED; there is even a     comment in scsi_host_dev_release() detailing that: such conditional is     meant for cases where the SCSI host was allocated but there was no calls to     {add,remove}_host(), like the usb-storage case.

    This is what we propose here and with that, the error path of usb-storage     does not trigger the warning anymore.

    CVE-2024-26934:
    In the Linux kernel, the following vulnerability has been resolved:

    USB: core: Fix deadlock in usb_deauthorize_interface()

    Among the attribute file callback routines in     drivers/usb/core/sysfs.c, the interface_authorized_store() function is     the only one which acquires a device lock on an ancestor device: It     calls usb_deauthorize_interface(), which locks the interface's parent     USB device.

    The will lead to deadlock if another process already owns that lock     and tries to remove the interface, whether through a configuration     change or because the device has been disconnected.  As part of the     removal procedure, device_del() waits for all ongoing sysfs attribute     callbacks to complete.  But usb_deauthorize_interface() can't complete     until the device lock has been released, and the lock won't be     released until the removal has finished.

    The mechanism provided by sysfs to prevent this kind of deadlock is     to use the sysfs_break_active_protection() function, which tells sysfs     not to wait for the attribute callback.

    Reported-and-tested by: Yue Sun <samsun1006219@gmail.com>     Reported by: xingwei lee <xrivendell7@gmail.com>

    CVE-2024-26931:
    In the Linux kernel, the following vulnerability has been resolved:

    scsi: qla2xxx: Fix command flush on cable pull

    System crash due to command failed to flush back to SCSI layer.

     BUG: unable to handle kernel NULL pointer dereference at 0000000000000000      PGD 0 P4D 0      Oops: 0000 [#1] SMP NOPTI      CPU: 27 PID: 793455 Comm: kworker/u130:6 Kdump: loaded Tainted: G           OE    --------- -  -     4.18.0-372.9.1.el8.x86_64 #1      Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 09/03/2021      Workqueue: nvme-wq nvme_fc_connect_ctrl_work [nvme_fc]      RIP: 0010:__wake_up_common+0x4c/0x190      Code: 24 10 4d 85 c9 74 0a 41 f6 01 04 0f 85 9d 00 00 00 48 8b 43 08 48 83 c3 08 4c 8d 48 e8 49 8d 41 18     48 39 c3 0f 84 f0 00 00 00 <49> 8b 41 18 89 54 24 08 31 ed 4c 8d 70 e8 45 8b 29 41 f6 c5 04 75      RSP: 0018:ffff95f3e0cb7cd0 EFLAGS: 00010086      RAX: 0000000000000000 RBX: ffff8b08d3b26328 RCX: 0000000000000000      RDX: 0000000000000001 RSI: 0000000000000003 RDI: ffff8b08d3b26320      RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffffffffffe8      R10: 0000000000000000 R11: ffff95f3e0cb7a60 R12: ffff95f3e0cb7d20      R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000      FS:  0000000000000000(0000) GS:ffff8b2fdf6c0000(0000) knlGS:0000000000000000      CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033      CR2: 0000000000000000 CR3: 0000002f1e410002 CR4: 00000000007706e0      DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000      DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400      PKRU: 55555554      Call Trace:
    __wake_up_common_lock+0x7c/0xc0     qla_nvme_ls_req+0x355/0x4c0 [qla2xxx]      qla2xxx [0000:12:00.1]-f084:3: qlt_free_session_done: se_sess 0000000000000000 / sess ffff8ae1407ca000     from port 21:32:00:02:ac:07:ee:b8 loop_id 0x02 s_id 01:02:00 logout 1 keep 0 els_logo 0      ? __nvme_fc_send_ls_req+0x260/0x380 [nvme_fc]      qla2xxx [0000:12:00.1]-207d:3: FCPort 21:32:00:02:ac:07:ee:b8 state transitioned from ONLINE to LOST -     portid=010200.
    ? nvme_fc_send_ls_req.constprop.42+0x1a/0x45 [nvme_fc]      qla2xxx [0000:12:00.1]-2109:3: qla2x00_schedule_rport_del 21320002ac07eeb8. rport ffff8ae598122000 roles     1      ? nvme_fc_connect_ctrl_work.cold.63+0x1e3/0xa7d [nvme_fc]      qla2xxx [0000:12:00.1]-f084:3: qlt_free_session_done: se_sess 0000000000000000 / sess ffff8ae14801e000     from port 21:32:01:02:ad:f7:ee:b8 loop_id 0x04 s_id 01:02:01 logout 1 keep 0 els_logo 0     ? __switch_to+0x10c/0x450      ? process_one_work+0x1a7/0x360      qla2xxx [0000:12:00.1]-207d:3: FCPort 21:32:01:02:ad:f7:ee:b8 state transitioned from ONLINE to LOST -     portid=010201.
    ? worker_thread+0x1ce/0x390     ? create_worker+0x1a0/0x1a0      qla2xxx [0000:12:00.1]-2109:3: qla2x00_schedule_rport_del 21320102adf7eeb8. rport ffff8ae3b2312800 roles     70     ? kthread+0x10a/0x120      qla2xxx [0000:12:00.1]-2112:3: qla_nvme_unregister_remote_port: unregister remoteport on ffff8ae14801e000     21320102adf7eeb8     ? set_kthread_struct+0x40/0x40      qla2xxx [0000:12:00.1]-2110:3: remoteport_delete of ffff8ae14801e000 21320102adf7eeb8 completed.
    ? ret_from_fork+0x1f/0x40      qla2xxx [0000:12:00.1]-f086:3: qlt_free_session_done: waiting for sess ffff8ae14801e000 logout

    The system was under memory stress where driver was not able to allocate an     SRB to carry out error recovery of cable pull.  The failure to flush causes     upper layer to start modifying scsi_cmnd.  When the system frees up some     memory, the subsequent cable pull trigger another command flush. At this     point the driver access a null pointer when attempting to DMA unmap the     SGL.

    Add a check to make sure commands are flush back on session tear down to     prevent the null pointer access.

    CVE-2023-52853:
    In the Linux kernel, the following vulnerability has been resolved:

    hid: cp2112: Fix duplicate workqueue initialization

    Previously the cp2112 driver called INIT_DELAYED_WORK within     cp2112_gpio_irq_startup, resulting in duplicate initilizations of the     workqueue on subsequent IRQ startups following an initial request. This     resulted in a warning in set_work_data in workqueue.c, as well as a rare     NULL dereference within process_one_work in workqueue.c.

    Initialize the workqueue within _probe instead.

    CVE-2022-49013:
    In the Linux kernel, the following vulnerability has been resolved:

    sctp: fix memory leak in sctp_stream_outq_migrate()

    When sctp_stream_outq_migrate() is called to release stream out resources,     the memory pointed to by prio_head in stream out is not released.

    The memory leak information is as follows:
     unreferenced object 0xffff88801fe79f80 (size 64):
     comm sctp_repo, pid 7957, jiffies 4294951704 (age 36.480s)      hex dump (first 32 bytes):
       80 9f e7 1f 80 88 ff ff 80 9f e7 1f 80 88 ff ff  ................
       90 9f e7 1f 80 88 ff ff 90 9f e7 1f 80 88 ff ff  ................
     backtrace:
       [<ffffffff81b215c6>] kmalloc_trace+0x26/0x60        [<ffffffff88ae517c>] sctp_sched_prio_set+0x4cc/0x770        [<ffffffff88ad64f2>] sctp_stream_init_ext+0xd2/0x1b0        [<ffffffff88aa2604>] sctp_sendmsg_to_asoc+0x1614/0x1a30        [<ffffffff88ab7ff1>] sctp_sendmsg+0xda1/0x1ef0        [<ffffffff87f765ed>] inet_sendmsg+0x9d/0xe0        [<ffffffff8754b5b3>] sock_sendmsg+0xd3/0x120        [<ffffffff8755446a>] __sys_sendto+0x23a/0x340        [<ffffffff87554651>] __x64_sys_sendto+0xe1/0x1b0        [<ffffffff89978b49>] do_syscall_64+0x39/0xb0        [<ffffffff89a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

Tenable has extracted the preceding description block directly from the Tencent Linux 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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-986934 advisory.

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

    sctp: fix memory leak in sctp_stream_outq_migrate()

    When sctp_stream_outq_migrate() is called to release stream out resources,     the memory pointed to by prio_head in stream out is not released.

    The memory leak information is as follows:
     unreferenced object 0xffff88801fe79f80 (size 64):
       comm sctp_repo, pid 7957, jiffies 4294951704 (age 36.480s)        hex dump (first 32 bytes):
         80 9f e7 1f 80 88 ff ff 80 9f e7 1f 80 88 ff ff  ................
         90 9f e7 1f 80 88 ff ff 90 9f e7 1f 80 88 ff ff  ................
       backtrace:
         [<ffffffff81b215c6>] kmalloc_trace+0x26/0x60          [<ffffffff88ae517c>] sctp_sched_prio_set+0x4cc/0x770          [<ffffffff88ad64f2>] sctp_stream_init_ext+0xd2/0x1b0          [<ffffffff88aa2604>] sctp_sendmsg_to_asoc+0x1614/0x1a30          [<ffffffff88ab7ff1>] sctp_sendmsg+0xda1/0x1ef0          [<ffffffff87f765ed>] inet_sendmsg+0x9d/0xe0          [<ffffffff8754b5b3>] sock_sendmsg+0xd3/0x120          [<ffffffff8755446a>] __sys_sendto+0x23a/0x340          [<ffffffff87554651>] __x64_sys_sendto+0xe1/0x1b0          [<ffffffff89978b49>] do_syscall_64+0x39/0xb0          [<ffffffff89a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

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 Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2025-988679 advisory.

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

    sctp: fix memory leak in sctp_stream_outq_migrate()

    When sctp_stream_outq_migrate() is called to release stream out resources,     the memory pointed to by prio_head in stream out is not released.

    The memory leak information is as follows:
     unreferenced object 0xffff88801fe79f80 (size 64):
       comm sctp_repo, pid 7957, jiffies 4294951704 (age 36.480s)        hex dump (first 32 bytes):
         80 9f e7 1f 80 88 ff ff 80 9f e7 1f 80 88 ff ff  ................
         90 9f e7 1f 80 88 ff ff 90 9f e7 1f 80 88 ff ff  ................
       backtrace:
         [<ffffffff81b215c6>] kmalloc_trace+0x26/0x60          [<ffffffff88ae517c>] sctp_sched_prio_set+0x4cc/0x770          [<ffffffff88ad64f2>] sctp_stream_init_ext+0xd2/0x1b0          [<ffffffff88aa2604>] sctp_sendmsg_to_asoc+0x1614/0x1a30          [<ffffffff88ab7ff1>] sctp_sendmsg+0xda1/0x1ef0          [<ffffffff87f765ed>] inet_sendmsg+0x9d/0xe0          [<ffffffff8754b5b3>] sock_sendmsg+0xd3/0x120          [<ffffffff8755446a>] __sys_sendto+0x23a/0x340          [<ffffffff87554651>] __x64_sys_sendto+0xe1/0x1b0          [<ffffffff89978b49>] do_syscall_64+0x39/0xb0          [<ffffffff89a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

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.

ID	Name	Product	Family	Published	Updated	Severity
225456	Linux Distros Unpatched Vulnerability : CVE-2022-49013	Nessus	Misc.	3/5/2025	1/15/2026	medium
170458	Amazon Linux 2 : kernel, --advisory ALAS2KERNEL-5.15-2023-012 (ALASKERNEL-5.15-2023-012)	Nessus	Amazon Linux Local Security Checks	1/24/2023	2/11/2026	high
305464	Unity Linux 20.1050e Security Update: kernel (UTSA-2026-006641)	Nessus	Unity Linux Local Security Checks	4/8/2026	4/8/2026	medium
170472	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2023-025)	Nessus	Amazon Linux Local Security Checks	1/24/2023	2/26/2026	high
200364	Amazon Linux 2 : kernel (ALASKERNEL-5.4-2024-071)	Nessus	Amazon Linux Local Security Checks	6/11/2024	1/26/2026	high
276192	TencentOS Server 4: kernel (TSSA-2025:0437)	Nessus	Tencent Local Security Checks	11/20/2025	11/20/2025	high
268405	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-986934)	Nessus	Unity Linux Local Security Checks	10/7/2025	10/15/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
273792	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988679)	Nessus	Unity Linux Local Security Checks	11/5/2025	11/5/2025	medium

Detections

Analytics

Plugins Search

medium

high

medium

high

high

high

medium

high

medium