An update of the linux package has been released.

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

  - In the Linux kernel, the following vulnerability has been resolved: ftrace: Clean up hash direct_functions     on register failures We see the following GPF when register_ftrace_direct fails: [ ] general protection     fault, probably for non-canonical address \ 0x200000000000010: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC PTI     [...] [ ] RIP: 0010:ftrace_find_rec_direct+0x53/0x70 [ ] Code: 48 c1 e0 03 48 03 42 08 48 8b 10 31 c0 48     85 d2 74 [...] [ ] RSP: 0018:ffffc9000138bc10 EFLAGS: 00010206 [ ] RAX: 0000000000000000 RBX:
    ffffffff813e0df0 RCX: 000000000000003b [ ] RDX: 0200000000000000 RSI: 000000000000000c RDI:
    ffffffff813e0df0 [ ] RBP: ffffffffa00a3000 R08: ffffffff81180ce0 R09: 0000000000000001 [ ] R10:
    ffffc9000138bc18 R11: 0000000000000001 R12: ffffffff813e0df0 [ ] R13: ffffffff813e0df0 R14:
    ffff888171b56400 R15: 0000000000000000 [ ] FS: 00007fa9420c7780(0000) GS:ffff888ff6a00000(0000)     knlGS:000000000 [ ] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ ] CR2: 000000000770d000 CR3:
    0000000107d50003 CR4: 0000000000370ee0 [ ] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
    0000000000000000 [ ] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ ] Call Trace: [ ]     <TASK> [ ] register_ftrace_direct+0x54/0x290 [ ] ? render_sigset_t+0xa0/0xa0 [ ]     bpf_trampoline_update+0x3f5/0x4a0 [ ] ? 0xffffffffa00a3000 [ ] bpf_trampoline_link_prog+0xa9/0x140 [ ]     bpf_tracing_prog_attach+0x1dc/0x450 [ ] bpf_raw_tracepoint_open+0x9a/0x1e0 [ ] ? find_held_lock+0x2d/0x90     [ ] ? lock_release+0x150/0x430 [ ] __sys_bpf+0xbd6/0x2700 [ ] ? lock_is_held_type+0xd8/0x130 [ ]
    __x64_sys_bpf+0x1c/0x20 [ ] do_syscall_64+0x3a/0x80 [ ] entry_SYSCALL_64_after_hwframe+0x44/0xae [ ] RIP:
    0033:0x7fa9421defa9 [ ] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 9 f8 [...] [ ] RSP:
    002b:00007ffed743bd78 EFLAGS: 00000246 ORIG_RAX: 0000000000000141 [ ] RAX: ffffffffffffffda RBX:
    00000000069d2480 RCX: 00007fa9421defa9 [ ] RDX: 0000000000000078 RSI: 00007ffed743bd80 RDI:
    0000000000000011 [ ] RBP: 00007ffed743be00 R08: 0000000000bb7270 R09: 0000000000000000 [ ] R10:
    00000000069da210 R11: 0000000000000246 R12: 0000000000000001 [ ] R13: 00007ffed743c4b0 R14:
    00000000069d2480 R15: 0000000000000001 [ ] </TASK> [ ] Modules linked in: klp_vm(OK) [ ] ---[ end trace     0000000000000000 ]--- One way to trigger this is: 1. load a livepatch that patches kernel function xxx; 2.
    run bpftrace -e 'kfunc:xxx {}', this will fail (expected for now); 3. repeat #2 => gpf. This is because     the entry is added to direct_functions, but not removed. Fix this by remove the entry from     direct_functions when register_ftrace_direct fails. Also remove the last trailing space from ftrace.c, so     we don't have to worry about it anymore. (CVE-2022-49402)

  - In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3: Fix refcount leak in     gic_populate_ppi_partitions of_find_node_by_phandle() returns a node pointer with refcount incremented, we     should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak.
    (CVE-2022-49715)

  - In the Linux kernel, the following vulnerability has been resolved: cpufreq: CPPC: Add u64 casts to avoid     overflowing The fields of the _CPC object are unsigned 32-bits values. To avoid overflows while using
    _CPC's values, add 'u64' casts. (CVE-2022-49750)

  - In the Linux kernel, the following vulnerability has been resolved: net: stream: purge sk_error_queue in     sk_stream_kill_queues() Changheon Lee reported TCP socket leaks, with a nice repro. It seems we leak TCP     sockets with the following sequence: 1) SOF_TIMESTAMPING_TX_ACK is enabled on the socket. Each ACK will     cook an skb put in error queue, from __skb_tstamp_tx(). __skb_tstamp_tx() is using skb_clone(), unless     SOF_TIMESTAMPING_OPT_TSONLY was also requested. 2) If the application is also using MSG_ZEROCOPY, then we     put in the error queue cloned skbs that had a struct ubuf_info attached to them. Whenever an struct     ubuf_info is allocated, sock_zerocopy_alloc() does a sock_hold(). As long as the cloned skbs are still in     sk_error_queue, socket refcount is kept elevated. 3) Application closes the socket, while error queue is     not empty. Since tcp_close() no longer purges the socket error queue, we might end up with a TCP socket     with at least one skb in error queue keeping the socket alive forever. This bug can be (ab)used to consume     all kernel memory and freeze the host. We need to purge the error queue, with proper synchronization     against concurrent writers. (CVE-2022-50838)

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Add preempt_count_{sub,add} into     btf id deny list The recursion check in __bpf_prog_enter* and __bpf_prog_exit* leave     preempt_count_{sub,add} unprotected. When attaching trampoline to them we get panic as follows, [     867.843050] BUG: TASK stack guard page was hit at 0000000009d325cf (stack is     0000000046a46a15..00000000537e7b28) [ 867.843064] stack guard page: 0000 [#1] PREEMPT SMP NOPTI [     867.843067] CPU: 8 PID: 11009 Comm: trace Kdump: loaded Not tainted 6.2.0+ #4 [ 867.843100] Call Trace: [     867.843101] <TASK> [ 867.843104] asm_exc_int3+0x3a/0x40 [ 867.843108] RIP: 0010:preempt_count_sub+0x1/0xa0     [ 867.843135] __bpf_prog_enter_recur+0x17/0x90 [ 867.843148] bpf_trampoline_6442468108_0+0x2e/0x1000 [     867.843154] ? preempt_count_sub+0x1/0xa0 [ 867.843157] preempt_count_sub+0x5/0xa0 [ 867.843159] ?     migrate_enable+0xac/0xf0 [ 867.843164] __bpf_prog_exit_recur+0x2d/0x40 [ 867.843168]     bpf_trampoline_6442468108_0+0x55/0x1000 ... [ 867.843788] preempt_count_sub+0x5/0xa0 [ 867.843793] ?     migrate_enable+0xac/0xf0 [ 867.843829] __bpf_prog_exit_recur+0x2d/0x40 [ 867.843837] BUG: IRQ stack guard     page was hit at 0000000099bd8228 (stack is 00000000b23e2bc4..000000006d95af35) [ 867.843841] BUG: IRQ     stack guard page was hit at 000000005ae07924 (stack is 00000000ffd69623..0000000014eb594c) [ 867.843843]     BUG: IRQ stack guard page was hit at 00000000028320f0 (stack is 00000000034b6438..0000000078d1bcec) [     867.843842] bpf_trampoline_6442468108_0+0x55/0x1000 ... That is because in __bpf_prog_exit_recur, the     preempt_count_{sub,add} are called after prog->active is decreased. Fixing this by adding these two     functions into btf ids deny list. (CVE-2023-54086)

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 Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1787305050 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: l2tp: prevent possible tunnel refcount     underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops     to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel     is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which     leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped.
    Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls     l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to     l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is     possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet     have session->tunnel set. Add a check for this case. (CVE-2024-49940)

  - In the Linux kernel, the following vulnerability has been resolved: mm/thp: fix deferred split unqueue     naming and locking Recent changes are putting more pressure on THP deferred split queues: under load     revealing long-standing races, causing list_del corruptions, Bad page states and worse (I keep BUGs in     both of those, so usually don't get to see how badly they end up without). The relevant recent changes     being 6.8's mTHP, 6.10's mTHP swapout, and 6.12's mTHP swapin, improved swap allocation, and underused THP     splitting. Before fixing locking: rename misleading folio_undo_large_rmappable(), which does not undo     large_rmappable, to folio_unqueue_deferred_split(), which is what it does. But that and its out-of-line
    __callee are mm internals of very limited usability: add comment and WARN_ON_ONCEs to check usage; and     return a bool to say if a deferred split was unqueued, which can then be used in WARN_ON_ONCEs around     safety checks (sparing callers the arcane conditionals in __folio_unqueue_deferred_split()). Just omit the     folio_unqueue_deferred_split() from free_unref_folios(), all of whose callers now call it beforehand (and     if any forget then bad_page() will tell) - except for its caller put_pages_list(), which itself no longer     has any callers (and will be deleted separately). Swapout: mem_cgroup_swapout() has been resetting     folio->memcg_data 0 without checking and unqueueing a THP folio from deferred split list; which is     unfortunate, since the split_queue_lock depends on the memcg (when memcg is enabled); so swapout has been     unqueueing such THPs later, when freeing the folio, using the pgdat's lock instead: potentially corrupting     the memcg's list. __remove_mapping() has frozen refcount to 0 here, so no problem with calling     folio_unqueue_deferred_split() before resetting memcg_data. That goes back to 5.4 commit 87eaceb3faa5     (mm: thp: make deferred split shrinker memcg aware): which included a check on swapcache before adding     to deferred queue, but no check on deferred queue before adding THP to swapcache. That worked fine with     the usual sequence of events in reclaim (though there were a couple of rare ways in which a THP on     deferred queue could have been swapped out), but 6.12 commit dafff3f4c850 (mm: split underused THPs)     avoids splitting underused THPs in reclaim, which makes swapcache THPs on deferred queue commonplace. Keep     the check on swapcache before adding to deferred queue? Yes: it is no longer essential, but preserves the     existing behaviour, and is likely to be a worthwhile optimization (vmstat showed much more traffic on the     queue under swapping load if the check was removed); update its comment. Memcg-v1 move (deprecated):
    mem_cgroup_move_account() has been changing folio->memcg_data without checking and unqueueing a THP folio     from the deferred list, sometimes corrupting from memcg's list, like swapout. Refcount is non-zero here,     so folio_unqueue_deferred_split() can only be used in a WARN_ON_ONCE to validate the fix, which must be     done earlier: mem_cgroup_move_charge_pte_range() first try to split the THP (splitting of course     unqueues), or skip it if that fails. Not ideal, but moving charge has been requested, and khugepaged     should repair the THP later: nobody wants new custom unqueueing code just for this deprecated case. The     87eaceb3faa5 commit did have the code to move from one deferred list to another (but was not conscious of     its unsafety while refcount non-0); but that was removed by 5.6 commit fac0516b5534 (mm: thp: don't need     care deferred split queue in memcg charge move path), which argued that the existence of a PMD mapping     guarantees that the THP cannot be on a deferred list. As above, false in rare cases, and now commonly     false. Backport to 6.11 should be straightforward. Earlier backports must take care that other
    _deferred_list fixes and dependencies are included. There is not a strong case for backports, but they can     fix cornercases. (CVE-2024-53079)

  - In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: reallocate buf lists on     upgrade IORING_REGISTER_PBUF_RING can reuse an old struct io_buffer_list if it was created for legacy     selected buffer and has been emptied. It violates the requirement that most of the field should stay     stable after publish. Always reallocate it instead. (CVE-2025-21836)

  - In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Add sanity checks on     rdev validity There is a possibility that ulp_irq_stop and ulp_irq_start callbacks will be called when the     device is in detached state. This can cause a crash due to NULL pointer dereference as the rdev is already     freed. (CVE-2025-21901)

  - In the Linux kernel, the following vulnerability has been resolved: cpufreq/amd-pstate: Add missing NULL     ptr check in amd_pstate_update Check if policy is NULL before dereferencing it in amd_pstate_update.
    (CVE-2025-23137)

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.

  - bpf: Reject sleepable kprobe_multi programs at attach time kprobe.multi programs run in atomic/RCU context     and cannot sleep. However, bpf_kprobe_multi_link_attach() did not validate whether the program being     attached had the sleepable flag set, allowing sleepable helpers such as bpf_copy_from_user() to be invoked     from a non-sleepable context. This causes a sleeping function called from invalid context splat: BUG:
    sleeping function called from invalid context at ./include/linux/uaccess.h:169 in_atomic(): 1,     irqs_disabled(): 0, non_block: 0, pid: 1787, name: sudo preempt_count: 1, expected: 0 RCU nest depth: 2,     expected: 0 Fix this by rejecting sleepable programs early in bpf_kprobe_multi_link_attach(), before any     further processing. (CVE-2026-43010)

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

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

  - In the Linux kernel, the following vulnerability has been resolved: l2tp: prevent possible tunnel refcount     underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops     to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel     is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which     leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped.
    Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls     l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to     l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is     possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet     have session->tunnel set. Add a check for this case. (CVE-2024-49940)

  - In the Linux kernel, the following vulnerability has been resolved: mm/thp: fix deferred split unqueue     naming and locking Recent changes are putting more pressure on THP deferred split queues: under load     revealing long-standing races, causing list_del corruptions, Bad page states and worse (I keep BUGs in     both of those, so usually don't get to see how badly they end up without). The relevant recent changes     being 6.8's mTHP, 6.10's mTHP swapout, and 6.12's mTHP swapin, improved swap allocation, and underused THP     splitting. Before fixing locking: rename misleading folio_undo_large_rmappable(), which does not undo     large_rmappable, to folio_unqueue_deferred_split(), which is what it does. But that and its out-of-line
    __callee are mm internals of very limited usability: add comment and WARN_ON_ONCEs to check usage; and     return a bool to say if a deferred split was unqueued, which can then be used in WARN_ON_ONCEs around     safety checks (sparing callers the arcane conditionals in __folio_unqueue_deferred_split()). Just omit the     folio_unqueue_deferred_split() from free_unref_folios(), all of whose callers now call it beforehand (and     if any forget then bad_page() will tell) - except for its caller put_pages_list(), which itself no longer     has any callers (and will be deleted separately). Swapout: mem_cgroup_swapout() has been resetting     folio->memcg_data 0 without checking and unqueueing a THP folio from deferred split list; which is     unfortunate, since the split_queue_lock depends on the memcg (when memcg is enabled); so swapout has been     unqueueing such THPs later, when freeing the folio, using the pgdat's lock instead: potentially corrupting     the memcg's list. __remove_mapping() has frozen refcount to 0 here, so no problem with calling     folio_unqueue_deferred_split() before resetting memcg_data. That goes back to 5.4 commit 87eaceb3faa5     (mm: thp: make deferred split shrinker memcg aware): which included a check on swapcache before adding     to deferred queue, but no check on deferred queue before adding THP to swapcache. That worked fine with     the usual sequence of events in reclaim (though there were a couple of rare ways in which a THP on     deferred queue could have been swapped out), but 6.12 commit dafff3f4c850 (mm: split underused THPs)     avoids splitting underused THPs in reclaim, which makes swapcache THPs on deferred queue commonplace. Keep     the check on swapcache before adding to deferred queue? Yes: it is no longer essential, but preserves the     existing behaviour, and is likely to be a worthwhile optimization (vmstat showed much more traffic on the     queue under swapping load if the check was removed); update its comment. Memcg-v1 move (deprecated):
    mem_cgroup_move_account() has been changing folio->memcg_data without checking and unqueueing a THP folio     from the deferred list, sometimes corrupting from memcg's list, like swapout. Refcount is non-zero here,     so folio_unqueue_deferred_split() can only be used in a WARN_ON_ONCE to validate the fix, which must be     done earlier: mem_cgroup_move_charge_pte_range() first try to split the THP (splitting of course     unqueues), or skip it if that fails. Not ideal, but moving charge has been requested, and khugepaged     should repair the THP later: nobody wants new custom unqueueing code just for this deprecated case. The     87eaceb3faa5 commit did have the code to move from one deferred list to another (but was not conscious of     its unsafety while refcount non-0); but that was removed by 5.6 commit fac0516b5534 (mm: thp: don't need     care deferred split queue in memcg charge move path), which argued that the existence of a PMD mapping     guarantees that the THP cannot be on a deferred list. As above, false in rare cases, and now commonly     false. Backport to 6.11 should be straightforward. Earlier backports must take care that other
    _deferred_list fixes and dependencies are included. There is not a strong case for backports, but they can     fix cornercases. (CVE-2024-53079)

  - In the Linux kernel, the following vulnerability has been resolved: io_uring/kbuf: reallocate buf lists on     upgrade IORING_REGISTER_PBUF_RING can reuse an old struct io_buffer_list if it was created for legacy     selected buffer and has been emptied. It violates the requirement that most of the field should stay     stable after publish. Always reallocate it instead. (CVE-2025-21836)

  - In the Linux kernel, the following vulnerability has been resolved: RDMA/bnxt_re: Add sanity checks on     rdev validity There is a possibility that ulp_irq_stop and ulp_irq_start callbacks will be called when the     device is in detached state. This can cause a crash due to NULL pointer dereference as the rdev is already     freed. (CVE-2025-21901)

  - In the Linux kernel, the following vulnerability has been resolved: cpufreq/amd-pstate: Add missing NULL     ptr check in amd_pstate_update Check if policy is NULL before dereferencing it in amd_pstate_update.
    (CVE-2025-23137)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
333954	Photon OS 5.0: Linux PHSA-2026-5.0-92-0916	Nessus	PhotonOS Local Security Checks	2026/8/10	2026/11/3	high
316948	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-1746)	Nessus	Amazon Linux Local Security Checks	2026/5/27	2026/7/16	high
361223	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1787307395)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	medium
332914	EulerOS 2.0 SP15 : kernel (EulerOS-SA-2026-2930)	Nessus	Huawei Local Security Checks	2026/8/6	2026/10/27	high
352240	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1787305050)	Nessus	Rocky Linux Local Security Checks	2026/9/30	2026/9/30	high
311650	Linux Distros Unpatched Vulnerability : CVE-2026-43010	Nessus	Misc.	2026/5/2	2026/10/21	medium
365522	Ubuntu 24.04 LTS : Linux kernel vulnerabilities (USN-8917-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
352220	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1787305050)	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/9/30	high

检测

插件搜索

high

high

medium

high

high

medium

medium

high