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

  - In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot     reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED     indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but     device_register() was called In case of device_register() has been called we should call put_device() to     correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of     MDIOBUS_ALLOCATED state To avoid this behaviour we need to set bus->state to MDIOBUS_UNREGISTERED _before_     calling device_register(), because put_device() should be called even in case of device_register()     failure. (CVE-2021-47416)

  - An out-of-bounds read flaw was found in the Linux kernel's TeleTYpe subsystem. The issue occurs in how a     user triggers a race condition using ioctls TIOCSPTLCK and TIOCGPTPEER and TIOCSTI and TCXONC with leakage     of memory in the flush_to_ldisc function. This flaw allows a local user to crash the system or read     unauthorized random data from memory. (CVE-2022-1462)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in     isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached     with a compliant CAN ID address configuration. The provided address information consisted of CAN ID     0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the     SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)

  - In the Linux kernel, the following vulnerability has been resolved: tty: fix deadlock caused by calling     printk() under tty_port->lock pty_write() invokes kmalloc() which may invoke a normal printk() to print     failure message. This can cause a deadlock in the scenario reported by syz-bot below: CPU0 CPU1 CPU2 ----
    ---- ---- lock(console_owner); lock(&port_lock_key); lock(&port->lock); lock(&port_lock_key);
    lock(&port->lock); lock(console_owner); As commit dbdda842fe96 (printk: Add console owner and waiter     logic to load balance console writes) said, such deadlock can be prevented by using printk_deferred() in     kmalloc() (which is invoked in the section guarded by the port->lock). But there are too many printk() on     the kmalloc() path, and kmalloc() can be called from anywhere, so changing printk() to printk_deferred()     is too complicated and inelegant. Therefore, this patch chooses to specify __GFP_NOWARN to kmalloc(), so     that printk() will not be called, and this deadlock problem can be avoided. Syzbot reported the following     lockdep error: ====================================================== WARNING: possible circular locking     dependency detected 5.4.143-00237-g08ccc19a-dirty #10 Not tainted
    ------------------------------------------------------ syz-executor.4/29420 is trying to acquire lock:
    ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: console_trylock_spinning kernel/printk/printk.c:1752     [inline] ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: vprintk_emit+0x2ca/0x470     kernel/printk/printk.c:2023 but task is already holding lock: ffff8880119c9158 (&port->lock){-.-.}-{2:2},     at: pty_write+0xf4/0x1f0 drivers/tty/pty.c:120 which lock already depends on the new lock. the existing     dependency chain (in reverse order) is: -> #2 (&port->lock){-.-.}-{2:2}: __raw_spin_lock_irqsave     include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x35/0x50     kernel/locking/spinlock.c:159 tty_port_tty_get drivers/tty/tty_port.c:288 [inline] <-- lock(&port->lock);
    tty_port_default_wakeup+0x1d/0xb0 drivers/tty/tty_port.c:47 serial8250_tx_chars+0x530/0xa80     drivers/tty/serial/8250/8250_port.c:1767 serial8250_handle_irq.part.0+0x31f/0x3d0     drivers/tty/serial/8250/8250_port.c:1854 serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1827     [inline] <-- lock(&port_lock_key); serial8250_default_handle_irq+0xb2/0x220     drivers/tty/serial/8250/8250_port.c:1870 serial8250_interrupt+0xfd/0x200     drivers/tty/serial/8250/8250_core.c:126 __handle_irq_event_percpu+0x109/0xa50 kernel/irq/handle.c:156     [...] -> #1 (&port_lock_key){-.-.}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110     [inline] _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159     serial8250_console_write+0x184/0xa40 drivers/tty/serial/8250/8250_port.c:3198 <-- lock(&port_lock_key);
    call_console_drivers kernel/printk/printk.c:1819 [inline] console_unlock+0x8cb/0xd00     kernel/printk/printk.c:2504 vprintk_emit+0x1b5/0x470 kernel/printk/printk.c:2024 <-- lock(console_owner);
    vprintk_func+0x8d/0x250 kernel/printk/printk_safe.c:394 printk+0xba/0xed kernel/printk/printk.c:2084     register_console+0x8b3/0xc10 kernel/printk/printk.c:2829 univ8250_console_init+0x3a/0x46     drivers/tty/serial/8250/8250_core.c:681 console_init+0x49d/0x6d3 kernel/printk/printk.c:2915     start_kernel+0x5e9/0x879 init/main.c:713 secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:241 ->     #0 (console_owner){....}-{0:0}: [...] lock_acquire+0x127/0x340 kernel/locking/lockdep.c:4734     console_trylock_spinning kernel/printk/printk.c:1773 ---truncated--- (CVE-2022-49441)

  - In the Linux kernel, the following vulnerability has been resolved: list: fix a data-race around     ep->rdllist ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is     empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses to it need some protection to     avoid store/load-tearing. Note INIT_LIST_HEAD_RCU() already has the annotation for both prev and next.
    Commit bf3b9f6372c4 (epoll: Add busy poll support to epoll with socket fds.) added the first lockless     ep_events_available(), and commit c5a282e9635e (fs/epoll: reduce the scope of wq lock in epoll_wait())     made some ep_events_available() calls lockless and added single call under a lock, finally commit     e59d3c64cba6 (epoll: eliminate unnecessary lock for zero timeout) made the last ep_events_available()     lockless. BUG: KCSAN: data-race in do_epoll_wait / do_epoll_wait write to 0xffff88810480c7d8 of 8 bytes by     task 1802 on cpu 0: INIT_LIST_HEAD include/linux/list.h:38 [inline] list_splice_init     include/linux/list.h:492 [inline] ep_start_scan fs/eventpoll.c:622 [inline] ep_send_events     fs/eventpoll.c:1656 [inline] ep_poll fs/eventpoll.c:1806 [inline] do_epoll_wait+0x4eb/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff88810480c7d8 of 8 bytes     by task 1799 on cpu 1: list_empty_careful include/linux/list.h:329 [inline] ep_events_available     fs/eventpoll.c:381 [inline] ep_poll fs/eventpoll.c:1797 [inline] do_epoll_wait+0x279/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0xffff88810480c7d0 ->     0xffff888103c15098 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1799 Comm: syz-fuzzer Tainted:
    G W 5.17.0-rc7-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS     Google 01/01/2011 (CVE-2022-49443)

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 :

    In the Linux kernel, the following vulnerability has been resolved:ntb: intel: Fix the NULL vs IS_ERR()     bug for debugfs_create_dir()  The debugfs_create_dir() function returns error pointers. It never returns     NULL. So use IS_ERR() to check it.(CVE-2023-52917)

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

    block, bfq: fix possible UAF for bfqq-bic with merge chain(CVE-2024-47706)

    In the Linux kernel, the following vulnerability has been resolved:iommu: Return right value in     iommu_sva_bind_device()  iommu_sva_bind_device() should return either a sva bond handle or an ERR_PTR     value in error cases. Existing drivers (idxd and uacce) only check the return value with IS_ERR(). This     could potentially lead to a kernel NULL pointer dereference issue if the function returns NULL instead of     an error pointer.  In reality, this doesn't cause any problems because iommu_sva_bind_device() only     returns NULL when the kernel is not configured with CONFIG_IOMMU_SVA. In this case,     iommu_dev_enable_feature(dev, IOMMU_DEV_FEAT_SVA) will return an error, and the device drivers won't call     iommu_sva_bind_device() at all.(CVE-2024-40945)

    net: hns3: void array out of bound when loop tnl_num(CVE-2024-46833)

    KVM: arm64: Make ICC_*SGI*_EL1 undef in the absence of a vGICv3(CVE-2024-46707)

    net/mlx5: Fix bridge mode operations when there are no VFs(CVE-2024-46857)

    In the Linux kernel, the following vulnerability has been resolved:netfilter: nft_socket: fix sk refcount     leaks  We must put 'sk' reference before returning.(CVE-2024-46855)

    fsnotify: clear PARENT_WATCHED flags lazily(CVE-2024-47660)

    tcp_bpf: fix return value of tcp_bpf_sendmsg()(CVE-2024-46783)

    mlxsw: spectrum_acl_erp: Fix object nesting warning(CVE-2024-43880)

    xdp: fix invalid wait context of page_pool_destroy()(CVE-2024-43834)

    virtio_net: Fix napi_skb_cache_put warning (CVE-2024-43835)

    net: hns3: fix kernel crash problem in concurrent scenario (CVE-2024-39507)

    xfrm6: check ip6_dst_idev() return value in xfrm6_get_saddr()(CVE-2024-40959)

    In the Linux kernel, the following vulnerability has been resolved:net: ena: Add validation for completion     descriptors consistency  Validate that `first` flag is set only for the first descriptor in multi-buffer     packets. In case of an invalid descriptor, a reset will occur. A new reset reason for RX data corruption     has been added.(CVE-2024-40999)

    ipvlan: Dont Use skb-sk in ipvlan_process_v{4,6}_outbound(CVE-2024-33621)

    net: relax socket state check at accept time(CVE-2024-36484)

    net: fix information leakage in /proc/ net/ptype(CVE-2022-48757)

    net: bridge: vlan: fix memory leak in __allowed_ingress(CVE-2022-48748)

    In the Linux kernel, the following vulnerability has been resolved:USB: usbtmc: prevent kernel-usb-     infoleak  The syzbot reported a kernel-usb-infoleak in usbtmc_write, we need to clear the structure before     filling fields.(CVE-2024-47671)

    hv_netvsc: Register VF in netvsc_probe(CVE-2024-26820)

    vfs: Don't evict inode under the inode lru traversing context(CVE-2024-45003)

    perf/x86/intel: Limit the period on Haswell(CVE-2024-46848)

    ethtool: fail closed if we can't get max channel used in indirection tables(CVE-2024-46834)

    ELF: fix kernel.randomize_va_space double read(CVE-2024-46826)

    arm64: acpi: Harden get_cpu_for_acpi_id() against missing CPU entry(CVE-2024-46822)

    sched/smt: Fix unbalance sched_smt_present dec/inc(CVE-2024-44958)

    platform/x86: panasonic-laptop: Fix SINF array out of bounds accesses(CVE-2024-46859)

    rtmutex: Drop rt_mutex::wait_lock before scheduling(CVE-2024-46829)

    drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[](CVE-2024-46815)

    drm/amd/display: Check link_index before accessing dc-links[](CVE-2024-46813)

    drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links(CVE-2024-46816)

    drm/amd/display: Check msg_id before processing transcation(CVE-2024-46814)

    thunderbolt: Mark XDomain as unplugged when router is removed(CVE-2024-46702)

    nvmet-tcp: fix kernel crash if commands allocation fails(CVE-2024-46737)

    of/irq: Prevent device address out-of-bounds read in interrupt map walk(CVE-2024-46743)

    VMCI: Fix use-after-free when removing resource in vmci_resource_remove()(CVE-2024-46738)

    usb: typec: ucsi: Fix null pointer dereference in trace(CVE-2024-46719)

    pktgen: use cpus_read_lock() in pg_net_init()(CVE-2024-46681)

    ethtool: check device is present when getting link settings(CVE-2024-46679)

    apparmor: fix possible NULL pointer dereference(CVE-2024-46721)

    selinux,smack: don't bypass permissions check in inode_setsecctx hook(CVE-2024-46695)

    bonding: change ipsec_lock from spin lock to mutex(CVE-2024-46678)

    PCI: Add missing bridge lock to pci_bus_lock()(CVE-2024-46750)

    ice: Add netif_device_attach/detach into PF reset flow(CVE-2024-46770)

    md: fix deadlock between mddev_suspend and flush bio(CVE-2024-43855)

    driver: iio: add missing checks on iio_info's callback access(CVE-2024-46715)

    uio_hv_generic: Fix kernel NULL pointer dereference in hv_uio_rescind (CVE-2024-46739)

    btrfs: fix qgroup reserve leaks in cow_file_range(CVE-2024-46733)

    Squashfs: sanity check symbolic link size(CVE-2024-46744)

    Input: MT - limit max slots(CVE-2024-45008)

    drm/amd/display: Assign linear_pitch_alignment even for VM(CVE-2024-46732)

    netem: fix return value if duplicate enqueue fails(CVE-2024-45016)

    sch/ netem: fix use after free in netem_dequeue(CVE-2024-46800)

    userfaultfd: fix checks for huge PMDs(CVE-2024-46787)

    netfilter: flowtable: initialise extack before use(CVE-2024-45018)

    rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back(CVE-2024-27414)

    xsk: validate user input for XDP_{UMEM|COMPLETION}_FILL_RING(CVE-2024-35976)

    net: atlantic: eliminate double free in error handling logic(CVE-2023-52664)

    netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get()(CVE-2024-35898)

    net/ipv6: avoid possible UAF in ip6_route_mpath_notify()(CVE-2024-26852)

    udf: Avoid excessive partition lengths(CVE-2024-46777)

    scsi: aacraid: Fix double-free on probe failure(CVE-2024-46673)

    In the Linux kernel, the following vulnerability has been resolved:memcg_write_event_control(): fix a     user-triggerable oops  we are *not* guaranteed that anything past the terminating NUL is mapped (let alone     initialized with anything sane).(CVE-2024-45021)

    drm/client: fix null pointer dereference in drm_client_modeset_probe(CVE-2024-43894)

    drm/qxl: Add check for drm_cvt_mode(CVE-2024-43829)

    rtnetlink: Correct nested IFLA_VF_VLAN_LIST attribute validation(CVE-2024-36017)

    net: core: reject skb_copy(_expand) for fraglist GSO skbs(CVE-2024-36929)

    perf/aux: Fix AUX buffer serialization(CVE-2024-46713)

    fix bitmap corruption on close_range() with CLOSE_RANGE_UNSHARE(CVE-2024-45025)

    driver core: Fix uevent_show() vs driver detach race(CVE-2024-44952)

    x86/mtrr: Check if fixed MTRRs exist before saving them(CVE-2024-44948)

    bonding: fix null pointer deref in bond_ipsec_offload_ok(CVE-2024-44990)

    net: hns3: fix a deadlock problem when config TC during resetting(CVE-2024-44995)

    bonding: fix xfrm real_dev null pointer dereference(CVE-2024-44989)

    scsi: qla2xxx: Fix for possible memory corruption(CVE-2024-42288)

    xhci: Fix Panther point NULL pointer deref at full-speed re-enumeration(CVE-2024-45006)

    dmaengine: idxd: Prevent use after free on completion memory(CVE-2022-48867)

    drm/vmwgfx: Remove rcu locks from user resources(CVE-2022-48887)

    RDMA/hns: Fix soft lockup under heavy CEQE load(CVE-2024-43872)

    ipv6: prevent UAF in ip6_send_skb()(CVE-2024-44987)

    md/raid5: avoid BUG_ON() while continue reshape after reassembling(CVE-2024-43914)

    kvm: s390: Reject memory region operations for ucontrol VMs(CVE-2024-43819)

    ipv6: fix possible UAF in ip6_finish_output2()(CVE-2024-44986)

    devres: Fix memory leakage caused by driver API devm_free_percpu()(CVE-2024-43871)

    drm/vmwgfx: Fix a deadlock in dma buf fence polling(CVE-2024-43863)

    media: xc2028: avoid use-after-free in load_firmware_cb()(CVE-2024-43900)

    gpio: prevent potential speculation leaks in gpio_device_get_desc()(CVE-2024-44931)

    netns: Make get_net_ns() handle zero refcount net(CVE-2024-40958)

    tty: n_gsm: require CAP_NET_ADMIN to attach N_GSM0710 ldisc(CVE-2023-52880)

    memcg: protect concurrent access to mem_cgroup_idr(CVE-2024-43892)

    netfilter: ctnetlink: use helper function to calculate expect ID(CVE-2024-44944)

    udf: Fix bogus checksum computation in udf_rename()(CVE-2024-43845)

    scsi: qla2xxx: validate nvme_local_port correctly(CVE-2024-42286)

    padata: Fix possible divide-by-0 panic in padata_mt_helper()(CVE-2024-43889)

    serial: core: check uartclk for zero to avoid divide by zero(CVE-2024-43893)

    sctp: Fix null-ptr-deref in reuseport_add_sock()(CVE-2024-44935)

    scsi: qla2xxx: Complete command early within lock(CVE-2024-42287)

    net: bridge: mcast: wait for previous gc cycles when removing port(CVE-2024-44934)

    bpf: Add schedule points in batch ops(CVE-2022-48939)

    apparmor: Fix null pointer deref when receiving skb during sock creation(CVE-2023-52889)

    dev/parport: fix the array out-of-bounds risk(CVE-2024-42301)

    block: initialize integrity buffer to zero before writing it to media(CVE-2024-43854)

    dma: fix call order in dmam_free_coherent(CVE-2024-43856)

    tracing: Fix overflow in get_free_elt()(CVE-2024-43890)

    ipv6: prevent possible NULL deref in fib6_nh_init()(CVE-2024-40961)

    sysctl: always initialize i_uid/i_gid(CVE-2024-42312)

    kobject_uevent: Fix OOB access within zap_modalias_env()(CVE-2024-42292)

    A flaw was found in the Linux kernel's NVMe driver. This issue may allow an unauthenticated malicious     actor to send a set of crafted TCP packages when using NVMe over TCP, leading the NVMe driver to a NULL     pointer dereference in the NVMe driver and causing kernel panic and a denial of service.(CVE-2023-6356)

    A flaw was found in the Linux kernel's NVMe driver. This issue may allow an unauthenticated malicious     actor to send a set of crafted TCP packages when using NVMe over TCP, leading the NVMe driver to a NULL     pointer dereference in the NVMe driver, causing kernel panic and a denial of service.(CVE-2023-6535)

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.

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
352871	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1783791447)	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/10/22	low
348098	EulerOS Virtualization 2.11.0 : kernel (EulerOS-SA-2026-3511)	Nessus	Huawei Local Security Checks	2026/9/18	2026/10/22	critical
212622	EulerOS 2.0 SP12 : kernel (EulerOS-SA-2024-2938)	Nessus	Huawei Local Security Checks	2024/12/12	2025/9/25	high

检测

插件搜索

low

critical

high