In the Linux kernel, the following vulnerability has been resolved: tipc: fix use-after-free Read in tipc_named_reinit syzbot found the following issue on: ================================================================== BUG: KASAN: use-after-free in tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413 Read of size 8 at addr ffff88805299a000 by task kworker/1:9/23764 CPU: 1 PID: 23764 Comm: kworker/1:9 Not tainted 5.18.0-rc4-syzkaller-00878-g17d49e6e8012 #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: events tipc_net_finalize_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description.constprop.0.cold+0xeb/0x495 mm/kasan/report.c:313 print_report mm/kasan/report.c:429 [inline] kasan_report.cold+0xf4/0x1c6 mm/kasan/report.c:491 tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413 tipc_net_finalize+0x234/0x3d0 net/tipc/net.c:138 process_one_work+0x996/0x1610 kernel/workqueue.c:2289 worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e9/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298 </TASK> [...] ================================================================== In the commit d966ddcc3821 ("tipc: fix a deadlock when flushing scheduled work"), the cancel_work_sync() function just to make sure ONLY the work tipc_net_finalize_work() is executing/pending on any CPU completed before tipc namespace is destroyed through tipc_exit_net(). But this function is not guaranteed the work is the last queued. So, the destroyed instance may be accessed in the work which will try to enqueue later. In order to completely fix, we re-order the calling of cancel_work_sync() to make sure the work tipc_net_finalize_work() was last queued and it must be completed by calling cancel_work_sync().

The CentOS Linux 8.4 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.4:CLSA-2026:1782145985 advisory.

  - Linux kernel CIFS implementation, version 4.9.0 is vulnerable to a relative paths injection in directory     entry lists. (CVE-2019-10220)

  - An issue was discovered in write_tpt_entry in drivers/infiniband/hw/cxgb4/mem.c in the Linux kernel     through 5.3.2. The cxgb4 driver is directly calling dma_map_single (a DMA function) from a stack variable.
    This could allow an attacker to trigger a Denial of Service, exploitable if this driver is used on an     architecture for which this stack/DMA interaction has security relevance. (CVE-2019-17075)

  - The KVM implementation in the Linux kernel through 4.20.5 has a Use-after-Free. (CVE-2019-7221)

  - This vulnerability allows local attackers to escalate privileges on affected installations of Linux Kernel     5.14-rc3. An attacker must first obtain the ability to execute low-privileged code on the target system in     order to exploit this vulnerability. The specific flaw exists within the handling of eBPF programs. The     issue results from the lack of proper validation of user-supplied eBPF programs, which can result in a     type confusion condition. An attacker can leverage this vulnerability to escalate privileges and execute     arbitrary code in the context of the kernel. Was ZDI-CAN-14689. (CVE-2021-34866)

  - In the Linux kernel, the following vulnerability has been resolved: kyber: fix out of bounds access when     preempted __blk_mq_sched_bio_merge() gets the ctx and hctx for the current CPU and passes the hctx to
    ->bio_merge(). kyber_bio_merge() then gets the ctx for the current CPU again and uses that to get the     corresponding Kyber context in the passed hctx. However, the thread may be preempted between the two calls     to blk_mq_get_ctx(), and the ctx returned the second time may no longer correspond to the passed hctx.
    This works accidentally most of the time, but it can cause us to read garbage if the second ctx came     from an hctx with more ctx's than the first one (i.e., if ctx->index_hw[hctx->type] > hctx->nr_ctx). This     manifested as this UBSAN array index out of bounds error reported by Jakub: UBSAN: array-index-out-of-     bounds in ../kernel/locking/qspinlock.c:130:9 index 13106 is out of range for type 'long unsigned int     [128]' Call Trace: dump_stack+0xa4/0xe5 ubsan_epilogue+0x5/0x40
    __ubsan_handle_out_of_bounds.cold.13+0x2a/0x34 queued_spin_lock_slowpath+0x476/0x480     do_raw_spin_lock+0x1c2/0x1d0 kyber_bio_merge+0x112/0x180 blk_mq_submit_bio+0x1f5/0x1100     submit_bio_noacct+0x7b0/0x870 submit_bio+0xc2/0x3a0 btrfs_map_bio+0x4f0/0x9d0     btrfs_submit_data_bio+0x24e/0x310 submit_one_bio+0x7f/0xb0 submit_extent_page+0xc4/0x440
    __extent_writepage_io+0x2b8/0x5e0 __extent_writepage+0x28d/0x6e0 extent_write_cache_pages+0x4d7/0x7a0     extent_writepages+0xa2/0x110 do_writepages+0x8f/0x180 __writeback_single_inode+0x99/0x7f0     writeback_sb_inodes+0x34e/0x790 __writeback_inodes_wb+0x9e/0x120 wb_writeback+0x4d2/0x660     wb_workfn+0x64d/0xa10 process_one_work+0x53a/0xa80 worker_thread+0x69/0x5b0 kthread+0x20b/0x240     ret_from_fork+0x1f/0x30 Only Kyber uses the hctx, so fix it by passing the request_queue to ->bio_merge()     instead. BFQ and mq-deadline just use that, and Kyber can map the queues itself to avoid the mismatch.
    (CVE-2021-46984)

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 8.5 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS8.5:CLSA-2026:1782146775 advisory.

  - Linux kernel CIFS implementation, version 4.9.0 is vulnerable to a relative paths injection in directory     entry lists. (CVE-2019-10220)

  - The KVM implementation in the Linux kernel through 4.20.5 has a Use-after-Free. (CVE-2019-7221)

  - Improper input validation in BlueZ may allow an unauthenticated user to potentially enable escalation of     privilege via adjacent access. (CVE-2020-12351)

  - Improper access control in BlueZ may allow an unauthenticated user to potentially enable information     disclosure via adjacent access. (CVE-2020-12352)

  - Improper buffer restrictions in BlueZ may allow an unauthenticated user to potentially enable denial of     service via adjacent access. This affects all Linux kernel versions that support BlueZ. (CVE-2020-24490)

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

The Rocky Linux 8.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the CIQ ciqsa-2026_0871 advisory.

    This advisory aggregates security fixes for the kernel SRPM in CIQ LTS 8.6. It addresses 28 CVEs:
    CVE-2022-50022, CVE-2022-49328, CVE-2025-21919, CVE-2025-38380, CVE-2025-38086, and 23 more.

