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-2026:0793 advisory.

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

    CVE-2026-31502:
    In the Linux kernel, the following vulnerability has been resolved: xfs: resample the data fork mapping     after cycling ILOCK. xfs_reflink_fill_{cow_hole,delalloc} are both presented with an inode, a data fork     mapping, and a cow fork mapping. Unfortunately, these two helpers cycle the ILOCK to grab a transaction,     which means that the mappings are stale as soon as we reacquire the ILOCK. Currently we refresh the cow     fork mapping by re-calling xfs_find_trim_cow_extent, but we don't refresh the data fork mapping     beforehand, which means that the xfs_bmap_trim_cow in that function queries the refcount btree about the     wrong physical blocks and returns an inaccurate value in *shared. If *shared is now false, the directio     write proceeds with a stale data fork mapping. Fix this by querying the data fork mapping if the sequence     counter changes across the ILOCK cycle.

    CVE-2026-43456:
    In the Linux kernel, the following vulnerability has been resolved:

    bonding: fix type confusion in bond_setup_by_slave()

    kernel BUG at net/core/skbuff.c:2306!     Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI     RIP: 0010:pskb_expand_head+0xa08/0xfe0 net/core/skbuff.c:2306     RSP: 0018:ffffc90004aff760 EFLAGS: 00010293     RAX: 0000000000000000 RBX: ffff88807e3c8780 RCX: ffffffff89593e0e     RDX: ffff88807b7c4900 RSI: ffffffff89594747 RDI: ffff88807b7c4900     RBP: 0000000000000820 R08: 0000000000000005 R09: 0000000000000000     R10: 00000000961a63e0 R11: 0000000000000000 R12: ffff88807e3c8780     R13: 00000000961a6560 R14: dffffc0000000000 R15: 00000000961a63e0     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033     CR2: 00007fe1a0ed8df0 CR3: 000000002d816000 CR4: 00000000003526f0     Call Trace:
     <TASK>      ipgre_header+0xdd/0x540 net/ipv4/ip_gre.c:900      dev_hard_header include/linux/netdevice.h:3439 [inline]      packet_snd net/packet/af_packet.c:3028 [inline]      packet_sendmsg+0x3ae5/0x53c0 net/packet/af_packet.c:3108      sock_sendmsg_nosec net/socket.c:727 [inline]
     __sock_sendmsg net/socket.c:742 [inline]
     ____sys_sendmsg+0xa54/0xc30 net/socket.c:2592
     ___sys_sendmsg+0x190/0x1e0 net/socket.c:2646
     __sys_sendmsg+0x170/0x220 net/socket.c:2678      do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]      do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94      entry_SYSCALL_64_after_hwframe+0x77/0x7f     RIP: 0033:0x7fe1a0e6c1a9

    When a non-Ethernet device (e.g. GRE tunnel) is enslaved to a bond,     bond_setup_by_slave() directly copies the slave's header_ops to the     bond device:

      bond_dev->header_ops = slave_dev->header_ops;

    This causes a type confusion when dev_hard_header() is later called     on the bond device. Functions like ipgre_header(), ip6gre_header(),all use     netdev_priv(dev) to access their device-specific private data. When     called with the bond device, netdev_priv() returns the bond's private     data (struct bonding) instead of the expected type (e.g. struct     ip_tunnel), leading to garbage values being read and kernel crashes.

    Fix this by introducing bond_header_ops with wrapper functions that     delegate to the active slave's header_ops using the slave's own     device. This ensures netdev_priv() in the slave's header functions     always receives the correct device.

    The fix is placed in the bonding driver rather than individual device     drivers, as the root cause is bond blindly inheriting header_ops from     the slave without considering that these callbacks expect a specific     netdev_priv() layout.

    The type confusion can be observed by adding a printk in     ipgre_header() and running the following commands:

      ip link add dummy0 type dummy       ip addr add 10.0.0.1/24 dev dummy0       ip link set dummy0 up       ip link add gre1 type gre local 10.0.0.1       ip link add bond1 type bond mode active-backup       ip link set gre1 master bond1       ip link set gre1 up       ip link set bond1 up       ip addr add fe80::1/64 dev bond1

    CVE-2026-64600:
    In the Linux kernel, the following vulnerability has been resolved:

    team: fix header_ops type confusion with non-Ethernet ports

    Similar to commit 950803f72547 (bonding: fix type confusion in     bond_setup_by_slave()) team has the same class of header_ops type     confusion.

    For non-Ethernet ports, team_setup_by_port() copies port_dev->header_ops     directly. When the team device later calls dev_hard_header() or     dev_parse_header(), these callbacks can run with the team net_device     instead of the real lower device, so netdev_priv(dev) is interpreted as     the wrong private type and can crash.

    The syzbot report shows a crash in bond_header_create(), but the root     cause is in team: the topology is gre -> bond -> team, and team calls     the inherited header_ops with its own net_device instead of the lower     device, so bond_header_create() receives a team device and interprets     netdev_priv() as bonding private data, causing a type confusion crash.

    Fix this by introducing team header_ops wrappers for create/parse,     selecting a team port under RCU, and calling the lower device callbacks     with port->dev, so each callback always sees the correct net_device     context.

    Also pass the selected lower device to the lower parse callback, so     recursion is bounded in stacked non-Ethernet topologies and parse     callbacks always run with the correct device context.

    CVE-2026-23451:
    In the Linux kernel, the following vulnerability has been resolved:

    bonding: prevent potential infinite loop in bond_header_parse()

    bond_header_parse() can loop if a stack of two bonding devices is setup,     because skb->dev always points to the hierarchy top.

    Add new const struct net_device *dev parameter to     (struct header_ops)->parse() method to make sure the recursion     is bounded, and that the final leaf parse method is called.

    CVE-2026-64564:
    In the Linux kernel, the following vulnerability has been resolved: sctp: don't free the ASCONF's own     transport in DEL-IP processing. sctp_process_asconf() caches the transport the ASCONF chunk is processed     against in asconf->transport. For an ASCONF located through its Address Parameter, that cached transport     corresponds to the Address Parameter, which need not be the packet's source address. A single ASCONF can     carry DEL-IP for the cached transport followed by a wildcard DEL-IP, causing use-after-free of the freed     transport.

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

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

    CVE-2026-31502:
    In the Linux kernel, the following vulnerability has been resolved: xfs: resample the data fork mapping     after cycling ILOCK. xfs_reflink_fill_{cow_hole,delalloc} are both presented with an inode, a data fork     mapping, and a cow fork mapping. Unfortunately, these two helpers cycle the ILOCK to grab a transaction,     which means that the mappings are stale as soon as we reacquire the ILOCK. Currently we refresh the cow     fork mapping by re-calling xfs_find_trim_cow_extent, but we don't refresh the data fork mapping     beforehand, which means that the xfs_bmap_trim_cow in that function queries the refcount btree about the     wrong physical blocks and returns an inaccurate value in *shared. If *shared is now false, the directio     write proceeds with a stale data fork mapping. Fix this by querying the data fork mapping if the sequence     counter changes across the ILOCK cycle.

    CVE-2026-43456:
    In the Linux kernel, the following vulnerability has been resolved:

    bonding: fix type confusion in bond_setup_by_slave()

    kernel BUG at net/core/skbuff.c:2306!     Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI     RIP: 0010:pskb_expand_head+0xa08/0xfe0 net/core/skbuff.c:2306     RSP: 0018:ffffc90004aff760 EFLAGS: 00010293     RAX: 0000000000000000 RBX: ffff88807e3c8780 RCX: ffffffff89593e0e     RDX: ffff88807b7c4900 RSI: ffffffff89594747 RDI: ffff88807b7c4900     RBP: 0000000000000820 R08: 0000000000000005 R09: 0000000000000000     R10: 00000000961a63e0 R11: 0000000000000000 R12: ffff88807e3c8780     R13: 00000000961a6560 R14: dffffc0000000000 R15: 00000000961a63e0     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033     CR2: 00007fe1a0ed8df0 CR3: 000000002d816000 CR4: 00000000003526f0     Call Trace:
     <TASK>      ipgre_header+0xdd/0x540 net/ipv4/ip_gre.c:900      dev_hard_header include/linux/netdevice.h:3439 [inline]      packet_snd net/packet/af_packet.c:3028 [inline]      packet_sendmsg+0x3ae5/0x53c0 net/packet/af_packet.c:3108      sock_sendmsg_nosec net/socket.c:727 [inline]
     __sock_sendmsg net/socket.c:742 [inline]
     ____sys_sendmsg+0xa54/0xc30 net/socket.c:2592
     ___sys_sendmsg+0x190/0x1e0 net/socket.c:2646
     __sys_sendmsg+0x170/0x220 net/socket.c:2678      do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]      do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94      entry_SYSCALL_64_after_hwframe+0x77/0x7f     RIP: 0033:0x7fe1a0e6c1a9

    When a non-Ethernet device (e.g. GRE tunnel) is enslaved to a bond,     bond_setup_by_slave() directly copies the slave's header_ops to the     bond device:

      bond_dev->header_ops = slave_dev->header_ops;

    This causes a type confusion when dev_hard_header() is later called     on the bond device. Functions like ipgre_header(), ip6gre_header(),all use     netdev_priv(dev) to access their device-specific private data. When     called with the bond device, netdev_priv() returns the bond's private     data (struct bonding) instead of the expected type (e.g. struct     ip_tunnel), leading to garbage values being read and kernel crashes.

    Fix this by introducing bond_header_ops with wrapper functions that     delegate to the active slave's header_ops using the slave's own     device. This ensures netdev_priv() in the slave's header functions     always receives the correct device.

    The fix is placed in the bonding driver rather than individual device     drivers, as the root cause is bond blindly inheriting header_ops from     the slave without considering that these callbacks expect a specific     netdev_priv() layout.

    The type confusion can be observed by adding a printk in     ipgre_header() and running the following commands:

      ip link add dummy0 type dummy       ip addr add 10.0.0.1/24 dev dummy0       ip link set dummy0 up       ip link add gre1 type gre local 10.0.0.1       ip link add bond1 type bond mode active-backup       ip link set gre1 master bond1       ip link set gre1 up       ip link set bond1 up       ip addr add fe80::1/64 dev bond1

    CVE-2026-23451:
    In the Linux kernel, the following vulnerability has been resolved:

    team: fix header_ops type confusion with non-Ethernet ports

    Similar to commit 950803f72547 (bonding: fix type confusion in     bond_setup_by_slave()) team has the same class of header_ops type     confusion.

    For non-Ethernet ports, team_setup_by_port() copies port_dev->header_ops     directly. When the team device later calls dev_hard_header() or     dev_parse_header(), these callbacks can run with the team net_device     instead of the real lower device, so netdev_priv(dev) is interpreted as     the wrong private type and can crash.

    The syzbot report shows a crash in bond_header_create(), but the root     cause is in team: the topology is gre -> bond -> team, and team calls     the inherited header_ops with its own net_device instead of the lower     device, so bond_header_create() receives a team device and interprets     netdev_priv() as bonding private data, causing a type confusion crash.

    Fix this by introducing team header_ops wrappers for create/parse,     selecting a team port under RCU, and calling the lower device callbacks     with port->dev, so each callback always sees the correct net_device     context.

    Also pass the selected lower device to the lower parse callback, so     recursion is bounded in stacked non-Ethernet topologies and parse     callbacks always run with the correct device context.

    CVE-2026-64600:
    In the Linux kernel, the following vulnerability has been resolved:

    bonding: prevent potential infinite loop in bond_header_parse()

    bond_header_parse() can loop if a stack of two bonding devices is setup,     because skb->dev always points to the hierarchy top.

    Add new const struct net_device *dev parameter to     (struct header_ops)->parse() method to make sure the recursion     is bounded, and that the final leaf parse method is called.

    CVE-2026-64564:
    In the Linux kernel, the following vulnerability has been resolved: sctp: don't free the ASCONF's own     transport in DEL-IP processing. sctp_process_asconf() caches the transport the ASCONF chunk is processed     against in asconf->transport. For an ASCONF located through its Address Parameter, that cached transport     corresponds to the Address Parameter, which need not be the packet's source address. A single ASCONF can     carry DEL-IP for the cached transport followed by a wildcard DEL-IP, causing use-after-free of the freed     transport.

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.

