In the Linux kernel, the following vulnerability has been resolved: xfs: close crash window in attr dabtree inactivation When inactivating an inode with node-format extended attributes, xfs_attr3_node_inactive() invalidates all child leaf/node blocks via xfs_trans_binval(), but intentionally does not remove the corresponding entries from their parent node blocks. The implicit assumption is that xfs_attr_inactive() will truncate the entire attr fork to zero extents afterwards, so log recovery will never reach the root node and follow those stale pointers. However, if a log shutdown occurs after the leaf/node block cancellations commit but before the attr bmap truncation commits, this assumption breaks. Recovery replays the attr bmap intact (the inode still has attr fork extents), but suppresses replay of all cancelled leaf/node blocks, maybe leaving them as stale data on disk. On the next mount, xlog_recover_process_iunlinks() retries inactivation and attempts to read the root node via the attr bmap. If the root node was not replayed, reading the unreplayed root block triggers a metadata verification failure immediately; if it was replayed, following its child pointers to unreplayed child blocks triggers the same failure: XFS (pmem0): Metadata corruption detected at xfs_da3_node_read_verify+0x53/0x220, xfs_da3_node block 0x78 XFS (pmem0): Unmount and run xfs_repair XFS (pmem0): First 128 bytes of corrupted metadata buffer: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000060: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000070: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ XFS (pmem0): metadata I/O error in "xfs_da_read_buf+0x104/0x190" at daddr 0x78 len 8 error 117 Fix this in two places: In xfs_attr3_node_inactive(), after calling xfs_trans_binval() on a child block, immediately remove the entry that references it from the parent node in the same transaction. This eliminates the window where the parent holds a pointer to a cancelled block. Once all children are removed, the now-empty root node is converted to a leaf block within the same transaction. This node-to-leaf conversion is necessary for crash safety. If the system shutdown after the empty node is written to the log but before the second-phase bmap truncation commits, log recovery will attempt to verify the root block on disk. xfs_da3_node_verify() does not permit a node block with count == 0; such a block will fail verification and trigger a metadata corruption shutdown. on the other hand, leaf blocks are allowed to have this transient state. In xfs_attr_inactive(), split the attr fork truncation into two explicit phases. First, truncate all extents beyond the root block (the child extents whose parent references have already been removed above). Second, invalidate the root block and truncate the attr bmap to zero in a single transaction. The two operations in the second phase must be atomic: as long as the attr bmap has any non-zero length, recovery can follow it to the root block, so the root block invalidation must commit together with the bmap-to-zero truncation.

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 :

    mm: blk-cgroup: fix use-after-free in cgwb_release_workfn()(CVE-2026-31586)

    e1000/e1000e: Fix leak in DMA error cleanup(CVE-2026-43445)

    futex: Clear stale exiting pointer in futex_lock_pi() retry path(CVE-2026-31555)

    kexec: derive purgatory entry from symbol(CVE-2026-43289)

    nvme-pci: Fix race bug in nvme_poll_irqdisable()(CVE-2026-43448)

    ext4: avoid infinite loops caused by residual data(CVE-2026-31448)

    mm/userfaultfd: fix hugetlb fault mutex hash calculation(CVE-2026-31575)

    netfilter: ip6t_rt: reject oversized addrnr in rt_mt6_check()(CVE-2026-31674)

    net: skbuff: propagate shared-frag marker through frag-transfer helpers(CVE-2026-43503)

    crypto: af-alg - fix NULL pointer dereference in scatterwalk(CVE-2026-43043)

    net: bonding: fix NULL deref in bond_debug_rlb_hash_show(CVE-2026-31546)

    drm/ioc32: stop speculation on the drm_compat_ioctl path(CVE-2026-31781)

    ext4: always drain queued discard work in ext4_mb_release()(CVE-2026-43065)

    netfilter: ctnetlink: fix use-after-free in ctnetlink_dump_exp_ct()(CVE-2026-23458)

    x86/platform/uv: Handle deconfigured sockets(CVE-2026-31542)

    USB: core: Limit the length of unkillable synchronous timeouts(CVE-2026-43428)

    cifs: some missing initializations on replay(CVE-2026-31693)

    serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN(CVE-2026-23472)

    EDAC/mc: Fix error path ordering in edac_mc_alloc()(CVE-2026-31689)

    module: Fix kernel panic when a symbol st_shndx is out of bounds(CVE-2026-31521)

    can: gw: fix OOB heap access in cgw_csum_crc8_rel()(CVE-2026-31570)

    ext4: publish jinode after initialization(CVE-2026-31450)

    netfilter: xt_multiport: validate range encoding in checkentry(CVE-2026-31681)

    usb: xhci: Prevent interrupt storm on host controller error (HCE)(CVE-2026-43488)

    netfilter: nf_conntrack_sip: fix Content-Length u32 truncation in sip_help_tcp()(CVE-2026-23457)

    ext4: replace BUG_ON with proper error handling in ext4_read_inline_folio(CVE-2026-31451)

    crypto: caam - fix DMA corruption on long hmac keys(CVE-2026-43044)

    scsi: qla2xxx: Completely fix fcport double free(CVE-2026-43414)

    ext4: reject mount if bigalloc with s_first_data_block != 0(CVE-2026-31447)

    net: ipv6: flowlabel: defer exclusive option free until RCU teardown(CVE-2026-31680)

    spi: use generic driver_override infrastructure(CVE-2026-31487)

    HID: logitech-hidpp: Prevent use-after-free on force feedback initialisation failure(CVE-2026-43049)

    dmaengine: idxd: Fix not releasing workqueue on .release()(CVE-2026-43064)

    usb: gadget: f_ecm: Fix net_device lifecycle with device_move(CVE-2026-31725)

    crypto: atmel-sha204a - Fix OOM -gt;tfm_count leak(CVE-2026-31391)

    netfilter: nf_conntrack_h323: check for zero length in DecodeQ931()(CVE-2026-23455)

    scsi: hisi_sas: Fix NULL pointer exception during user_scan()(CVE-2026-43413)

    x86/apic: Disable x2apic on resume if the kernel expects so(CVE-2026-43363)

    netfilter: nf_conntrack_expect: use expect-gt;helper(CVE-2026-31414)

    nvme-pci: Fix slab-out-of-bounds in nvme_dbbuf_set(CVE-2026-43449)

    HID: core: Mitigate potential OOB by removing bogus memset()(CVE-2026-43048)

    mfd: core: Add locking around #39;mfd_of_node_list#39;(CVE-2026-43143)

    scsi: target: tcm_loop: Drain commands in target_reset handler(CVE-2026-43054)

    ACPI: processor: Fix NULL-pointer dereference in acpi_processor_errata_piix4()(CVE-2026-43313)

    netfilter: nft_ct: fix use-after-free in timeout object destroy(CVE-2026-31665)

    lib/crypto: mpi: Fix integer underflow in mpi_read_raw_from_sgl()(CVE-2026-43492)

    xfrm: clear trailing padding in build_polexpire()(CVE-2026-31664)

    perf/x86/intel/uncore: Skip discovery table for offline dies(CVE-2026-43079)

    usb: dwc3: gadget: Move vbus draw to workqueue context(CVE-2026-43170)

    net: fix fanout UAF in packet_release() via NETDEV_UP race(CVE-2026-31504)

    usb: gadget: u_ether: Fix race between gether_disconnect and eth_stop(CVE-2026-31728)

    netfilter: ip6t_eui64: reject invalid MAC header for all packets(CVE-2026-31685)

    perf/x86/intel/uncore: Fix die ID init and look up bugs(CVE-2026-43344)

    udp: Fix wildcard bind conflict check when using hash2(CVE-2026-31503)

    net/sched: sch_netem: fix out-of-bounds access in packet corruption(CVE-2026-31675)

    ext4: validate p_idx bounds in ext4_ext_correct_indexes(CVE-2026-31449)

    xfrm: prevent policy_hthresh.work from racing with netns teardown(CVE-2026-31516)

    f2fs: fix use-after-free of sbi in f2fs_compress_write_end_io()(CVE-2026-31702)

    KVM: x86: Ignore -EBUSY when checking nested events from vcpu_block()(CVE-2026-43265)

    ext4: avoid allocate block from corrupted group in ext4_mb_find_by_goal()(CVE-2026-43068)

    cifs: Fix locking usage for tcon fields(CVE-2026-43215)

    dmaengine: idxd: fix possible wrong descriptor completion in llist_abort_desc()(CVE-2026-31436)

    fbcon: check return value of con2fb_acquire_newinfo()(CVE-2026-43123)

    xfs: close crash window in attr dabtree inactivation(CVE-2026-43053)

    HID: alps: fix NULL pointer dereference in alps_raw_event()(CVE-2026-31625)

    netfilter: nf_conntrack_expect: skip expectations in other netns via proc(CVE-2026-31496)

    xfs: save ailp before dropping the AIL lock in push callbacks(CVE-2026-31454)

    KVM: SEV: Protect *all* of sev_mem_enc_register_region() with kvm-gt;lock(CVE-2026-31592)

    KVM: SEV: Drop WARN on large size for KVM_MEMORY_ENCRYPT_REG_REGION(CVE-2026-31590)

    net: ethernet: xscale: Check for PTP support properly(CVE-2026-43173)

    HID: magicmouse: Do not crash on missing msc-gt;input(CVE-2026-43140)

    smb: client: fix OOB reads parsing symlink error response(CVE-2026-31613)

    net/sched: cls_flow: fix NULL pointer dereference on shared blocks(CVE-2026-31422)

    xfrm: hold dev ref until after transport_finish NF_HOOK(CVE-2026-31663)

    bpf: Fix regsafe() for pointers to packet(CVE-2026-43030)

    xfs: avoid dereferencing log items after push callbacks(CVE-2026-31453)

    smb: client: prevent races in -gt;query_interfaces()(CVE-2026-43239)

    kprobes: avoid crash when rmmod/insmod after ftrace killed(CVE-2026-43409)

    xfs: fix undersized l_iclog_roundoff values(CVE-2026-43365)

    ixgbevf: add missing negotiate_features op to Hyper-V ops table(CVE-2026-43094)

    arm64: contpte: fix set_access_flags() no-op check for SMMU/ATS faults(CVE-2026-43486)

    arm64: Add support for TSV110 Spectre-BHB mitigation(CVE-2026-43261)

    KVM: x86: Add SRCU protection for reading PDPTRs in __get_sregs2()(CVE-2026-43214)

    can: raw: fix ro-gt;uniq use-after-free in raw_rcv()(CVE-2026-31532)

    ptrace: slightly saner #39;get_dumpable()#39; logic(CVE-2026-46333)

    openvswitch: validate MPLS set/set_masked payload length(CVE-2026-31679)

    smb: client: fix OOB read in smb2_ioctl_query_info QUERY_INFO path(CVE-2026-31708)

    af_unix: read UNIX_DIAG_VFS data under unix_state_lock(CVE-2026-31673)

    esp: fix skb leak with espintcp and async crypto(CVE-2026-31518)

    smb: client: fix off-by-8 bounds check in check_wsl_eas()(CVE-2026-31614)

    af_key: validate families in pfkey_send_migrate()(CVE-2026-31515)

    USB: usbtmc: Use usb_bulk_msg_killable() with user-specified timeouts(CVE-2026-43429)

    bpf: Fix incorrect pruning due to atomic fetch precision tracking(CVE-2026-43009)

    xfs: stop reclaim before pushing AIL during unmount(CVE-2026-31455)

    netfilter: x_tables: restrict xt_check_match/xt_check_target extensions for NFPROTO_ARP(CVE-2026-31424)

    ext4: convert inline data to extents when truncate exceeds inline size(CVE-2026-31452)

    HID: multitouch: Check to ensure report responses match the request(CVE-2026-43047)

    HID: core: clamp report_size in s32ton() to avoid undefined shift(CVE-2026-31624)

    EFI/CPER: don#39;t dump the entire memory region(CVE-2026-43171)

    pstore: ram_core: fix incorrect success return when vmap() fails(CVE-2026-43124)

    xfrm_user: fix info leak in build_report()(CVE-2026-31671)

    KVM: SVM: Set/clear CR8 write interception when AVIC is (de)activated(CVE-2026-43483)

    dcache: Limit the minimal number of bucket to two(CVE-2026-43071)

    netfilter: nf_conntrack_h323: fix OOB read in decode_int() CONS case(CVE-2026-23456)

    dm: clear cloned request bio pointer when last clone bio completes(CVE-2026-43278)

    net/tls: fix use-after-free in -EBUSY error path of tls_do_encryption(CVE-2026-31533)

    netfilter: ipset: drop logically empty buckets in mtype_del(CVE-2026-31418)

    bridge: br_nd_send: linearize skb before parsing ND options(CVE-2026-31682)

    x86/CPU: Fix FPDSS on Zen1(CVE-2026-31628)

    ext4: fix use-after-free in update_super_work when racing with umount(CVE-2026-31446)

    nvmet: move async event work off nvmet-wq(CVE-2026-31557)

    bpf: Reject sleepable kprobe_multi programs at attach time(CVE-2026-43010)

    ipv4: nexthop: allocate skb dynamically in rtm_get_nexthop()(CVE-2026-31531)

    hwmon: (pmbus/core) Protect regulator operations with mutex(CVE-2026-31486)

    iavf: fix out-of-bounds writes in iavf_get_ethtool_stats()(CVE-2026-31505)

    bpf: reject direct access to nullable PTR_TO_BUF pointers(CVE-2026-43333)

    netfilter: ctnetlink: use netlink policy range checks(CVE-2026-31495)

    nfsd: fix heap overflow in NFSv4.0 LOCK replay cache(CVE-2026-31402)

    virtio_net: Fix UAF on dst_ops when IFF_XMIT_DST_RELEASE is cleared and napi_tx is false(CVE-2026-31469)

    nvme-pci: ensure we#39;re polling a polled queue(CVE-2026-31523)

    nvdimm/bus: Fix potential use after free in asynchronous initialization(CVE-2026-31399)

    net: bonding: fix use-after-free in bond_xmit_broadcast()(CVE-2026-31419)

    mm/damon/sysfs: check contexts-gt;nr before accessing contexts_arr[0](CVE-2026-31458)

    ipv6: avoid overflows in ip6_datagram_send_ctl()(CVE-2026-31415)

    openvswitch: defer tunnel netdev_put to RCU release(CVE-2026-31678)

    mmc: vub300: fix NULL-deref on disconnect(CVE-2026-31651)

    net: openvswitch: Avoid releasing netdev before teardown completes(CVE-2026-31508)

    netfilter: nfnetlink_log: fix uninitialized padding leak in NFULA_PAYLOAD(CVE-2026-31428)

    perf: Make sure to use pmu_ctx-gt;pmu for groups(CVE-2026-31528)

    netfilter: nf_conntrack_sip: fix use of uninitialized rtp_addr in process_sdp(CVE-2026-31427)

    netfilter: nfnetlink_log: account for netlink header size(CVE-2026-31416)

    X.509: Fix out-of-bounds access when parsing extensions(CVE-2026-31430)

    HID: apple: avoid memory leak in apple_report_fixup()(CVE-2026-31520)

    driver core: platform: use generic driver_override infrastructure(CVE-2026-31527)

    crypto: af_alg - limit RX SG extraction by receive buffer budget(CVE-2026-31677)

    HID: magicmouse: avoid memory leak in magicmouse_report_fixup()(CVE-2026-31522)

    bpf, arm64: Force 8-byte alignment for JIT buffer to prevent atomic tearing(CVE-2026-23383)

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

  - xfs: close crash window in attr dabtree inactivation When inactivating an inode with node-format extended     attributes, xfs_attr3_node_inactive() invalidates all child leaf/node blocks via xfs_trans_binval(), but     intentionally does not remove the corresponding entries from their parent node blocks. The implicit     assumption is that xfs_attr_inactive() will truncate the entire attr fork to zero extents afterwards, so     log recovery will never reach the root node and follow those stale pointers. However, if a log shutdown     occurs after the leaf/node block cancellations commit but before the attr bmap truncation commits, this     assumption breaks. Recovery replays the attr bmap intact (the inode still has attr fork extents), but     suppresses replay of all cancelled leaf/node blocks, maybe leaving them as stale data on disk. On the next     mount, xlog_recover_process_iunlinks() retries inactivation and attempts to read the root node via the     attr bmap. If the root node was not replayed, reading the unreplayed root block triggers a metadata     verification failure immediately; if it was replayed, following its child pointers to unreplayed child     blocks triggers the same failure: XFS (pmem0): Metadata corruption detected at     xfs_da3_node_read_verify+0x53/0x220, xfs_da3_node block 0x78 XFS (pmem0): Unmount and run xfs_repair XFS     (pmem0): First 128 bytes of corrupted metadata buffer: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00     00 00 ................ 00000010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000030: 00 00 00 00 00 00 00     00 00 00 00 00 00 00 00 00 ................ 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00     ................ 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000060: 00     00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00000070: 00 00 00 00 00 00 00 00 00 00 00     00 00 00 00 00 ................ XFS (pmem0): metadata I/O error in xfs_da_read_buf+0x104/0x190 at daddr     0x78 len 8 error 117 Fix this in two places: In xfs_attr3_node_inactive(), after calling     xfs_trans_binval() on a child block, immediately remove the entry that references it from the parent node     in the same transaction. This eliminates the window where the parent holds a pointer to a cancelled block.
    Once all children are removed, the now-empty root node is converted to a leaf block within the same     transaction. This node-to-leaf conversion is necessary for crash safety. If the system shutdown after the     empty node is written to the log but before the second-phase bmap truncation commits, log recovery will     attempt to verify the root block on disk. xfs_da3_node_verify() does not permit a node block with count ==     0; such a block will fail verification and trigger a metadata corruption shutdown. on the other hand, leaf     blocks are allowed to have this transient state. In xfs_attr_inactive(), split the attr fork truncation     into two explicit phases. First, truncate all extents beyond the root block (the child extents whose     parent references have already been removed above). Second, invalidate the root block and truncate the     attr bmap to zero in a single transaction. The two operations in the second phase must be atomic: as long     as the attr bmap has any non-zero length, recovery can follow it to the root block, so the root block     invalidation must commit together with the bmap-to-zero truncation. (CVE-2026-43053)

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