Tenable has extracted the preceding description block directly from the CIQ 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-988662 advisory.

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

    tipc: fix use-after-free Read in tipc_named_reinit

    syzbot found the following issue on:
    ==================================================================     BUG: KASAN: use-after-free in tipc_named_reinit+0x94f/0x9b0     net/tipc/name_distr.c:413     Read of size 8 at addr ffff88805299a000 by task kworker/1:9/23764

    CPU: 1 PID: 23764 Comm: kworker/1:9 Not tainted     5.18.0-rc4-syzkaller-00878-g17d49e6e8012 #0     Hardware name: Google Compute Engine/Google Compute Engine,     BIOS Google 01/01/2011     Workqueue: events tipc_net_finalize_work     Call Trace:
     <TASK>
     __dump_stack lib/dump_stack.c:88 [inline]      dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106      print_address_description.constprop.0.cold+0xeb/0x495     mm/kasan/report.c:313      print_report mm/kasan/report.c:429 [inline]      kasan_report.cold+0xf4/0x1c6 mm/kasan/report.c:491      tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413      tipc_net_finalize+0x234/0x3d0 net/tipc/net.c:138      process_one_work+0x996/0x1610 kernel/workqueue.c:2289      worker_thread+0x665/0x1080 kernel/workqueue.c:2436      kthread+0x2e9/0x3a0 kernel/kthread.c:376      ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298      </TASK>     [...]     ==================================================================

    In the commit     d966ddcc3821 (tipc: fix a deadlock when flushing scheduled work),     the cancel_work_sync() function just to make sure ONLY the work     tipc_net_finalize_work() is executing/pending on any CPU completed before     tipc namespace is destroyed through tipc_exit_net(). But this function     is not guaranteed the work is the last queued. So, the destroyed instance     may be accessed in the work which will try to enqueue later.

    In order to completely fix, we re-order the calling of cancel_work_sync()     to make sure the work tipc_net_finalize_work() was last queued and it     must be completed by calling cancel_work_sync().

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

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

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

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

    tipc: fix use-after-free Read in tipc_named_reinit

    syzbot found the following issue on:
    ==================================================================     BUG: KASAN: use-after-free in tipc_named_reinit+0x94f/0x9b0     net/tipc/name_distr.c:413     Read of size 8 at addr ffff88805299a000 by task kworker/1:9/23764

    CPU: 1 PID: 23764 Comm: kworker/1:9 Not tainted     5.18.0-rc4-syzkaller-00878-g17d49e6e8012 #0     Hardware name: Google Compute Engine/Google Compute Engine,     BIOS Google 01/01/2011     Workqueue: events tipc_net_finalize_work     Call Trace:
     <TASK>
     __dump_stack lib/dump_stack.c:88 [inline]      dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106      print_address_description.constprop.0.cold+0xeb/0x495     mm/kasan/report.c:313      print_report mm/kasan/report.c:429 [inline]      kasan_report.cold+0xf4/0x1c6 mm/kasan/report.c:491      tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413      tipc_net_finalize+0x234/0x3d0 net/tipc/net.c:138      process_one_work+0x996/0x1610 kernel/workqueue.c:2289      worker_thread+0x665/0x1080 kernel/workqueue.c:2436      kthread+0x2e9/0x3a0 kernel/kthread.c:376      ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298      </TASK>     [...]     ==================================================================

    In the commit     d966ddcc3821 (tipc: fix a deadlock when flushing scheduled work),     the cancel_work_sync() function just to make sure ONLY the work     tipc_net_finalize_work() is executing/pending on any CPU completed before     tipc namespace is destroyed through tipc_exit_net(). But this function     is not guaranteed the work is the last queued. So, the destroyed instance     may be accessed in the work which will try to enqueue later.

    In order to completely fix, we re-order the calling of cancel_work_sync()     to make sure the work tipc_net_finalize_work() was last queued and it     must be completed by calling cancel_work_sync().

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

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

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2025:9498 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * kernel: tipc: fix use-after-free Read in tipc_named_reinit (CVE-2022-49696)

    * kernel: mt76: fix use-after-free by removing a non-RCU wcid pointer (CVE-2022-49328)

    * kernel: ndisc: use RCU protection in ndisc_alloc_skb() (CVE-2025-21764)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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 remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2025:9494 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * kernel: tipc: fix use-after-free Read in tipc_named_reinit (CVE-2022-49696)

    * kernel: mt76: fix use-after-free by removing a non-RCU wcid pointer (CVE-2022-49328)

    * kernel: ndisc: use RCU protection in ndisc_alloc_skb() (CVE-2025-21764)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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 remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2025:9493 advisory.

    The kernel-rt packages provide the Real Time Linux Kernel, which enables fine-tuning for systems with     extremely high determinism requirements.

    Security Fix(es):

    * kernel: tipc: fix use-after-free Read in tipc_named_reinit (CVE-2022-49696)

    * kernel: mt76: fix use-after-free by removing a non-RCU wcid pointer (CVE-2022-49328)

    * kernel: ndisc: use RCU protection in ndisc_alloc_skb() (CVE-2025-21764)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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 remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2025:9497 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * kernel: tipc: fix use-after-free Read in tipc_named_reinit (CVE-2022-49696)

    * kernel: ndisc: use RCU protection in ndisc_alloc_skb() (CVE-2025-21764)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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.