An update of the linux package has been released.

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-2026:0792 advisory.

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

    CVE-2026-31502:
    In the Linux kernel, the following vulnerability has been resolved: xfs: resample the data fork mapping     after cycling ILOCK. xfs_reflink_fill_{cow_hole,delalloc} are both presented with an inode, a data fork     mapping, and a cow fork mapping. Unfortunately, these two helpers cycle the ILOCK to grab a transaction,     which means that the mappings are stale as soon as we reacquire the ILOCK. Currently we refresh the cow     fork mapping by re-calling xfs_find_trim_cow_extent, but we don't refresh the data fork mapping     beforehand, which means that the xfs_bmap_trim_cow in that function queries the refcount btree about the     wrong physical blocks and returns an inaccurate value in *shared. If *shared is now false, the directio     write proceeds with a stale data fork mapping. Fix this by querying the data fork mapping if the sequence     counter changes across the ILOCK cycle.

    CVE-2026-53362:
    In the Linux kernel, the following vulnerability has been resolved:

    eventpoll: fix ep_remove struct eventpoll / struct file UAF

    ep_remove() (via ep_remove_file()) cleared file->f_ep under     file->f_lock but then kept using @file inside the critical section     (is_file_epoll(), hlist_del_rcu() through the head, spin_unlock).
    A concurrent __fput() taking the eventpoll_release() fastpath in     that window observed the transient NULL, skipped     eventpoll_release_file() and ran to f_op->release / file_free().

    For the epoll-watches-epoll case, f_op->release is     ep_eventpoll_release() -> ep_clear_and_put() -> ep_free(), which     kfree()s the watched struct eventpoll. Its embedded ->refs     hlist_head is exactly where epi->fllink.pprev points, so the     subsequent hlist_del_rcu()'s *pprev = next scribbles into freed     kmalloc-192 memory.

    In addition, struct file is SLAB_TYPESAFE_BY_RCU, so the slot     backing @file could be recycled by alloc_empty_file() --     reinitializing f_lock and f_ep -- while ep_remove() is still     nominally inside that lock. The upshot is an attacker-controllable     kmem_cache_free() against the wrong slab cache.

    Pin @file via epi_fget() at the top of ep_remove() and gate the     critical section on the pin succeeding. With the pin held @file     cannot reach refcount zero, which holds __fput() off and     transitively keeps the watched struct eventpoll alive across the     hlist_del_rcu() and the f_lock use, closing both UAFs.

    If the pin fails @file has already reached refcount zero and its
    __fput() is in flight. Because we bailed before clearing f_ep,     that path takes the eventpoll_release() slow path into     eventpoll_release_file() and blocks on ep->mtx until the waiter     side's ep_clear_and_put() drops it. The bailed epi's share of     ep->refcount stays intact, so the trailing ep_refcount_dec_and_test()     in ep_clear_and_put() cannot free the eventpoll out from under     eventpoll_release_file(); the orphaned epi is then cleaned up     there.

    A successful pin also proves we are not racing     eventpoll_release_file() on this epi, so drop the now-redundant     re-check of epi->dying under f_lock. The cheap lockless     READ_ONCE(epi->dying) fast-path bailout stays.

    CVE-2026-43456:
    In the Linux kernel, the following vulnerability has been resolved:

    ipv6: account for fraggap on the paged allocation path

    In __ip6_append_data(), when the paged-allocation branch is taken     (MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are     computed as

            alloclen = fragheaderlen + transhdrlen;
            pagedlen = datalen - transhdrlen;

    datalen already includes fraggap (datalen = length + fraggap). When     fraggap is non-zero, this is not the first skb and transhdrlen is zero.
    The fraggap bytes carried over from the previous skb are copied just past     the fragment headers in the new skb's linear area. The linear area is     therefore undersized by fraggap bytes while pagedlen is overstated by the     same amount, and the copy writes past skb->end into the trailing     skb_shared_info.

    An unprivileged user can trigger this via a UDPv6 socket using     MSG_MORE together with MSG_SPLICE_PAGES.

    The bad accounting was introduced by commit 773ba4fe9104 (ipv6:
    avoid partial copy for zc). Before commit ce650a166335 (udp6: Fix
    __ip6_append_data()'s handling of MSG_SPLICE_PAGES), the negative     copy value caused -EINVAL to be returned. That later commit allowed     MSG_SPLICE_PAGES to proceed in this case, making the corruption     triggerable.

    The non-paged branch sets alloclen to fraglen, which already accounts     for fraggap because datalen does. Bring the paged branch in line by     adding fraggap to alloclen and subtracting it from pagedlen.

    After this adjustment, copy no longer collapses to -fraggap on the     paged path, so remove the stale comment describing that old arithmetic.
    Since a negative copy is no longer expected for a valid MSG_SPLICE_PAGES     case, remove the MSG_SPLICE_PAGES exception from the negative copy check.

    CVE-2026-46242:
    In the Linux kernel, the following vulnerability has been resolved:

    bonding: fix type confusion in bond_setup_by_slave()

    kernel BUG at net/core/skbuff.c:2306!     Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI     RIP: 0010:pskb_expand_head+0xa08/0xfe0 net/core/skbuff.c:2306     RSP: 0018:ffffc90004aff760 EFLAGS: 00010293     RAX: 0000000000000000 RBX: ffff88807e3c8780 RCX: ffffffff89593e0e     RDX: ffff88807b7c4900 RSI: ffffffff89594747 RDI: ffff88807b7c4900     RBP: 0000000000000820 R08: 0000000000000005 R09: 0000000000000000     R10: 00000000961a63e0 R11: 0000000000000000 R12: ffff88807e3c8780     R13: 00000000961a6560 R14: dffffc0000000000 R15: 00000000961a63e0     CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033     CR2: 00007fe1a0ed8df0 CR3: 000000002d816000 CR4: 00000000003526f0     Call Trace:
     <TASK>      ipgre_header+0xdd/0x540 net/ipv4/ip_gre.c:900      dev_hard_header include/linux/netdevice.h:3439 [inline]      packet_snd net/packet/af_packet.c:3028 [inline]      packet_sendmsg+0x3ae5/0x53c0 net/packet/af_packet.c:3108      sock_sendmsg_nosec net/socket.c:727 [inline]
     __sock_sendmsg net/socket.c:742 [inline]
     ____sys_sendmsg+0xa54/0xc30 net/socket.c:2592
     ___sys_sendmsg+0x190/0x1e0 net/socket.c:2646
     __sys_sendmsg+0x170/0x220 net/socket.c:2678      do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]      do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94      entry_SYSCALL_64_after_hwframe+0x77/0x7f     RIP: 0033:0x7fe1a0e6c1a9

    When a non-Ethernet device (e.g. GRE tunnel) is enslaved to a bond,     bond_setup_by_slave() directly copies the slave's header_ops to the     bond device:

      bond_dev->header_ops = slave_dev->header_ops;

    This causes a type confusion when dev_hard_header() is later called     on the bond device. Functions like ipgre_header(), ip6gre_header(),all use     netdev_priv(dev) to access their device-specific private data. When     called with the bond device, netdev_priv() returns the bond's private     data (struct bonding) instead of the expected type (e.g. struct     ip_tunnel), leading to garbage values being read and kernel crashes.

    Fix this by introducing bond_header_ops with wrapper functions that     delegate to the active slave's header_ops using the slave's own     device. This ensures netdev_priv() in the slave's header functions     always receives the correct device.

    The fix is placed in the bonding driver rather than individual device     drivers, as the root cause is bond blindly inheriting header_ops from     the slave without considering that these callbacks expect a specific     netdev_priv() layout.

    The type confusion can be observed by adding a printk in     ipgre_header() and running the following commands:

      ip link add dummy0 type dummy       ip addr add 10.0.0.1/24 dev dummy0       ip link set dummy0 up       ip link add gre1 type gre local 10.0.0.1       ip link add bond1 type bond mode active-backup       ip link set gre1 master bond1       ip link set gre1 up       ip link set bond1 up       ip addr add fe80::1/64 dev bond1

    CVE-2026-23451:
    In the Linux kernel, the following vulnerability has been resolved:

    team: fix header_ops type confusion with non-Ethernet ports

    Similar to commit 950803f72547 (bonding: fix type confusion in     bond_setup_by_slave()) team has the same class of header_ops type     confusion.

    For non-Ethernet ports, team_setup_by_port() copies port_dev->header_ops     directly. When the team device later calls dev_hard_header() or     dev_parse_header(), these callbacks can run with the team net_device     instead of the real lower device, so netdev_priv(dev) is interpreted as     the wrong private type and can crash.

    The syzbot report shows a crash in bond_header_create(), but the root     cause is in team: the topology is gre -> bond -> team, and team calls     the inherited header_ops with its own net_device instead of the lower     device, so bond_header_create() receives a team device and interprets     netdev_priv() as bonding private data, causing a type confusion crash.

    Fix this by introducing team header_ops wrappers for create/parse,     selecting a team port under RCU, and calling the lower device callbacks     with port->dev, so each callback always sees the correct net_device     context.

    Also pass the selected lower device to the lower parse callback, so     recursion is bounded in stacked non-Ethernet topologies and parse     callbacks always run with the correct device context.

    CVE-2026-64600:
    In the Linux kernel, the following vulnerability has been resolved:

    bonding: prevent potential infinite loop in bond_header_parse()

    bond_header_parse() can loop if a stack of two bonding devices is setup,     because skb->dev always points to the hierarchy top.

    Add new const struct net_device *dev parameter to     (struct header_ops)->parse() method to make sure the recursion     is bounded, and that the final leaf parse method is called.

    CVE-2026-64531:
    In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: reject oversized     nested action attrs. Open vSwitch stores generated flow actions as nlattrs, whose nla_len field is u16. An     oversized generated container can be closed with a truncated nla_len, causing later dump or teardown to     walk a structurally different stream than the one that was validated. An oversized nested CLONE/CT action     may cause subsequent bytes to be interpreted as independent actions.

    CVE-2026-64564:
    In the Linux kernel, the following vulnerability has been resolved: sctp: don't free the ASCONF's own     transport in DEL-IP processing. sctp_process_asconf() caches the transport the ASCONF chunk is processed     against in asconf->transport. For an ASCONF located through its Address Parameter, that cached transport     corresponds to the Address Parameter, which need not be the packet's source address. A single ASCONF can     carry DEL-IP for the cached transport followed by a wildcard DEL-IP, causing use-after-free of the freed     transport.

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 CentOS Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS7:CLSA-2026:1788170774 advisory.

  - A race condition in Linux kernel SCTP sockets (net/sctp/socket.c) before 5.12-rc8 can lead to kernel     privilege escalation from the context of a network service or an unprivileged process. If     sctp_destroy_sock is called without sock_net(sk)->sctp.addr_wq_lock then an element is removed from the     auto_asconf_splist list without any proper locking. This can be exploited by an attacker with network     service privileges to escalate to root or from the context of an unprivileged user directly if a     BPF_CGROUP_INET_SOCK_CREATE is attached which denies creation of some SCTP socket. (CVE-2021-23133)

  - In the Linux kernel, the following vulnerability has been resolved: drm: Fix use-after-free read in     drm_getunique() There is a time-of-check-to-time-of-use error in drm_getunique() due to retrieving     file_priv->master prior to locking the device's master mutex. An example can be seen in the crash report     of the use-after-free error found by Syzbot:
    https://syzkaller.appspot.com/bug?id=148d2f1dfac64af52ffd27b661981a540724f803 In the report, the master     pointer was used after being freed. This is because another process had acquired the device's master mutex     in drm_setmaster_ioctl(), then overwrote fpriv->master in drm_new_set_master(). The old value of     fpriv->master was subsequently freed before the mutex was unlocked. To fix this, we lock the device's     master mutex before retrieving the pointer from from fpriv->master. This patch passes the Syzbot     reproducer test. (CVE-2021-47280)

  - In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Fix kernel panic during     drive powercycle test While looping over shost's sdev list it is possible that one of the drives is     getting removed and its sas_target object is freed but its sdev object remains intact. Consequently, a     kernel panic can occur while the driver is trying to access the sas_address field of sas_target object     without also checking the sas_target object for NULL. (CVE-2021-47565)

  - In the Linux kernel, the following vulnerability has been resolved: dm btree remove: fix use after free in     rebalance_children() Move dm_tm_unlock() after dm_tm_dec(). (CVE-2021-47600)

  - In the Linux kernel, the following vulnerability has been resolved: media: pvrusb2: fix array-index-out-     of-bounds in pvr2_i2c_core_init Syzbot reported that -1 is used as array index. The problem was in missing     validation check. hdw->unit_number is initialized with -1 and then if init table walk fails this value     remains unchanged. Since code blindly uses this member for array indexing adding sanity check is the     easiest fix for that. hdw->workpoll initialization moved upper to prevent warning in __flush_work.
    (CVE-2022-49478)

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

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

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

    The following security issues were fixed:

    - CVE-2024-57841,CVE-2026-53260: net: fix memory leak in tcp_conn_request() (bsc#1235944 bsc#1269731).
    - CVE-2025-68214: timers: Fix NULL function pointer race in timer_shutdown_sync() (bsc#1255225).
    - CVE-2026-23451: bonding: prevent potential infinite loop in bond_header_parse() (bsc#1261604).
    - CVE-2026-31502: team: fix header_ops type confusion with non-Ethernet ports (bsc#1263072).
    - CVE-2026-43147: Revert 'PCI/IOV: Add PCI rescan-remove locking when enabling/disabling SR-IOV'     (bsc#1264642).
    - CVE-2026-43456: bonding: fix type confusion in bond_setup_by_slave() (bsc#1264734).
    - CVE-2026-45968: cpuidle: Skip governor when only one idle state is available (bsc#1267023).
    - CVE-2026-52910: bpf: Free reuseport cBPF prog after RCU grace period (bsc#1268659).
    - CVE-2026-52912: netfilter: nf_queue: hold bridge skb->dev while queued (bsc#1269000).
    - CVE-2026-52929: sctp: stream: fully roll back denied add-stream state (bsc#1269004).
    - CVE-2026-52977: futex: Prevent lockup in requeue-PI during signal/ timeout wakeup (bsc#1269242).
    - CVE-2026-52994: vsock/virtio: fix MSG_ZEROCOPY pinned-pages accounting (bsc#1269126).
    - CVE-2026-53059: dm log: fix out-of-bounds write due to region_count overflow (bsc#1269655).
    - CVE-2026-53110: selftests/bpf: Add ASSERT_OK_FD macro (bsc#1269985).
    - CVE-2026-53163: locking/rtmutex: Skip remove_waiter() when waiter is not enqueued (bsc#1269306).
    - CVE-2026-53264: net/sched: act_api: use RCU with deferred freeing for action lifecycle (bsc#1269238).
    - CVE-2026-53365: vsock/virtio: fix zerocopy completion for multi-skb sends (bsc#1271365).
    - CVE-2026-53381: virtiofs: fix UAF on submount umount (bsc#1271830).
    - CVE-2026-63801: tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done (bsc#1272230).
    - CVE-2026-63823: keys: Pin request_key_auth payload in instantiate paths (bsc#1272182).
    - CVE-2026-63827: apparmor: fix use-after-free in rawdata dedup loop (bsc#1272179).
    - CVE-2026-63879: drm/amdgpu: fix amdgpu_hmm_range_get_pages (bsc#1272569).
    - CVE-2026-63881: drm/amdkfd: fix a vulnerability of integer overflow in kfd debugger (bsc#1272571).
    - CVE-2026-63887: scsi: target: iscsi: Bound iscsi_encode_text_output() appends to rsp_buf (bsc#1272385).
    - CVE-2026-63888: scsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()     (bsc#1272390).
    - CVE-2026-63920: ipv6: validate extension header length before copying to cmsg (bsc#1272877).
    - CVE-2026-63944: Bluetooth: hci_sync: fix UAF in hci_le_create_cis_sync (bsc#1272662).
    - CVE-2026-63970: vsock/virtio: bind uarg before filling zerocopy skb (bsc#1272673).
    - CVE-2026-63992: tunnels: do not assume transport header in iptunnel_pmtud_check_icmp() (bsc#1272868).
    - CVE-2026-64000: net: hsr: fix potential OOB access in supervision frame handling (bsc#1273030).
    - CVE-2026-64002: ipv4: free net->ipv4.sysctl_local_reserved_ports after unregister_net_sysctl_table()     (bsc#1273774).
    - CVE-2026-64007: netfilter: synproxy: refresh tcphdr after skb_ensure_writable (bsc#1273105).
    - CVE-2026-64010: nfc: llcp: Fix use-after-free race in nfc_llcp_recv_cc() (bsc#1273882).
    - CVE-2026-64011: nfc: llcp: Fix use-after-free in llcp_sock_release() (bsc#1273891).
    - CVE-2026-64015: security/keys: fix missed RCU read section on lookup (bsc#1273762).
    - CVE-2026-64029: ALSA: seq: Serialize UMP output teardown with event_input (bsc#1273766).
    - CVE-2026-64048: net/smc: reject CHID-0 ACCEPT that matches an empty ism_dev slot (bsc#1273484).
    - CVE-2026-64098: drm/virtio: use uninterruptible resv lock for plane updates (bsc#1273488).
    - CVE-2026-64109: af_unix: Peek the queue synchronized (bsc#1273748).
    - CVE-2026-64114: ipv4: raw: reject IP_HDRINCL packets with ihl < 5 (bsc#1273742).
    - CVE-2026-64115: vsock/vmci: fix UAF when peer resets connection during handshake (bsc#1273745).
    - CVE-2026-64121: net: ifb: report ethtool stats over num_tx_queues (bsc#1273743).
    - CVE-2026-64217: netfs: Fix overrun check in netfs_extract_user_iter() (bsc#1272798).
    - CVE-2026-64268: RDMA/siw: bound Read Response placement to the RREAD length (bsc#1273276).
    - CVE-2026-64304: crypto: qat - validate RSA CRT component lengths (bsc#1273944).
    - CVE-2026-64312: crypto: pcrypt - restore callback for non-parallel fallback (bsc#1273968).
    - CVE-2026-64355: bpf: Reject fragmented frames in devmap (bsc#1273422).
    - CVE-2026-64383: smb: client: fix double-free in SMB2_flush() replay (bsc#1273426).
    - CVE-2026-64384: smb: client: fix change notify replay double-free (bsc#1274541).
    - CVE-2026-64385: smb: client: fix double-free in SMB2_ioctl() replay (bsc#1274539).
    - CVE-2026-64386: smb: client: fix query_info() replay double-free (bsc#1274543).
    - CVE-2026-64387: smb: client: fix query directory replay double-free (bsc#1274545).
    - CVE-2026-64423: ipv4: igmp: remove multicast group from hash table on device destruction (bsc#1274274).
    - CVE-2026-64450: tipc: fix out-of-bounds read in broadcast Gap ACK blocks (bsc#1273523).
    - CVE-2026-64481: ALSA: hda/cs35l41: Fix firmware load work teardown (bsc#1274547).
    - CVE-2026-64541: net/smc: fix UAF in smc_cdc_rx_handler() by pinning the socket (bsc#1273303).
    - CVE-2026-64543: tipc: fix use-after-free of the discoverer in tipc_disc_rcv() (bsc#1273311).
    - CVE-2026-64562: KVM: nVMX: Hide shadow VMCS right after VMCLEAR (bsc#1273930).
    - CVE-2026-64563: rhashtable: clear stale iter->p on table restart (bsc#1273995).
    - CVE-2026-64572: ipv4: fib: free fib_alias with kfree_rcu() on insert error path (bsc#1274014).
    - CVE-2026-64577: gtp: check skb_pull_data() return in gtp1u_send_echo_resp() (bsc#1274031).
    - CVE-2026-64581: xfrm: fix sk_dst_cache double-free in xfrm_user_policy() (bsc#1274041).
    - CVE-2026-64593: btrfs: do not trim a device which is not writeable (bsc#1274497).
    - CVE-2026-68121: pppoe: reload header pointer after dev_hard_header() (bsc#1274888).
    - CVE-2026-68136: net: gro: fix double aggregation of flush-marked skbs (bsc#1275474).
    - CVE-2026-68138: net/sched: serialize qdisc_rtab_list against concurrent get/put (bsc#1274941).
    - CVE-2026-68155: libceph: Reject monmaps advertising zero monitors (bsc#1275304).
    - CVE-2026-68158: libceph: Fix multiplication overflow in decode_new_up_state_weight() (bsc#1275307).
    - CVE-2026-68159: libceph: bound pg_{temp,upmap,upmap_items} length to CEPH_PG_MAX_SIZE (bsc#1275470).
    - CVE-2026-68160: ceph: fix pre-auth out-of-bounds read on snaptrace in ceph_handle_caps() (bsc#1275472).
    - CVE-2026-68202: ALSA: seq: close a re-opened queue timer in the destructor (bsc#1275161).
    - CVE-2026-68397: net/iucv: take a reference on the socket found in afiucv_hs_rcv() (bsc#1274898).
    - CVE-2026-68398: ppp: defer channel free to an RCU grace period to fix pppol2tp RX UAF (bsc#1274908).
    - CVE-2026-68417: RDMA/siw: publish QP after initialization (bsc#1274696).
    - CVE-2026-68426: xfrm: fix stale skb->prev after async crypto steals a GSO segment (bsc#1274705).
    - CVE-2026-68480: x86/bugs: Make Safe-RET robust against interrupt injection (bsc#1274208).
    - CVE-2026-72020: ipvs: reset full ip_vs_seq structs in ip_vs_conn_new (bsc#1275506).
    - CVE-2026-72069: locking/rt: Fix the incorrect RCU protection in rt_spin_unlock() (bsc#1275528).
    - CVE-2026-72072: net/mlx5e: macsec: fix use-after-free of metadata_dst on RX SC delete (bsc#1277155).
    - CVE-2026-72083: scsi: target: core: Fix iSCSI ISID use-after-free in REGISTER AND MOVE (bsc#1275535).
    - CVE-2026-72084: scsi: target: Bound PR-OUT TransportID parsing to the received buffer (bsc#1275540).
    - CVE-2026-72123: can: bcm: defer rx_op deallocation to workqueue to fix thrtimer UAF (bsc#1277523).
    - CVE-2026-72135: tpm: Make the TPM character devices non-seekable (bsc#1277571).
    - CVE-2026-72221: sunrpc: wait for in-flight TLS handshake callback when cancel loses race (bsc#1275665).
    - CVE-2026-72222: sunrpc: pin svc_xprt across the asynchronous TLS handshake callback (bsc#1275669).
    - CVE-2026-72251: netfilter: nf_nat_sip: reload possible stale data pointer (bsc#1275827).
    - CVE-2026-72262: ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get (bsc#1277678).
    - CVE-2026-72288: KVM: arm64: vgic: Handle race between interrupt affinity change and LPI disabling     (bsc#1275886).
    - CVE-2026-72289: KVM: arm64: vgic: Check the interrupt is still ours before migrating it (bsc#1275905).
    - CVE-2026-72317: SUNRPC: pin upper rpc_clnt across the TLS connect_worker (bsc#1275925).
    - CVE-2026-72339: qede: fix off-by-one in BD ring consumption on build_skb failure (bsc#1276006).
    - CVE-2026-72389: bridge: stp: Fix a potential use-after-free when deleting a bridge (bsc#1273869).
    - CVE-2026-74345: RDMA/siw: Fix endpoint/socket association handling (bsc#1277285).
    - CVE-2026-74377: RDMA/rxe: Copy WQE to local buffer in non-SRQ receive path (bsc#1278236).
    - CVE-2026-74378: RDMA/rxe: Fix TOCTOU heap overflow in get_srq_wqe (bsc#1278233).
    - CVE-2026-74390: RDMA/irdma: Fix out-of-bounds write in irdma_copy_user_pgaddrs (bsc#1278088).
    - CVE-2026-74394: RDMA/srpt: fix integer overflow in immediate data length check (bsc#1277408).
    - CVE-2026-74454: drm/vc4: Supply the overflow slot size in BPOS, not the whole bin BO (bsc#1277073).
    - CVE-2026-74488: wifi: mwifiex: use the subframe length when parsing A-MSDU TDLS frames (bsc#1276350).
    - CVE-2026-74496: fou: Fix use-after-free in fou_create() (bsc#1275867).
    - CVE-2026-74516: KVM: SVM: Update x2APIC MSR intercepts if AVIC is inhibited while L2 is active     (bsc#1275797).
    - CVE-2026-74518: mm/hugetlb: fix list corruption in allocate_file_region_entries() (bsc#1275798).
    - CVE-2026-74537: Bluetooth: ISO: hold sk properly in iso_conn_ready (bsc#1275687).
    - CVE-2026-74556: scsi: libiscsi_tcp: Bound SCSI Response data segment to the connection buffer     (bsc#1275696).
    - CVE-2026-74581: net: ipv6: clear suppressed fib6 rule result (bsc#1275782).
    - CVE-2026-74582: packet: use consistent hard_header_len in non-ring send paths (bsc#1275784).
    - CVE-2026-74612: veth: fix skb length accounting after XDP frag adjustment (bsc#1277505).
    - CVE-2026-74669: ipvs: clear IPv4 options after rebasing tunnel ICMP errors (bsc#1277391).
    - CVE-2026-74695: netfilter: nf_flow_table: drop existing skb dst before skb_dst_set_noref()     (bsc#1276931).
    - CVE-2026-80722: wifi: mac80211: validate individual TWT params before driver setup (bsc#1277860).

    The following non security issues were fixed:

    - ibmvnic: Only record tx completed bytes once per handler (bsc#1274620).
    - KVM: arm64: vgic: Fix IIDR revision field extracted from wrong value (git-fixes).
    - KVM: x86/mmu: WARN and clear role.invalid when creating a child shadow page (git-fixes).
    - mkspec-dtb: Move DTS prefix into package list.
    - mkspec-dtb: Move provides-obsoletes to package list.
    - mkspec-dtb: Put per-architecture package lists into a hash.
    - mkspec-dtb: re-indent.
    - net: mana: Add debug knob to skip TX timeout recovery reset (git-fixes).
    - net: mana: Add handler for sriov configure (bsc#1272756).
    - net: mana: Cap MSI-X vectors to the device MSI-X table size (git-fixes).
    - net: mana: Extend RX CQE coalescing up to 8 packets (git-fixes).
    - net: mana: Fall back to scattered pages for GDMA queues (git-fixes).
    - net: mana: force full-page RX buffers via ethtool private flag (bsc#1269792).
    - net: mana: refactor mana_get_strings() and mana_get_sset_count() to use switch (bsc#1269792).
    - net: mana: Route ring-buffer access through offset-based helpers (git-fixes).
    - net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp() (git-fixes bsc#1274550).
    - PCI: hv: Set irq_retrigger callback for the Hyper-V PCI MSI irqchip (git-fixes).
    - powerpc/pseries: lparcfg - fix kbuf[] underflow (bsc#1274753 ltc#221289 bsc#1274754 ltc#221288     bsc#1274752       ltc#221290).
    - RDMA/mana_ib: drain QP references after partial table insertion (git-fixes).
    - RDMA/mana_ib: unify QP lookup table (git-fixes).
    - scsi: storvsc: Support manual scans for all Hyper-V targets (git-fixes).
    - smb/client: handle overlapping allocated ranges in fallocate (bsc#1274902).
    - x86/bugs: Clarify that syscall hardening isn't a BHI mitigation (git-fixes).

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
333137	TencentOS Server 3: kernel (TSSA-2026:0793)	Nessus	Tencent Local Security Checks	8/6/2026	8/10/2026	critical
333145	TencentOS Server 2: kernel (TSSA-2026:0797)	Nessus	Tencent Local Security Checks	8/6/2026	8/10/2026	critical
334015	Photon OS 5.0: Linux PHSA-2026-5.0-91-0888	Nessus	PhotonOS Local Security Checks	8/10/2026	11/2/2026	critical
324734	Photon OS 4.0: Linux PHSA-2026-4.0-1048	Nessus	PhotonOS Local Security Checks	7/2/2026	11/2/2026	high
333128	TencentOS Server 4: kernel (TSSA-2026:0792)	Nessus	Tencent Local Security Checks	8/6/2026	10/27/2026	critical
359803	CentOS Linux 7 [TuxCare] Security Update: bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / etc Multiple Vulnerabilities (CENTOS7:CLSA-2026:1788170774)	Nessus	CentOS Local Security Checks	10/1/2026	10/1/2026	high
350940	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2026:4369-1)	Nessus	SuSE Local Security Checks	9/29/2026	10/5/2026	high

Detections

Analytics

Plugins Search

critical

critical

critical

high

critical

high

high