An update of the linux package has been released.

The version of kernel installed on the remote host is prior to 5.4.172-90.336. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2022-021 advisory.

    A denial of service flaw for virtual machine guests in the Linux kernel's Xen hypervisor subsystem was     found in the way users call some interrupts with high frequency from one of the guests.A local user could     use this flaw to starve the resources resulting in a denial of service. (CVE-2021-28711)

    A denial of service flaw for virtual machine guests in the Linux kernel's Xen hypervisor subsystem was     found in the way users call some interrupts with high frequency from one of the guests.A local user could     use this flaw to starve the resources resulting in a denial of service. (CVE-2021-28712)

    A denial of service flaw for virtual machine guests in the Linux kernel's Xen hypervisor subsystem was     found in the way users call some interrupts with high frequency from one of the guests.A local user could     use this flaw to starve the resources resulting in a denial of service. (CVE-2021-28713)

    Incoming data packets for a guest in the Linux kernel's netback driver are buffered until the guest is     ready to process them. There are some measures taken for avoiding to pile up too much data, but those can     be bypassed by the guest: The timeout could even never trigger if the guest manages to have only one free     slot in its RX queue ring page and the next package would require more than one free slot, which may be     the case when using GSO, XDP, or software hashing. (CVE-2021-28714)

    Incoming data packets for a guest in the Linux kernel's netback driver are buffered until the guest is     ready to process them. There are some measures taken for avoiding to pile up too much data, but those can     be bypassed by the guest: There is a timeout how long the client side of an interface can stop consuming     new packets before it is assumed to have stalled, but this timeout is rather long (60 seconds by default).
    Using a UDP connection on a fast interface can easily accumulate gigabytes of data in that time.
    (CVE-2021-28715)

    A flaw was found in the Linux kernel's implementation of RDMA over infiniband. An attacker with a     privileged local account can leak kernel stack information when issuing commands to the     /dev/infiniband/rdma_cm device node. While this access is unlikely to leak sensitive user information, it     can be further used to defeat existing kernel protection mechanisms. (CVE-2021-3923)

    A flaw memory leak in the Linux kernel's eBPF for the Simulated networking device driver in the way user     uses BPF for the device such that function nsim_map_alloc_elem being called. A local user could use this     flaw to get unauthorized access to some data. (CVE-2021-4135)

    A data leak flaw was found in the way XFS_IOC_ALLOCSP IOCTL in the XFS filesystem allowed for size     increase of files with unaligned size. A local attacker could use this flaw to leak data on the XFS     filesystem otherwise not accessible to them. (CVE-2021-4155)

    An out-of-bounds write flaw was found in the Linux kernel's Aquantia AQtion Ethernet card Atlantic driver     in the way the ethernet card provides malicious input to the driver. This flaw allows a local user to     emulate the networking device and crash the system. The highest threat from this vulnerability is to     confidentiality, integrity, as well as system availability. (CVE-2021-43975)

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

    sctp: use call_rcu to free endpoint (CVE-2021-46929)

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

    i2c: validate user data in compat ioctl

    Wrong user data may cause warning in i2c_transfer(), ex: zero msgs.Userspace should not be able to trigger     warnings, so this patch addsvalidation checks for user data in compact ioctl to prevent reportedwarnings     (CVE-2021-46934)

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

    net: fix use-after-free in tw_timer_handler (CVE-2021-46936)

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

    Input: elantech - fix stack out of bound access in elantech_change_report_id() (CVE-2021-47097)

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

    aio: fix use-after-free due to missing POLLFREE handling (CVE-2021-47505)

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

    nfsd: fix use-after-free due to delegation race (CVE-2021-47506)

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

    nfsd: Fix nsfd startup race (again) (CVE-2021-47507)

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

    seg6: fix the iif in the IPv6 socket control block (CVE-2021-47515)

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

    serial: core: fix transmit-buffer reset and memleak (CVE-2021-47527)

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

    rxrpc: Fix rxrpc_local leak in rxrpc_lookup_peer() (CVE-2021-47538)

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

    net/mlx4_en: Fix an use-after-free bug in mlx4_en_try_alloc_resources() (CVE-2021-47541)

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

    net: qlogic: qlcnic: Fix a NULL pointer dereference in qlcnic_83xx_add_rings() (CVE-2021-47542)

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

    ipv6: fix memory leak in fib6_rule_suppress (CVE-2021-47546)

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

    ethernet: hisilicon: hns: hns_dsaf_misc: fix a possible array overflow in hns_dsaf_ge_srst_by_port()     (CVE-2021-47548)

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

    net: vlan: fix underflow for the real_dev refcnt (CVE-2021-47555)

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

    scsi: mpt3sas: Fix kernel panic during drive powercycle test (CVE-2021-47565)

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

    proc/vmcore: fix clearing user buffer by properly using clear_user() (CVE-2021-47566)

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

    net: nexthop: fix null pointer dereference when IPv6 is not enabled (CVE-2021-47572)

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

    scsi: scsi_debug: Sanity check block descriptor length in resp_mode_select() (CVE-2021-47576)

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

    ovl: fix warning in ovl_create_real() (CVE-2021-47579)

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

    sit: do not call ipip6_dev_free() from sit_init_net() (CVE-2021-47588)

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

    igbvf: fix double free in `igbvf_probe` (CVE-2021-47589)

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

    inet_diag: fix kernel-infoleak for UDP sockets (CVE-2021-47597)

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

    sch_cake: do not call cake_destroy() from cake_init() (CVE-2021-47598)

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

    dm btree remove: fix use after free in rebalance_children() (CVE-2021-47600)

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

    audit: improve robustness of the audit queue handling (CVE-2021-47603)

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

    net: netlink: af_netlink: Prevent empty skb by adding a check on len. (CVE-2021-47606)

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

    firmware: arm_scpi: Fix string overflow in SCPI genpd driver (CVE-2021-47609)

    A heap-based buffer overflow flaw was found in the way the legacy_parse_param function in the Filesystem     Context functionality of the Linux kernel verified the supplied parameters length. An unprivileged (in     case of unprivileged user namespaces enabled, otherwise needs namespaced CAP_SYS_ADMIN privilege) local     user able to open a filesystem that does not support the Filesystem Context API (and thus fallbacks to     legacy handling) could use this flaw to escalate their privileges on the system. (CVE-2022-0185)

    In various methods of kernel base drivers, there is a possible out of bounds write due to a heap buffer     overflow. This could lead to local escalation of privilege with System execution privileges needed. User     interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID:
    A-182388481References: Upstream kernel (CVE-2022-20166)

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

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

    aio: fix use-after-free due to missing POLLFREE handling

    signalfd_poll() and binder_poll() are special in that they use a     waitqueue whose lifetime is the current task, rather than the struct     file as is normally the case.  This is okay for blocking polls, since a     blocking poll occurs within one task; however, non-blocking polls     require another solution.  This solution is for the queue to be cleared     before it is freed, by sending a POLLFREE notification to all waiters.

    Unfortunately, only eventpoll handles POLLFREE.  A second type of     non-blocking poll, aio poll, was added in kernel v4.18, and it doesn't     handle POLLFREE.  This allows a use-after-free to occur if a signalfd or     binder fd is polled with aio poll, and the waitqueue gets freed.

    Fix this by making aio poll handle POLLFREE.

    A patch by Ramji Jiyani <ramjiyani@google.com>     (https://lore.kernel.org/r/20211027011834.2497484-1-ramjiyani@google.com)     tried to do this by making aio_poll_wake() always complete the request     inline if POLLFREE is seen.  However, that solution had two bugs.
    First, it introduced a deadlock, as it unconditionally locked the aio     context while holding the waitqueue lock, which inverts the normal     locking order.  Second, it didn't consider that POLLFREE notifications     are missed while the request has been temporarily de-queued.

    The second problem was solved by my previous patch.  This patch then     properly fixes the use-after-free by handling POLLFREE in a     deadlock-free way.  It does this by taking advantage of the fact that     freeing of the waitqueue is RCU-delayed, similar to what eventpoll does.

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 Tencent Linux installed on the remote TencentOS Server 3 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2025:0434 advisory.

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

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

    nilfs2: add missing check for inode numbers on directory entries

    Syzbot reported that mounting and unmounting a specific pattern of     corrupted nilfs2 filesystem images causes a use-after-free of metadata     file inodes, which triggers a kernel bug in lru_add_fn().

    As Jan Kara pointed out, this is because the link count of a metadata file     gets corrupted to 0, and nilfs_evict_inode(), which is called from iput(),     tries to delete that inode (ifile inode in this case).

    The inconsistency occurs because directories containing the inode numbers     of these metadata files that should not be visible in the namespace are     read without checking.

    Fix this issue by treating the inode numbers of these internal files as     errors in the sanity check helper when reading directory folios/pages.

    Also thanks to Hillf Danton and Matthew Wilcox for their initial mm-layer     analysis.

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

    jffs2: prevent xattr node from overflowing the eraseblock

    Add a check to make sure that the requested xattr node size is no larger     than the eraseblock minus the cleanmarker.

    Unlike the usual inode nodes, the xattr nodes aren't split into parts     and spread across multiple eraseblocks, which means that a xattr node     must not occupy more than one eraseblock. If the requested xattr value is     too large, the xattr node can spill onto the next eraseblock, overwriting     the nodes and causing errors such as:

    jffs2: argh. node added in wrong place at 0x0000b050(2)     jffs2: nextblock 0x0000a000, expected at 0000b00c     jffs2: error: (823) do_verify_xattr_datum: node CRC failed at 0x01e050,     read=0xfc892c93, calc=0x000000     jffs2: notice: (823) jffs2_get_inode_nodes: Node header CRC failed     at 0x01e00c. {848f,2fc4,0fef511f,59a3d171}     jffs2: Node at 0x0000000c with length 0x00001044 would run over the     end of the erase block     jffs2: Perhaps the file system was created with the wrong erase size?     jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found     at 0x00000010: 0x1044 instead

    This breaks the filesystem and can lead to KASAN crashes such as:

    BUG: KASAN: slab-out-of-bounds in jffs2_sum_add_kvec+0x125e/0x15d0     Read of size 4 at addr ffff88802c31e914 by task repro/830     CPU: 0 PID: 830 Comm: repro Not tainted 6.9.0-rc3+ #1     Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),     BIOS Arch Linux 1.16.3-1-1 04/01/2014     Call Trace:
     <TASK>      dump_stack_lvl+0xc6/0x120      print_report+0xc4/0x620      ? __virt_addr_valid+0x308/0x5b0      kasan_report+0xc1/0xf0      ? jffs2_sum_add_kvec+0x125e/0x15d0      ? jffs2_sum_add_kvec+0x125e/0x15d0      jffs2_sum_add_kvec+0x125e/0x15d0      jffs2_flash_direct_writev+0xa8/0xd0      jffs2_flash_writev+0x9c9/0xef0      ? __x64_sys_setxattr+0xc4/0x160      ? do_syscall_64+0x69/0x140      ? entry_SYSCALL_64_after_hwframe+0x76/0x7e      [...]

    Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

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

    nilfs2: fix use-after-free of timer for log writer thread

    Patch series nilfs2: fix log writer related issues.

    This bug fix series covers three nilfs2 log writer-related issues,     including a timer use-after-free issue and potential deadlock issue on     unmount, and a potential freeze issue in event synchronization found     during their analysis.  Details are described in each commit log.


    This patch (of 3):

    A use-after-free issue has been reported regarding the timer sc_timer on     the nilfs_sc_info structure.

    The problem is that even though it is used to wake up a sleeping log     writer thread, sc_timer is not shut down until the nilfs_sc_info structure     is about to be freed, and is used regardless of the thread's lifetime.

    Fix this issue by limiting the use of sc_timer only while the log writer     thread is alive.

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

    fs/9p: only translate RWX permissions for plain 9P2000

    Garbage in plain 9P2000's perm bits is allowed through, which causes it     to be able to set (among others) the suid bit. This was presumably not     the intent since the unix extended bits are handled explicitly and     conditionally on .u.

    CVE-2021-47505:
    In the Linux kernel, the following vulnerability has been resolved:

    aio: fix use-after-free due to missing POLLFREE handling

    signalfd_poll() and binder_poll() are special in that they use a     waitqueue whose lifetime is the current task, rather than the struct     file as is normally the case.  This is okay for blocking polls, since a     blocking poll occurs within one task; however, non-blocking polls     require another solution.  This solution is for the queue to be cleared     before it is freed, by sending a POLLFREE notification to all waiters.

    Unfortunately, only eventpoll handles POLLFREE.  A second type of     non-blocking poll, aio poll, was added in kernel v4.18, and it doesn't     handle POLLFREE.  This allows a use-after-free to occur if a signalfd or     binder fd is polled with aio poll, and the waitqueue gets freed.

    Fix this by making aio poll handle POLLFREE.

    A patch by Ramji Jiyani <ramjiyani@google.com>     (https://lore.kernel.org/r/20211027011834.2497484-1-ramjiyani@google.com)     tried to do this by making aio_poll_wake() always complete the request     inline if POLLFREE is seen.  However, that solution had two bugs.
    First, it introduced a deadlock, as it unconditionally locked the aio     context while holding the waitqueue lock, which inverts the normal     locking order.  Second, it didn't consider that POLLFREE notifications     are missed while the request has been temporarily de-queued.

    The second problem was solved by my previous patch.  This patch then     properly fixes the use-after-free by handling POLLFREE in a     deadlock-free way.  It does this by taking advantage of the fact that     freeing of the waitqueue is RCU-delayed, similar to what eventpoll does.

    CVE-2021-46993:
    In the Linux kernel, the following vulnerability has been resolved:

    sched: Fix out-of-bound access in uclamp

    Util-clamp places tasks in different buckets based on their clamp values     for performance reasons. However, the size of buckets is currently     computed using a rounding division, which can lead to an off-by-one     error in some configurations.

    For instance, with 20 buckets, the bucket size will be 1024/20=51. A     task with a clamp of 1024 will be mapped to bucket id 1024/51=20. Sadly,     correct indexes are in range [0,19], hence leading to an out of bound     memory access.

    Clamp the bucket id to fix the issue.

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.

ID	Name	Product	Family	Published	Updated	Severity
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	7/22/2021	10/9/2026	high
238832	TencentOS Server 3: kernel (TSSA-2024:0719)	Nessus	Tencent Local Security Checks	6/16/2025	11/20/2025	high
160423	Amazon Linux 2 : kernel (ALASKERNEL-5.4-2022-021)	Nessus	Amazon Linux Local Security Checks	5/2/2022	2/26/2026	high
273452	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988947)	Nessus	Unity Linux Local Security Checks	11/5/2025	11/5/2025	high
276021	TencentOS Server 3: kernel (TSSA-2025:0434)	Nessus	Tencent Local Security Checks	11/20/2025	11/20/2025	high

Detections

Analytics

Plugins Search

high

high

high

high

high