According to the versions of the kernel packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    ipv4: Fix a data-race around sysctl_fib_sync_mem.(CVE-2022-49637)

    ima: Fix potential memory leak in ima_init_crypto().(CVE-2022-49627)

    MIPS: pgalloc: fix memory leak caused by pgd_free().(CVE-2022-49210)

    ip: Fix data-races around sysctl_ip_fwd_use_pmtu.(CVE-2022-49604)

    net: tipc: fix possible refcount leak in tipc_sk_create()(CVE-2022-49620)

    bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full(CVE-2022-49209)

    net: remove two BUG() from skb_checksum_help().(CVE-2022-49497)

    usbnet: fix memory leak in error case(CVE-2022-49657)

    ip: Fix a data-race around sysctl_ip_autobind_reuse.(CVE-2022-49600)

    cipso: Fix data-races around sysctl.(CVE-2022-49639)

    nexthop: Fix data-races around nexthop_compat_mode.(CVE-2022-49629)

    tracing/histograms: Fix memory leak problem(CVE-2022-49648)

    SUNRPC: Fix the svc_deferred_event trace class(CVE-2022-49065)

    af_unix: Fix a data-race in unix_dgram_peer_wake_me().(CVE-2022-49344)

    RDMA/cm: Fix memory leak in ib_cm_insert_listen(CVE-2022-49671)

    ip: Fix a data-race around sysctl_fwmark_reflect.(CVE-2022-49602)

    raw: Fix a data-race around sysctl_raw_l3mdev_accept.(CVE-2022-49631)

    icmp: Fix data-races around sysctl.(CVE-2022-49638)

    tty: synclink_gt: Fix null-pointer-dereference in slgt_clean().(CVE-2022-49307)

    tipc: move bc link creation back to tipc_node_create(CVE-2022-49664)

    icmp: Fix a data-race around sysctl_icmp_errors_use_inbound_ifaddr.(CVE-2022-49632)

    xprtrdma: treat all calls not a bcall when bc_serv is NULL(CVE-2022-49321)

    net: phy: micrel: Allow probing without .driver_data(CVE-2022-49472)

    tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept.(CVE-2022-49601)

    ip: Fix data-races around sysctl_ip_fwd_update_priority.(CVE-2022-49603)

    igb: fix a use-after-free issue in igb_clean_tx_ring(CVE-2022-49695)

    rxrpc: Fix listen() setting the bar too high for the prealloc rings(CVE-2022-49450)

    tty: fix deadlock caused by calling printk() under tty_port-lock(CVE-2022-49441)

    media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init(CVE-2022-49478)

    ima: Fix a potential integer overflow in ima_appraise_measurement(CVE-2022-49643)

    scsi: qla2xxx: Fix scheduling while atomic(CVE-2022-49156)

    mm/mempolicy: fix uninit-value in mpol_rebind_policy().(CVE-2022-49567)

    dm raid: fix KASAN warning in raid5_add_disks(CVE-2022-49673)

    padata: avoid UAF for reorder_work(CVE-2025-21726)

    ARM: hisi: Add missing of_node_put after of_find_compatible_node(CVE-2022-49447)

    ptp: Ensure info-enable callback is always set(CVE-2025-21814)

    bpf: Send signals asynchronously if !preemptible(CVE-2025-21728)

    ext4: don't BUG if someone dirty pages without asking ext4 first(CVE-2022-49171)

    ext4: fix ext4_mb_mark_bb() with flex_bg with fast_commit(CVE-2022-49174)

    dax: make sure inodes are flushed before destroy cache(CVE-2022-49220)

    ext4: avoid cycles in directory h-tree(CVE-2022-49343)

    ext4: fix bug_on in ext4_writepages(CVE-2022-49347)

    ext4: filter out EXT4_FC_REPLAY from on-disk superblock field s_state(CVE-2022-49348)

    ext4: fix use-after-free in ext4_rename_dir_prepare(CVE-2022-49349)

    ext4: fix warning in ext4_handle_inode_extension(CVE-2022-49352)

    PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store().(CVE-2022-49434)

    x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails(CVE-2022-49549)

    scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI(CVE-2022-49535)

    crypto: qat - add param check for RSA(CVE-2022-49563)

    dmaengine: idxd: Fix the error handling path in idxd_cdev_register()(CVE-2022-49422)

    RDMA/mlx5: Fix memory leak in error flow for subscribe event routine(CVE-2022-49206)

    bpf, arm64: Clear prog-jited_len along prog-jited(CVE-2022-49341)

    bpf: Fix UAF due to race between btf_try_get_module and load_module(CVE-2022-49236)

    bpf: Fix potential array overflow in bpf_trampoline_get_progs().(CVE-2022-49548)

    bpf: Fix insufficient bounds propagation from adjust_scalar_min_max_vals(CVE-2022-49658)

    zsmalloc: fix races between asynchronous zspage free and page migration(CVE-2022-49554)

    tpm: fix reference counting for struct tpm_chip(CVE-2022-49287)

    netfilter: nf_tables: initialize registers in nft_do_chain().(CVE-2022-49293)

    dm ioctl: prevent potential spectre v1 gadget(CVE-2022-49122)

    scsi: sd: Fix potential NULL pointer dereference(CVE-2022-49376)

    sysctl: Fix data races in proc_douintvec_minmax().(CVE-2022-49640)

    sysctl: Fix data races in proc_douintvec().(CVE-2022-49641)

    scsi: libfc: Fix use after free in fc_exch_abts_resp().(CVE-2022-49114)

    nbd: don't allow reconnect after disconnect(CVE-2025-21731)

    tpm: use try_get_ops() in tpm-space.c(CVE-2022-49286)

    cifs: potential buffer overflow in handling symlinks(CVE-2022-49058)

    extcon: Modify extcon device to be created after driver data is set(CVE-2022-49308)

    bfq: Update cgroup information before merging bio(CVE-2022-49413)

    cifs: prevent bad output lengths in smb2_ioctl_query_info().(CVE-2022-49271)

    media: cx24116: prevent overflows on SNR calculus(CVE-2024-50290)

    thermal/core: Fix memory leak in __thermal_cooling_device_register().(CVE-2022-49468)

    nbd: call genl_unregister_family() first in nbd_cleanup().(CVE-2022-49295)

    blk-mq: don't touch -tagset in blk_mq_get_sq_hctx(CVE-2022-49377)

    bfq: Make sure bfqg for which we are queueing requests is online(CVE-2022-49411)

    nvdimm: Fix firmware activation deadlock scenarios(CVE-2022-49446)

    nbd: fix io hung while disconnecting device(CVE-2022-49297)

    crypto: qat - add param check for DH(CVE-2022-49564)

    nbd: fix race between nbd_alloc_config() and module removal(CVE-2022-49300)

    net: usb: rtl8150: enable basic endpoint checking(CVE-2025-21708)

    scsi: target: tcmu: Fix possible page UAF(CVE-2022-49053)

    block: don't delete queue kobject before its children(CVE-2022-49259)

    md/bitmap: don't set sb values if can't pass sanity check(CVE-2022-49526)

    mm/slub: add missing TID updates on slab deactivation(CVE-2022-49700)

    block: Fix handling of offline queues in blk_mq_alloc_request_hctx().(CVE-2022-49720)

    ext4: fix race condition between ext4_write and ext4_convert_inline_data(CVE-2022-49414)

    ext4: fix bug_on in __es_tree_search(CVE-2022-49409)

    net: hns3: fix oops when unload drivers paralleling(CVE-2025-21802)

    irqchip/gic-v3: Fix refcount leak in gic_populate_ppi_partitions(CVE-2022-49715)

    mm/mempolicy: fix mpol_new leak in shared_policy_replace(CVE-2022-49080)

    ext4: fix bug_on ext4_mb_use_inode_pa(CVE-2022-49708)

    ext4: add reserved GDT blocks check(CVE-2022-49707)

    irqchip/gic-v3: Fix error handling in gic_populate_ppi_partitions(CVE-2022-49716)

    mm: fix unexpected zeroed page mapping with zram swap(CVE-2022-49052)

    scsi: qla2xxx: Fix crash during module load unload test(CVE-2022-49160)

    sctp: sysctl: rto_min/max: avoid using current-nsproxy(CVE-2025-21639)

    crypto: qat - fix memory leak in RSA(CVE-2022-49566)

    net/mlx5: Fix variable not being completed when function returns(CVE-2025-21662)

    scsi: storvsc: Ratelimit warning logs to prevent VM denial of service(CVE-2025-21690)

    vfio/platform: check the bounds of read/write syscalls(CVE-2025-21687)

    USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb().(CVE-2025-21689)

    ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init().(CVE-2024-53680)

    bpf: fix recursive lock when verdict program return SK_PASS(CVE-2024-56694)

    mm: zswap: properly synchronize freeing resources during CPU hotunplug(CVE-2025-21693)

    filemap: avoid truncating 64-bit offset to 32 bits(CVE-2025-21665)

    iomap: avoid avoid truncating 64-bit offset to 32 bits(CVE-2025-21667)

    fs/proc: fix softlockup in __read_vmcore (part 2).(CVE-2025-21694)

    net: hns3: don't auto enable misc vector(CVE-2025-21651)

    netfilter: conntrack: clamp maximum hashtable size to INT_MAX(CVE-2025-21648)

    net_sched: cls_flow: validate TCA_FLOW_RSHIFT attribute(CVE-2025-21653)

    netfilter: ipset: Hold module reference while requesting a module(CVE-2024-56637)

    sctp: sysctl: auth_enable: avoid using current-nsproxy(CVE-2025-21638)

    sctp: sysctl: cookie_hmac_alg: avoid using current-nsproxy(CVE-2025-21640)

    af_packet: fix vlan_get_protocol_dgram() vs MSG_PEEK(CVE-2024-57901)

    net: sched: fix ordering of qlen adjustment(CVE-2024-53164)

    af_packet: fix vlan_get_tci() vs MSG_PEEK(CVE-2024-57902)

    geneve: do not assume mac header is set in geneve_xmit_skb().(CVE-2024-56636)

    RDMA/rxe: Remove the direct link to net_device(CVE-2024-57795)

    net/ipv6: release expired exception dst cached in socket(CVE-2024-56644)

    NFSD: Prevent NULL dereference in nfsd4_process_cb_update()(CVE-2024-53217)

    iommu/arm-smmu: Defer probe of clients after smmu device bound(CVE-2024-56568)

    net/sctp: Prevent autoclose integer overflow in sctp_association_init().(CVE-2024-57938)

    dlm: fix possible lkb_resource null dereference(CVE-2024-47809)

    vsock/virtio: discard packets if the transport changes(CVE-2025-21669)

    vsock: prevent null-ptr-deref in vsock_*[has_data|has_space](CVE-2025-21666)

    netfilter: nf_tables: adapt set backend to use GC transaction API(CVE-2023-52923)

    RDMA/uverbs: Prevent integer overflow issue(CVE-2024-57890)

    pinmux: Use sequential access to access desc-pinmux data(CVE-2024-47141)

    drm/dp_mst: Ensure mst_primary pointer is valid in drm_dp_mst_handle_up_req().(CVE-2024-57798)

    selinux: ignore unknown extended permissions(CVE-2024-57931)

    eth: bnxt: always recalculate features after XDP clearing, fix null-deref(CVE-2025-21682)

    net: restrict SO_REUSEPORT to inet sockets(CVE-2024-57903)

    bpf: Fix bpf_sk_select_reuseport() memory leak(CVE-2025-21683)

    sunrpc: fix one UAF issue caused by sunrpc kernel tcp socket(CVE-2024-53168)

    net: macsec: Fix offload support for NETDEV_UNREGISTER event(CVE-2022-48720)

    netfilter: nf_set_pipapo: fix initial map fill(CVE-2024-57947)

    RDMA/hfi1: Fix use-after-free bug for mm struct(CVE-2022-49076)

    tipc: fix use-after-free Read in tipc_named_reinit(CVE-2022-49696)

    net: bonding: fix use-after-free after 802.3ad slave unbind(CVE-2022-49667)

    usbnet: fix memory leak in error case(CVE-2022-49589)

    sfc: fix use after free when disabling sriov(CVE-2022-49626)

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

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