ID	Name	Product	Family	Type	Severity
352871	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1783791447)	Nessus	Alma Linux Local Security Checks	Local	medium
348098	EulerOS Virtualization 2.11.0 : kernel (EulerOS-SA-2026-3511)	Nessus	Huawei Local Security Checks	Local	critical
348006	EulerOS Virtualization 2.11.1 : kernel (EulerOS-SA-2026-3424)	Nessus	Huawei Local Security Checks	Local	critical
333469	EulerOS 2.0 SP11 : kernel (EulerOS-SA-2026-3126)	Nessus	Huawei Local Security Checks	Local	high
333425	EulerOS 2.0 SP11 : kernel (EulerOS-SA-2026-3071)	Nessus	Huawei Local Security Checks	Local	high
332914	EulerOS 2.0 SP15 : kernel (EulerOS-SA-2026-2930)	Nessus	Huawei Local Security Checks	Local	high
332913	EulerOS 2.0 SP15 : kernel (EulerOS-SA-2026-2889)	Nessus	Huawei Local Security Checks	Local	high
329305	openSUSE 16: cluster-md-kmp-64kb / cluster-md-kmp-azure / cluster-md-kmp-default / etc (openSUSE-SU-2026:21388-1)	Nessus	SuSE Local Security Checks	Local	high
326000	SUSE SLED15 / SLES15 : Security update for the Linux Kernel (SUSE-SU-2026:2800-1)	Nessus	SuSE Local Security Checks	Local	high
311613	Linux Distros Unpatched Vulnerability : CVE-2026-43053	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-43053

medium

Tenable Plugins

medium

critical

critical

high

high

high

high

high

high

medium