According to the versions of the kernel packages installed, the EulerOS installation on the remote host is affected by the following vulnerabilities :

    xsk: Fix race at socket teardown(CVE-2022-49215)

    acct: perform last write from workqueue(CVE-2025-21846)

    nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags(CVE-2022-49492)

    drop_monitor: fix incorrect initialization order(CVE-2025-21862)

    iommu/arm-smmu-v3: check return value after calling platform_get_resource().(CVE-2022-49319)

    ipv4: Fix a data-race around sysctl_fib_sync_mem.(CVE-2022-49637)

    memcg: fix soft lockup in the OOM process(CVE-2024-57977)

    ima: Fix potential memory leak in ima_init_crypto().(CVE-2022-49627)

    rdma/cxgb4: Prevent potential integer overflow on 32bit(CVE-2024-57973)

    tracing: Make sure trace_printk() can output as soon as it can be used(CVE-2023-53007)

    trace_events_hist: add check for return value of 'create_hist_field'(CVE-2023-53005)

    Squashfs: fix handling and sanity checking of xattr_ids count(CVE-2023-52933)

    tcp: Fix a data-race around sysctl_tcp_probe_threshold.(CVE-2022-49595)

    tcp: Fix data-races around sysctl_tcp_min_snd_mss.(CVE-2022-49596)

    tcp: Fix data-races around sysctl_tcp_base_mss.(CVE-2022-49597)

    tcp: Fix data-races around sysctl_tcp_l3mdev_accept.(CVE-2022-49599)

    hrtimers: Force migrate away hrtimers queued after CPUHP_AP_HRTIMERS_DYING(CVE-2025-21816)

    RDMA/hfi1: Prevent use of lock before it is initialized(CVE-2022-49433)

    openvswitch: fix lockup on tx to unregistering netdev with carrier(CVE-2025-21681)

    net: hns3: add vlan list lock to protect vlan list(CVE-2022-49182)

    driver: base: fix UAF when driver_attach failed(CVE-2022-49385)

    ubi: ubi_create_volume: Fix use-after-free when volume creation failed(CVE-2022-49388)

    rtc: pcf85063: fix potential OOB write in PCF85063 NVMEM read(CVE-2024-58069)

    lz4: fix LZ4_decompress_safe_partial read out of bound(CVE-2022-49078)

    um: Fix out-of-bounds read in LDT setup(CVE-2022-49395)

    KVM: Explicitly verify target vCPU is online in kvm_get_vcpu().(CVE-2024-58083)

    ipv6: mcast: extend RCU protection in igmp6_send().(CVE-2025-21759)

    vsock: Keep the binding until socket destruction(CVE-2025-21756)

    pps: Fix a use-after-free(CVE-2024-57979)

    RDMA/hfi1: Fix use-after-free bug for mm struct(CVE-2022-49076)

    padata: fix UAF in padata_reorder(CVE-2025-21727)

    net: bonding: fix use-after-free after 802.3ad slave unbind(CVE-2022-49667)

    netfilter: nf_tables: avoid skb access on nf_stolen(CVE-2022-49622)

    srcu: Tighten cleanup_srcu_struct() GP checks(CVE-2022-49651)

    openvswitch: use RCU protection in ovs_vport_cmd_fill_info().(CVE-2025-21761)

    cgroup: Use separate src/dst nodes when preloading css_sets for migration(CVE-2022-49647)

    ice: arfs: fix use-after-free when freeing @rx_cpu_rmap(CVE-2022-49063)

    sfc: fix use after free when disabling sriov(CVE-2022-49626)

    macsec: fix UAF bug for real_dev(CVE-2022-49390)

    ndisc: extend RCU protection in ndisc_send_skb().(CVE-2025-21760)

    nfsd: release svc_expkey(CVE-2024-53216)

    nfsd: make sure exp active before svc_export_show(CVE-2024-56558)

    net: sched: Disallow replacing of child qdisc from one parent to another(CVE-2025-21700)

    tipc: fix use-after-free Read in tipc_named_reinit(CVE-2022-49696)

    arp: use RCU protection in arp_xmit().(CVE-2025-21762)

    nfsd: clear acl_access/acl_default after releasing them(CVE-2025-21796)

    ndisc: use RCU protection in ndisc_alloc_skb().(CVE-2025-21764)

    neighbour: use RCU protection in __neigh_notify().(CVE-2025-21763)

    scsi: hisi_sas: Free irq vectors in order for v3 HW(CVE-2022-49118)

    drm/plane: Move range check for format_count earlier(CVE-2021-47659)

    USB: hub: Ignore non-compliant devices with too many configs or interfaces(CVE-2025-21776)

    MIPS: pgalloc: fix memory leak caused by pgd_free().(CVE-2022-49210)

    bpf: avoid holding freeze_mutex during mmap operation(CVE-2025-21853)

    ip: Fix data-races around sysctl_ip_fwd_use_pmtu.(CVE-2022-49604)

    linux/dim: Fix divide by 0 in RDMA DIM(CVE-2022-49670)

    HID: multitouch: Add NULL check in mt_input_configured(CVE-2024-58020)

    nfp: bpf: Add check for nfp_app_ctrl_msg_alloc().(CVE-2025-21848)

    net: tipc: fix possible refcount leak in tipc_sk_create()(CVE-2022-49620)

    bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full(CVE-2022-49209)

    net: remove two BUG() from skb_checksum_help().(CVE-2022-49497)

    usbnet: fix memory leak in error case(CVE-2022-49657)

    usbnet: fix memory leak in error case(CVE-2022-49589)

    ip: Fix a data-race around sysctl_ip_autobind_reuse.(CVE-2022-49600)

    cipso: Fix data-races around sysctl.(CVE-2022-49639)

    KVM: x86: Reject Hyper-V's SEND_IPI hypercalls if local APIC isn't in-kernel(CVE-2025-21779)

    nexthop: Fix data-races around nexthop_compat_mode.(CVE-2022-49629)

    tracing/histograms: Fix memory leak problem(CVE-2022-49648)

    SUNRPC: Fix the svc_deferred_event trace class(CVE-2022-49065)

    af_unix: Fix a data-race in unix_dgram_peer_wake_me().(CVE-2022-49344)

    usb: xhci: Fix NULL pointer dereference on certain command aborts(CVE-2024-57981)

    ceph: fix memory leak in ceph_readdir when note_last_dentry returns error(CVE-2022-49107)

    NFSv4.2: fix reference count leaks in _nfs42_proc_copy_notify().(CVE-2022-49103)

    io_uring: fix memory leak of uid in files registration(CVE-2022-49144)

    RDMA/cm: Fix memory leak in ib_cm_insert_listen(CVE-2022-49671)

    ip: Fix a data-race around sysctl_fwmark_reflect.(CVE-2022-49602)

    hwrng: cavium - fix NULL but dereferenced coccicheck error(CVE-2022-49177)

    mlxsw: spectrum: Guard against invalid local ports(CVE-2022-49134)

    raw: Fix a data-race around sysctl_raw_l3mdev_accept.(CVE-2022-49631)

    icmp: Fix data-races around sysctl.(CVE-2022-49638)

    tty: synclink_gt: Fix null-pointer-dereference in slgt_clean().(CVE-2022-49307)

    iommu/arm-smmu: fix possible null-ptr-deref in arm_smmu_device_probe().(CVE-2022-49323)

    drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes(CVE-2022-49532)

    scsi: qla2xxx: Suppress a kernel complaint in qla_create_qpair().(CVE-2022-49155)

    tipc: move bc link creation back to tipc_node_create(CVE-2022-49664)

    NFSv4: Don't hold the layoutget locks across multiple RPC calls(CVE-2022-49316)

    icmp: Fix a data-race around sysctl_icmp_errors_use_inbound_ifaddr.(CVE-2022-49632)

    xprtrdma: treat all calls not a bcall when bc_serv is NULL(CVE-2022-49321)

    net: phy: micrel: Allow probing without .driver_data(CVE-2022-49472)

    tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept.(CVE-2022-49601)

    kernel/resource: fix kfree() of bootmem memory again(CVE-2022-49190)

    vrf: use RCU protection in l3mdev_l3_out().(CVE-2025-21791)

    tcp: Fix a data-race around sysctl_tcp_ecn_fallback.(CVE-2022-49630)

    i2c: dev: check return value when calling dev_set_name().(CVE-2022-49046)

    list: fix a data-race around ep-rdllist(CVE-2022-49443)

    perf/core: Fix data race between perf_event_set_output() and perf_mmap_close()(CVE-2022-49607)

    drm/amd/display: Fix memory leak(CVE-2022-49135)

    ip: Fix data-races around sysctl_ip_fwd_update_priority.(CVE-2022-49603)

    media: uvcvideo: Fix double free in error path(CVE-2024-57980)

    io_uring: prevent opcode speculation(CVE-2025-21863)

    geneve: Fix use-after-free in geneve_find_dev().(CVE-2025-21858)

    arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array(CVE-2025-21785)

    igb: fix a use-after-free issue in igb_clean_tx_ring(CVE-2022-49695)

    rxrpc: Fix listen() setting the bar too high for the prealloc rings(CVE-2022-49450)

    tty: fix deadlock caused by calling printk() under tty_port-lock(CVE-2022-49441)

    media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init(CVE-2022-49478)

    ima: Fix a potential integer overflow in ima_appraise_measurement(CVE-2022-49643)

    scsi: qla2xxx: Fix scheduling while atomic(CVE-2022-49156)

    scsi: lpfc: Fix SCSI I/O completion and abort handler deadlock(CVE-2022-49536)

    mm/mempolicy: fix uninit-value in mpol_rebind_policy().(CVE-2022-49567)

    KVM: VMX: Prevent RSB underflow before vmenter(CVE-2022-49610)

    dm raid: fix KASAN warning in raid5_add_disks(CVE-2022-49673)

    tpm: Change to kvalloc() in eventlog/acpi.c(CVE-2024-58005)

    media: uvcvideo: Remove dangling pointers(CVE-2024-58002)

    padata: avoid UAF for reorder_work(CVE-2025-21726)

    ARM: hisi: Add missing of_node_put after of_find_compatible_node(CVE-2022-49447)

    ptp: Ensure info-enable callback is always set(CVE-2025-21814)

    bpf: Send signals asynchronously if !preemptible(CVE-2025-21728)

    ext4: don't BUG if someone dirty pages without asking ext4 first(CVE-2022-49171)

    ext4: fix ext4_mb_mark_bb() with flex_bg with fast_commit(CVE-2022-49174)

    dax: make sure inodes are flushed before destroy cache(CVE-2022-49220)

    ext4: avoid cycles in directory h-tree(CVE-2022-49343)

    ext4: fix bug_on in ext4_writepages(CVE-2022-49347)

    ext4: filter out EXT4_FC_REPLAY from on-disk superblock field s_state(CVE-2022-49348)

    ext4: fix use-after-free in ext4_rename_dir_prepare(CVE-2022-49349)

    ext4: fix warning in ext4_handle_inode_extension(CVE-2022-49352)

    PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store().(CVE-2022-49434)

    x86/MCE/AMD: Fix memory leak when threshold_create_bank() fails(CVE-2022-49549)

    scsi: lpfc: Fix null pointer dereference after failing to issue FLOGI and PLOGI(CVE-2022-49535)

    crypto: qat - add param check for RSA(CVE-2022-49563)

    dmaengine: idxd: Fix the error handling path in idxd_cdev_register()(CVE-2022-49422)

    RDMA/mlx5: Fix memory leak in error flow for subscribe event routine(CVE-2022-49206)

    bpf, arm64: Clear prog-jited_len along prog-jited(CVE-2022-49341)

    bpf: Fix UAF due to race between btf_try_get_module and load_module(CVE-2022-49236)

    bpf: Fix potential array overflow in bpf_trampoline_get_progs().(CVE-2022-49548)

    bpf: Fix insufficient bounds propagation from adjust_scalar_min_max_vals(CVE-2022-49658)

    zsmalloc: fix races between asynchronous zspage free and page migration(CVE-2022-49554)

    tpm: fix reference counting for struct tpm_chip(CVE-2022-49287)

    netfilter: nf_tables: initialize registers in nft_do_chain().(CVE-2022-49293)

    dm ioctl: prevent potential spectre v1 gadget(CVE-2022-49122)

    scsi: sd: Fix potential NULL pointer dereference(CVE-2022-49376)

    sysctl: Fix data races in proc_douintvec_minmax().(CVE-2022-49640)

    sysctl: Fix data races in proc_douintvec().(CVE-2022-49641)

    scsi: libfc: Fix use after free in fc_exch_abts_resp().(CVE-2022-49114)

    nbd: don't allow reconnect after disconnect(CVE-2025-21731)

    tpm: use try_get_ops() in tpm-space.c(CVE-2022-49286)

    cifs: potential buffer overflow in handling symlinks(CVE-2022-49058)

    extcon: Modify extcon device to be created after driver data is set(CVE-2022-49308)

    bfq: Update cgroup information before merging bio(CVE-2022-49413)

    cifs: prevent bad output lengths in smb2_ioctl_query_info().(CVE-2022-49271)

    media: cx24116: prevent overflows on SNR calculus(CVE-2024-50290)

    thermal/core: Fix memory leak in __thermal_cooling_device_register().(CVE-2022-49468)

    nbd: call genl_unregister_family() first in nbd_cleanup().(CVE-2022-49295)

    blk-mq: don't touch -tagset in blk_mq_get_sq_hctx(CVE-2022-49377)

    bfq: Make sure bfqg for which we are queueing requests is online(CVE-2022-49411)

    nvdimm: Fix firmware activation deadlock scenarios(CVE-2022-49446)

    crypto: qat - add param check for DH(CVE-2022-49564)

    nbd: fix race between nbd_alloc_config() and module removal(CVE-2022-49300)

    nbd: fix io hung while disconnecting device(CVE-2022-49297)

    net: usb: rtl8150: enable basic endpoint checking(CVE-2025-21708)

    scsi: target: tcmu: Fix possible page UAF(CVE-2022-49053)

    block: don't delete queue kobject before its children(CVE-2022-49259)

    md/bitmap: don't set sb values if can't pass sanity check(CVE-2022-49526)

    mm/slub: add missing TID updates on slab deactivation(CVE-2022-49700)

    block: Fix handling of offline queues in blk_mq_alloc_request_hctx().(CVE-2022-49720)

    ext4: fix race condition between ext4_write and ext4_convert_inline_data(CVE-2022-49414)

    ext4: fix bug_on in __es_tree_search(CVE-2022-49409)

    net: hns3: fix oops when unload drivers paralleling(CVE-2025-21802)

    irqchip/gic-v3: Fix refcount leak in gic_populate_ppi_partitions(CVE-2022-49715)

    mm/mempolicy: fix mpol_new leak in shared_policy_replace(CVE-2022-49080)

    ext4: fix bug_on ext4_mb_use_inode_pa(CVE-2022-49708)

    ext4: add reserved GDT blocks check(CVE-2022-49707)

    irqchip/gic-v3: Fix error handling in gic_populate_ppi_partitions(CVE-2022-49716)

    mm: fix unexpected zeroed page mapping with zram swap(CVE-2022-49052)

    scsi: qla2xxx: Fix crash during module load unload test(CVE-2022-49160)

    sctp: sysctl: rto_min/max: avoid using current-nsproxy(CVE-2025-21639)

    crypto: qat - fix memory leak in RSA(CVE-2022-49566)

    net/mlx5: Fix variable not being completed when function returns(CVE-2025-21662)

    scsi: storvsc: Ratelimit warning logs to prevent VM denial of service(CVE-2025-21690)

    vfio/platform: check the bounds of read/write syscalls(CVE-2025-21687)

    USB: serial: quatech2: fix null-ptr-deref in qt2_process_read_urb().(CVE-2025-21689)

    ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init().(CVE-2024-53680)

    bpf: fix recursive lock when verdict program return SK_PASS(CVE-2024-56694)

    mm: zswap: properly synchronize freeing resources during CPU hotunplug(CVE-2025-21693)

    ovl: fix UAF in ovl_dentry_update_reval by moving dput() in ovl_link_up(CVE-2025-21887)

    net: asix: add proper error handling of usb read errors(CVE-2022-49226)

    mm/khugepaged: fix -anon_vma race(CVE-2023-52935)

    HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections(CVE-2024-57986)

    proc: fix UAF in proc_get_inode().(CVE-2025-21999)

    smb: client: Add check for next_buffer in receive_encrypted_standard().(CVE-2025-21844)

    exec: don't WARN for racy path_noexec check(CVE-2024-50010)

    kthread: unpark only parked kthread(CVE-2024-50019)

Tenable has extracted the preceding description block directly from the EulerOS kernel 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.291-207.406. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.4-2025-098 advisory.

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

    macsec: fix UAF bug for real_dev (CVE-2022-49390)

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

    tipc: fix use-after-free Read in tipc_named_reinit (CVE-2022-49696)

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

    block: Fix handling of offline queues in blk_mq_alloc_request_hctx() (CVE-2022-49720)

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

    tcp/dccp: Don't use timer_pending() in reqsk_queue_unlink(). (CVE-2024-50154)

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

    padata: fix UAF in padata_reorder (CVE-2025-21727)

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

    udp: Fix memory accounting leak. (CVE-2025-22058)

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 Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - tipc: fix use-after-free Read in tipc_named_reinit syzbot found the following issue on:
    ================================================================== BUG: KASAN: use-after-free in     tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413 Read of size 8 at addr ffff88805299a000 by task     kworker/1:9/23764 CPU: 1 PID: 23764 Comm: kworker/1:9 Not tainted 5.18.0-rc4-syzkaller-00878-g17d49e6e8012     #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: events     tipc_net_finalize_work Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline]     dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106 print_address_description.constprop.0.cold+0xeb/0x495     mm/kasan/report.c:313 print_report mm/kasan/report.c:429 [inline] kasan_report.cold+0xf4/0x1c6     mm/kasan/report.c:491 tipc_named_reinit+0x94f/0x9b0 net/tipc/name_distr.c:413     tipc_net_finalize+0x234/0x3d0 net/tipc/net.c:138 process_one_work+0x996/0x1610 kernel/workqueue.c:2289     worker_thread+0x665/0x1080 kernel/workqueue.c:2436 kthread+0x2e9/0x3a0 kernel/kthread.c:376     ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298 </TASK> [...]     ================================================================== In the commit d966ddcc3821 (tipc: fix     a deadlock when flushing scheduled work), the cancel_work_sync() function just to make sure ONLY the work     tipc_net_finalize_work() is executing/pending on any CPU completed before tipc namespace is destroyed     through tipc_exit_net(). But this function is not guaranteed the work is the last queued. So, the     destroyed instance may be accessed in the work which will try to enqueue later. In order to completely     fix, we re-order the calling of cancel_work_sync() to make sure the work tipc_net_finalize_work() was last     queued and it must be completed by calling cancel_work_sync(). (CVE-2022-49696)

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

The version of kernel installed on the remote host is prior to 5.10.130-118.517. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.10-2022-018 advisory.

    An out-of-bounds write flaw was found in the Linux kernel's framebuffer-based console driver     functionality in the way a user triggers ioctl FBIOPUT_VSCREENINFO with malicious data. This flaw allows a     local user to crash or potentially escalate their privileges on the system. (CVE-2021-33655)

    There are use-after-free vulnerabilities caused by timer handler in net/rose/rose_timer.c of linux that     allow attackers to crash linux kernel without any privileges. (CVE-2022-2318)

    Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text     explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device     frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740).
    Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to     unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend     (CVE-2022-33741, CVE-2022-33742). (CVE-2022-26365)

    Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text     explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device     frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740).
    Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to     unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend     (CVE-2022-33741, CVE-2022-33742). (CVE-2022-33740)

    Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text     explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device     frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740).
    Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to     unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend     (CVE-2022-33741, CVE-2022-33742). (CVE-2022-33741)

    Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text     explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device     frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740).
    Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to     unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend     (CVE-2022-33741, CVE-2022-33742). (CVE-2022-33742)

    network backend may cause Linux netfront to use freed SKBs While adding logic to support XDP (eXpress Data     Path), a code label was moved in a way allowing for SKBs having references (pointers) retained for further     processing to nevertheless be freed. (CVE-2022-33743)

    Arm guests can cause Dom0 DoS via PV devices When mapping pages of guests on Arm, dom0 is using an rbtree     to keep track of the foreign mappings. Updating of that rbtree is not always done completely with the     related lock held, resulting in a small race window, which can be used by unprivileged guests via PV     devices to cause inconsistencies of the rbtree. These inconsistencies can lead to Denial of Service (DoS)     of dom0, e.g. by causing crashes or the inability to perform further mappings of other guests' memory     pages. (CVE-2022-33744)

    A heap buffer overflow flaw was found in the Linux kernel's Netfilter subsystem in the way a user provides     incorrect input of the NFT_DATA_VERDICT type. This flaw allows a local user to crash or potentially     escalate their privileges on the system. (CVE-2022-34918)

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

    usbnet: fix memory leak in error case (CVE-2022-49657)

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

    bpf: Fix insufficient bounds propagation from adjust_scalar_min_max_vals (CVE-2022-49658)

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

    tunnels: do not assume mac header is set in skb_tunnel_check_pmtu() (CVE-2022-49663)

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

    tipc: move bc link creation back to tipc_node_create (CVE-2022-49664)

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

    net: bonding: fix use-after-free after 802.3ad slave unbind (CVE-2022-49667)

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

    linux/dim: Fix divide by 0 in RDMA DIM (CVE-2022-49670)

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

    RDMA/cm: Fix memory leak in ib_cm_insert_listen (CVE-2022-49671)

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

    net: tun: unlink NAPI from device on destruction (CVE-2022-49672)

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

    dm raid: fix KASAN warning in raid5_add_disks (CVE-2022-49673)

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

    dm raid: fix accesses beyond end of raid member array (CVE-2022-49674)

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

    tick/nohz: unexport __init-annotated tick_nohz_full_setup() (CVE-2022-49675)

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

    virtio_net: fix xdp_rxq_info bug after suspend/resume (CVE-2022-49687)

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

    afs: Fix dynamic root getattr (CVE-2022-49688)

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

    erspan: do not assume transport header is always set (CVE-2022-49691)

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

    igb: fix a use-after-free issue in igb_clean_tx_ring (CVE-2022-49695)

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

    tipc: fix use-after-free Read in tipc_named_reinit (CVE-2022-49696)

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

    bpf: Fix request_sock leak in sk lookup helpers (CVE-2022-49697)

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

    netfilter: use get_random_u32 instead of prandom (CVE-2022-49698)

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

    mm/slub: add missing TID updates on slab deactivation (CVE-2022-49700)

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.15.54-25.126. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2KERNEL-5.15-2022-005 advisory.

    Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text     explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device     frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740).
    Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to     unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend     (CVE-2022-33741, CVE-2022-33742). (CVE-2022-26365)

    Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text     explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device     frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740).
    Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to     unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend     (CVE-2022-33741, CVE-2022-33742). (CVE-2022-33740)

    Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text     explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device     frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740).
    Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to     unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend     (CVE-2022-33741, CVE-2022-33742). (CVE-2022-33741)

    Linux disk/nic frontends data leaks T[his CNA information record relates to multiple CVEs; the text     explains which aspects/vulnerabilities correspond to which CVE.] Linux Block and Network PV device     frontends don't zero memory regions before sharing them with the backend (CVE-2022-26365, CVE-2022-33740).
    Additionally the granularity of the grant table doesn't allow sharing less than a 4K page, leading to     unrelated data residing in the same 4K page as data shared with a backend being accessible by such backend     (CVE-2022-33741, CVE-2022-33742). (CVE-2022-33742)

    network backend may cause Linux netfront to use freed SKBs While adding logic to support XDP (eXpress Data     Path), a code label was moved in a way allowing for SKBs having references (pointers) retained for further     processing to nevertheless be freed. (CVE-2022-33743)

    A heap buffer overflow flaw was found in the Linux kernel's Netfilter subsystem in the way a user provides     incorrect input of the NFT_DATA_VERDICT type. This flaw allows a local user to crash or potentially     escalate their privileges on the system. (CVE-2022-34918)

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

    scsi: qla2xxx: Fix crash during module load unload test (CVE-2022-49160)

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

    block: fix rq-qos breakage from skipping rq_qos_done_bio() (CVE-2022-49266)

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

    module: fix [e_shstrndx].sh_size=0 OOB access (CVE-2022-49444)

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

    bpf: Fix insufficient bounds propagation from adjust_scalar_min_max_vals (CVE-2022-49658)

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

    ipv6: fix lockdep splat in in6_dump_addrs() (CVE-2022-49662)

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

    tunnels: do not assume mac header is set in skb_tunnel_check_pmtu() (CVE-2022-49663)

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

    tipc: move bc link creation back to tipc_node_create (CVE-2022-49664)

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

    net: bonding: fix use-after-free after 802.3ad slave unbind (CVE-2022-49667)

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

    linux/dim: Fix divide by 0 in RDMA DIM (CVE-2022-49670)

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

    RDMA/cm: Fix memory leak in ib_cm_insert_listen (CVE-2022-49671)

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

    net: tun: unlink NAPI from device on destruction (CVE-2022-49672)

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

    dm raid: fix KASAN warning in raid5_add_disks (CVE-2022-49673)

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

    dm raid: fix accesses beyond end of raid member array (CVE-2022-49674)

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

    tick/nohz: unexport __init-annotated tick_nohz_full_setup() (CVE-2022-49675)

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

    virtio_net: fix xdp_rxq_info bug after suspend/resume (CVE-2022-49687)

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

    afs: Fix dynamic root getattr (CVE-2022-49688)

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

    erspan: do not assume transport header is always set (CVE-2022-49691)

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

    igb: fix a use-after-free issue in igb_clean_tx_ring (CVE-2022-49695)

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

    tipc: fix use-after-free Read in tipc_named_reinit (CVE-2022-49696)

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

    bpf: Fix request_sock leak in sk lookup helpers (CVE-2022-49697)

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

    netfilter: use get_random_u32 instead of prandom (CVE-2022-49698)

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

    mm/slub: add missing TID updates on slab deactivation (CVE-2022-49700)

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

    btrfs: fix hang during unmount when block group reclaim task is running (CVE-2022-49702)

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

    sock: redo the psock vs ULP protection check (CVE-2022-49732)

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.

An update of the linux package has been released.

ID	Name	Product	Family	Type	Severity
360976	CentOS Linux 8.4 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS8.4:CLSA-2026:1782145985)	Nessus	CentOS Local Security Checks	Local	high
360215	CentOS Linux 8.5 [TuxCare] Security Update: bpftool / kernel / kernel-core / kernel-cross-headers / etc Multiple Vulnerabilities (CENTOS8.5:CLSA-2026:1782146775)	Nessus	CentOS Local Security Checks	Local	high
355129	Rocky Linux 8.6 [CIQ] Security Update: bpftool / bpftool-debuginfo / kernel / kernel-abi-stablelists / etc Multiple Vulnerabilities (ciqsa-2026_0871)	Nessus	Rocky Linux Local Security Checks	Local	high
273948	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988662)	Nessus	Unity Linux Local Security Checks	Local	high
268430	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-986737)	Nessus	Unity Linux Local Security Checks	Local	high
240473	RHEL 8 : kernel (RHSA-2025:9498)	Nessus	Red Hat Local Security Checks	Local	high
240432	RHEL 9 : kernel (RHSA-2025:9494)	Nessus	Red Hat Local Security Checks	Local	high
240429	RHEL 9 : kernel-rt (RHSA-2025:9493)	Nessus	Red Hat Local Security Checks	Local	high
240423	RHEL 8 : kernel (RHSA-2025:9497)	Nessus	Red Hat Local Security Checks	Local	high
238226	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-1635)	Nessus	Huawei Local Security Checks	Local	high
238210	EulerOS 2.0 SP13 : kernel (EulerOS-SA-2025-1618)	Nessus	Huawei Local Security Checks	Local	high
238183	EulerOS 2.0 SP12 : kernel (EulerOS-SA-2025-1590)	Nessus	Huawei Local Security Checks	Local	high
238182	EulerOS 2.0 SP12 : kernel (EulerOS-SA-2025-1589)	Nessus	Huawei Local Security Checks	Local	high
238056	Amazon Linux 2 : kernel (ALASKERNEL-5.4-2025-098)	Nessus	Amazon Linux Local Security Checks	Local	high
227381	Linux Distros Unpatched Vulnerability : CVE-2022-49696	Nessus	Misc.	Local	high
163382	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2022-018)	Nessus	Amazon Linux Local Security Checks	Local	high
163352	Amazon Linux 2 : kernel (ALASKERNEL-5.15-2022-005)	Nessus	Amazon Linux Local Security Checks	Local	high
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2022-49696

high

Tenable Plugins

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high