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

  - In the Linux kernel, the following vulnerability has been resolved: soc: qcom: qmi_encdec: Restrict string     length in decode The QMI TLV value for strings in a lot of qmi element info structures account for null     terminated strings with MAX_LEN + 1. If a string is actually MAX_LEN + 1 length, this will cause an out of     bounds access when the NULL character is appended in decoding. (CVE-2023-53729)

  - In the Linux kernel, the following vulnerability has been resolved: rv: Use strings in da monitors     tracepoints Using DA monitors tracepoints with KASAN enabled triggers the following warning: BUG: KASAN:
    global-out-of-bounds in do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0 Read of size 32 at addr     ffffffffaada8980 by task ... Call Trace: <TASK> [...] do_trace_event_raw_event_event_da_monitor+0xd6/0x1a0     ? __pfx_do_trace_event_raw_event_event_da_monitor+0x10/0x10 ? trace_event_sncid+0x83/0x200     trace_event_sncid+0x163/0x200 [...] The buggy address belongs to the variable: automaton_snep+0x4e0/0x5e0     This is caused by the tracepoints reading 32 bytes __array instead of __string from the automata     definition. Such strings are literals and reading 32 bytes ends up in out of bound memory accesses (e.g.
    the next automaton's data in this case). The error is harmless as, while printing the string, we stop at     the null terminator, but it should still be fixed. Use the __string facilities while defining the     tracepoints to avoid reading out of bound memory. (CVE-2025-38636)

  - In the Linux kernel, the following vulnerability has been resolved: perf: arm_spe: Prevent overflow in     PERF_IDX2OFF() Cast nr_pages to unsigned long to avoid overflow when handling large AUX buffer sizes (>= 2     GiB). (CVE-2025-40081)

  - In the Linux kernel, the following vulnerability has been resolved: arch_topology: Fix incorrect error     check in topology_parse_cpu_capacity() Fix incorrect use of PTR_ERR_OR_ZERO() in     topology_parse_cpu_capacity() which causes the code to proceed with NULL clock pointers. The current logic     uses !PTR_ERR_OR_ZERO(cpu_clk) which evaluates to true for both valid pointers and NULL, leading to     potential NULL pointer dereference in clk_get_rate(). Per include/linux/err.h documentation,     PTR_ERR_OR_ZERO(ptr) returns: The error code within @ptr if it is an error pointer; 0 otherwise. This     means PTR_ERR_OR_ZERO() returns 0 for both valid pointers AND NULL pointers. Therefore     !PTR_ERR_OR_ZERO(cpu_clk) evaluates to true (proceed) when cpu_clk is either valid or NULL, causing     clk_get_rate(NULL) to be called when of_clk_get() returns NULL. Replace with !IS_ERR_OR_NULL(cpu_clk)     which only proceeds for valid pointers, preventing potential NULL pointer dereference in clk_get_rate().
    (CVE-2025-40346)

  - In the Linux kernel, the following vulnerability has been resolved: platform/x86/amd/pmc: Add support for     Van Gogh SoC The ROG Xbox Ally (non-X) SoC features a similar architecture to the Steam Deck. While the     Steam Deck supports S3 (s2idle causes a crash), this support was dropped by the Xbox Ally which only S0ix     suspend. Since the handler is missing here, this causes the device to not suspend and the AMD GPU driver     to crash while trying to resume afterwards due to a power hang. (CVE-2025-68334)

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

The remote Oracle Linux 8 / 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2026-500249 advisory.

    - inet: frags: strip GSO state from fragments before reassembly (Xinyang Ge)  [Orabug: 39974835]     {CVE-2026-80590}
    - KVM: x86/mmu: Stop needlessly making MMU pages available for TDP MMU faults (David Matlack) [Orabug:
    39830590] {CVE-2026-64561}
    - KVM: x86: Check for invalid/obsolete root *after* making MMU pages available (Sean Christopherson)     [Orabug: 39830590,39832946] {CVE-2026-64561}
    - KVM: x86/mmu: Rename __direct_map() to direct_map() (David Matlack) [Orabug: 39830590] {CVE-2026-64561}
    - KVM: x86/mmu: Split out TDP MMU page fault handling (David Matlack) [Orabug: 39830590] {CVE-2026-64561}
    - KVM: Rename mmu_notifier_* to mmu_invalidate_* (Chao Peng) [Orabug: 39830590] {CVE-2026-64561}
    - KVM: x86/mmu: Document the 'rules' for using host_pfn_mapping_level() (Sean Christopherson) [Orabug:
    39830590] {CVE-2026-64561}
    - KVM: x86/mmu: Rename pte_list_{destroy,remove}() to show they zap SPTEs (Sean Christopherson) [Orabug:
    39830590] {CVE-2026-64561}
    - KVM: x86/mmu: Directly 'destroy' PTE list when recycling rmaps (Sean Christopherson) [Orabug: 39830590]     {CVE-2026-64561}
    - x86/bugs: Make Safe-RET robust against interrupt injection (Borislav Petkov) [Orabug: 39784615,39853775]     {CVE-2026-68480}
    - x86/alternatives: Disable interrupts and sync when optimizing NOPs in place (Thomas Gleixner) [Orabug:
    39784615] {CVE-2026-68480}
    - x86/alternative: Support relocations in alternatives (Peter Zijlstra) [Orabug: 39784615]     {CVE-2026-68480}
    - x86/alternative: Make debug-alternative selective (Peter Zijlstra) [Orabug: 39784615] {CVE-2026-68480}
    - x86/alternatives: Add alt_instr.flags (Borislav Petkov) [Orabug: 39784615] {CVE-2026-68480}
    - x86/asm: Provide ALTERNATIVE_3 (Peter Zijlstra) [Orabug: 39784615] {CVE-2026-68480}
    - posix-cpu-timers: Prevent UAF caused by non-leader exec() race (Thomas Gleixner) [Orabug: 39807438]     {CVE-2026-64560}
    - ALSA: seq: Fix uninitialised heap leak in snd_seq_event_dup() (Hyeongjun An) [Orabug: 39853280]     {CVE-2026-64479}
    - crypto: qat - validate RSA CRT component lengths (Giovanni Cabiddu) [Orabug: 39785885] {CVE-2026-64304}
    - btrfs: do not trim a device which is not writeable (Qu Wenruo) [Orabug: 39843586] {CVE-2026-64593}
    - bpf: Allow LPM map access from sleepable BPF programs (Vlad Poenaru) [Orabug: 39786046] {CVE-2026-64352}
    - bpf: Reject fragmented frames in devmap (Zhao Zhang) [Orabug: 39786052] {CVE-2026-64355}
    - HID: appleir: fix UAF on pending key_up_timer in remove() (Manish Khadka) [Orabug: 39786074]     {CVE-2026-64363}
    - proc: protect ptrace_may_access() with exec_update_lock (part 1) (Jann Horn) [Orabug: 39786095]     {CVE-2026-64371}
    - HID: multitouch: fix out-of-bounds bit access on mt_io_flags (Trung Nguyen) [Orabug: 39786078]     {CVE-2026-64364}
    - proc: protect ptrace_may_access() with exec_update_lock (FD links) (Jann Horn) [Orabug: 39786112]     {CVE-2026-64375}
    - smb: client: harden POSIX SID length parsing (Zihan Xi) [Orabug: 39786128] {CVE-2026-64380}
    - smb: client: mask server-provided mode to 07777 in modefromsid (Norbert Manthey) [Orabug: 39786124]     {CVE-2026-64379}
    - smb: client: resolve SWN tcon from live registrations (Michael Bommarito) [Orabug: 39786200]     {CVE-2026-64401}
    - smb: client: Fix next buffer leak in receive_encrypted_standard() (Haoxiang Li) [Orabug: 39786131]     {CVE-2026-64381}
    - Bluetooth: L2CAP: cancel pending_rx_work before taking conn->lock (Runyu Xiao) [Orabug: 39760901]     {CVE-2026-64206}
    - netfilter: ebtables: zero chainstack array (Florian Westphal) [Orabug: 39786232] {CVE-2026-64413}
    - staging: rtl8723bs: fix OOB reads in rtw_get_sec_ie(), rtw_get_wapi_ie(), and rtw_get_wps_attr()     (Alexandru Hossu) [Orabug: 39786307] {CVE-2026-64441}
    - PCI: mediatek: Fix IRQ domain leak when port fails to enable (Manivannan Sadhasivam) [Orabug: 39786366]     {CVE-2026-64461}
    - staging: rtl8723bs: fix heap buffer overflow in rtw_cfg80211_set_wpa_ie() (Alexandru Hossu) [Orabug:
    39786327] {CVE-2026-64446}
    - smb: client: restrict implied bcc[0] exemption to responses without data area (Shoichiro Miyamoto)     [Orabug: 39786332] {CVE-2026-64448}
    - vfio/pci: Release the VGA arbiter client on register_device() failure (Alex Williamson) [Orabug:
    39786409] {CVE-2026-64475}
    - ACPI: NFIT: core: Fix acpi_nfit_init() error cleanup (Rafael J. Wysocki) [Orabug: 39786502]     {CVE-2026-64510}
    - ACPI: CPPC: Suppress UBSAN warning caused by field misuse (Jeremy Linton) [Orabug: 39786508]     {CVE-2026-64512}
    - net: openvswitch: reject oversized nested action attrs (Asim Viladi Oglu Manizada) [Orabug:
    39789564,39816016,39819143] {CVE-2026-64531}
    - nvmet-tcp: check INIT_FAILED before nvmet_req_uninit in digest error path (Shivam Kumar) [Orabug:
    39789573] {CVE-2026-64534}
    - sctp: validate STALE_COOKIE cause length before reading staleness (Weiming Shi) [Orabug: 39794431]     {CVE-2026-64551}
    - netfilter: bridge: fix stale prevhdr pointer in br_ip6_fragment() (Xiang Mei) [Orabug: 39794442]     {CVE-2026-64554}
    - Bluetooth: bpa10x: avoid OOB read of revision string in bpa10x_setup() (Weiming Shi) [Orabug: 39794421]     {CVE-2026-64549}
    - net: usb: net1080: validate packet_len before pad-byte access in rx_fixup (Xiang Mei) [Orabug: 39794412]     {CVE-2026-64547}
    - usbnet: gl620a: fix out-of-bounds read in genelink_rx_fixup() (Xiang Mei) [Orabug: 39794387]     {CVE-2026-64540}
    - net/sched: cls_api: Handle TC_ACT_CONSUMED in tcf_qevent_handle (Jamal Hadi Salim) [Orabug: 39787017]     {CVE-2026-64530}
    - net, bpf: check master for NULL in xdp_master_redirect() (Xiang Mei) [Orabug: 39794405] {CVE-2026-64545}
    - ipv6: Fix null-ptr-deref in fib6_nh_mtu_change(). (Xiang Mei) [Orabug: 39794379] {CVE-2026-64538}
    - drm/edid: fix OOB read in drm_parse_tiled_block() (Xiang Mei) [Orabug: 39794408] {CVE-2026-64546}
    - net: psample: fix info leak in PSAMPLE_ATTR_DATA (Jakub Kicinski) [Orabug: 39794438] {CVE-2026-64553}
    - bpf, sockmap: reject overflowing copy + len in bpf_msg_push_data() (Weiming Shi) [Orabug: 39794417]     {CVE-2026-64548}
    - crypto: asymmetric_keys - fix OOB read in pefile_digest_pe_contents (Weiming Shi) [Orabug: 39794401]     {CVE-2026-64544}
    - xfs: fail recovery on a committed log item with no regions (Weiming Shi) [Orabug: 39760871]     {CVE-2026-64187}
    - fuse: re-lock request before returning from fuse_ref_folio() (Joanne Koong) [Orabug: 39785786]     {CVE-2026-64266}
    - Input: touchwin - reset the packet index on every complete packet (Bryam Vargas) [Orabug: 39785802]     {CVE-2026-64271}
    - Input: elan_i2c - prevent division by zero and arithmetic underflow (Ranjan Kumar) [Orabug: 39785819]     {CVE-2026-64275}
    - Input: synaptics-rmi4 - bound the F30 keymap to the GPIO/LED count (Bryam Vargas) [Orabug: 39785823]     {CVE-2026-64276}
    - i2c: core: fix adapter deregistration race (Johan Hovold) [Orabug: 39785831] {CVE-2026-64279}
    - KVM: VMX: Grab vmcs12 on CR8 interception update iff vCPU is in guest mode (Sean Christopherson)     [Orabug: 39843616] {CVE-2026-64604}
    - exfat: bound uniname advance in exfat_find_dir_entry() (Bryam Vargas) [Orabug: 39785863]     {CVE-2026-64296}
    - NFSv4: include MAY_WRITE in open permission mask for O_TRUNC (Benjamin Coddington) [Orabug: 39785868]     {CVE-2026-64298}
    - tracing: Prevent out-of-bounds read in glob matching (Huihui Huang) [Orabug: 39785872] {CVE-2026-64299}
    - crypto: drbg - Fix returning success on failure in CTR_DRBG (Eric Biggers) [Orabug: 39785893]     {CVE-2026-64306}
    - crypto: pcrypt - restore callback for non-parallel fallback (Ruijie Li) [Orabug: 39785906]     {CVE-2026-64312}
    - crypto: ecc - Fix carry overflow in vli multiplication (Anastasia Tishchenko) [Orabug: 39785910]     {CVE-2026-64313}
    - isofs: bound Rock Ridge symlink components to the SL record (Bryam Vargas) [Orabug: 39785923]     {CVE-2026-64317}
    - udf: validate sparing table length as an entry count, not a byte count (Bryam Vargas) [Orabug: 39785940]     {CVE-2026-64322}
    - udf: validate VAT header length against the VAT inode size (Bryam Vargas) [Orabug: 39785944]     {CVE-2026-64323}
    - udf: validate free block extents against the partition length (Michael Bommarito) [Orabug: 39785948]     {CVE-2026-64324}
    - usb: typec: tcpm: Validate SVID index in svdm_consume_modes() (Badhri Jagan Sridharan) [Orabug:
    39785963] {CVE-2026-64330}
    - usbip: vudc: fix NULL deref in vep_dequeue() (Sam Day) [Orabug: 39785967] {CVE-2026-64331}
    - USB: ulpi: fix memory leak on registration failure (Johan Hovold) [Orabug: 39785971] {CVE-2026-64332}
    - USB: serial: digi_acceleport: fix write buffer corruption (Johan Hovold) [Orabug: 39785975]     {CVE-2026-64333}
    - USB: serial: digi_acceleport: fix hard lockup on disconnect (Johan Hovold) [Orabug: 39785979]     {CVE-2026-64334}
    - USB: serial: digi_acceleport: fix broken rx after throttle (Johan Hovold) [Orabug: 39785983]     {CVE-2026-64335}
    - USB: serial: keyspan_pda: fix information leak (Johan Hovold) [Orabug: 39785987] {CVE-2026-64336}
    - USB: misc: uss720: unregister parport on probe failure (Myeonghun Pak) [Orabug: 39785994]     {CVE-2026-64338}
    - USB: legousbtower: fix use-after-free on disconnect race (Johan Hovold) [Orabug: 39785999]     {CVE-2026-64340}
    - USB: iowarrior: fix use-after-free on disconnect (Johan Hovold) [Orabug: 39786007] {CVE-2026-64342}
    - USB: ldusb: fix use-after-free on disconnect race (Johan Hovold) [Orabug: 39786012] {CVE-2026-64343}
    - USB: idmouse: fix use-after-free on disconnect race (Johan Hovold) [Orabug: 39786017] {CVE-2026-64344}
    - usb: gadget: udc: Fix use-after-free in gadget_match_driver (Jimmy Hu) [Orabug: 39786026]     {CVE-2026-64346}
    - usb: gadget: composite: fix dead empty check in the USB_DT_OTG handler (Maoyi Xie) [Orabug: 39786030]     {CVE-2026-64347}
    - net: usb: kalmia: bound RX frame length in kalmia_rx_fixup() (Maoyi Xie) [Orabug: 39786042]     {CVE-2026-64351}
    - HID: lg-g15: cancel pending work on remove to fix a use-after-free (Maoyi Xie) [Orabug: 39786071]     {CVE-2026-64362}
    - HID: wacom: stop hardware after post-start probe failures (Myeonghun Pak) [Orabug: 39859299]     {CVE-2026-68091}
    - posix-cpu-timers: Fix pid refcount leak in do_cpu_nanosleep() error path (Xu Wang) [Orabug: 39786091]     {CVE-2026-64370}
    - cpufreq: pcc: fix use-after-free and double free in _OSC evaluation (Yuho Choi) [Orabug: 39786100]     {CVE-2026-64372}
    - cpufreq: Fix hotplug-suspend race during reboot (Tianxiang Chen) [Orabug: 39786104] {CVE-2026-64373}
    - sched/rt: Have RT_PUSH_IPI be default off for non PREEMPT_RT (Steven Rostedt) [Orabug: 39786108]     {CVE-2026-64374}
    - net: Drop the lock in skb_may_tx_timestamp() (Sebastian Andrzej Siewior) [Orabug: 39331701]     {CVE-2026-43216}
    - Bluetooth: L2CAP: validate option length before reading conf opt value (Muhammad Bilal) [Orabug:
    39786205] {CVE-2026-64403}
    - Bluetooth: fix UAF in bt_accept_dequeue() (Yousef Alhouseen) [Orabug: 39786578] {CVE-2026-64406}
    - Bluetooth: bnep: pin L2CAP connection during netdev registration (Yousef Alhouseen) [Orabug: 39786217]     {CVE-2026-64408}
    - netfilter: ebtables: terminate table name before find_table_lock() (Xiang Mei) [Orabug: 39786224]     {CVE-2026-64411}
    - netfilter: ebtables: module names must be null-terminated (Florian Westphal) [Orabug: 39786228]     {CVE-2026-64412}
    - mfd: cros_ec: Delay dev_set_drvdata() until probe success (Andrei Kuchynski) [Orabug: 39786248]     {CVE-2026-64420}
    - net: ipv4: bound TCP reordering sysctl writes and MTU probe sizes (Wyatt Feng) [Orabug: 39786254]     {CVE-2026-64422}
    - ipv4: igmp: remove multicast group from hash table on device destruction (Yuyang Huang) [Orabug:
    39786259] {CVE-2026-64423}
    - io_uring/io-wq: re-check IO_WQ_BIT_EXIT for each linked work item (Runyu Xiao) [Orabug: 39786574]     {CVE-2026-64425}
    - audit: Fix data races of skb_queue_len() readers on audit_queue (Chi Wang) [Orabug: 39786289]     {CVE-2026-64435}
    - net: af_key: initialize alg_key_len for IPComp states (Zijing Yin) [Orabug: 39786293] {CVE-2026-64436}
    - crypto: amlogic - avoid double cleanup in meson_crypto_probe() (Dawei Feng) [Orabug: 39843604]     {CVE-2026-64599}
    - staging: rtl8723bs: fix OOB write in HT_caps_handler() (Alexandru Hossu) [Orabug: 39786303]     {CVE-2026-64440}
    - staging: rtl8723bs: fix OOB reads in is_ap_in_tkip() IE loop (Alexandru Hossu) [Orabug: 39789581]     {CVE-2026-64536}
    - staging: rtl8723bs: fix OOB reads in IE loops in issue_assocreq() and join_cmd_hdl() (Alexandru Hossu)     [Orabug: 39786311] {CVE-2026-64442}
    - staging: rtl8723bs: fix OOB read in update_beacon_info() IE loop (Alexandru Hossu) [Orabug: 39786315]     {CVE-2026-64443}
    - staging: rtl8723bs: fix OOB read in OnAssocRsp() IE loop (Alexandru Hossu) [Orabug: 39786319]     {CVE-2026-64444}
    - staging: rtl8723bs: fix WEP length underflow and OOB read in OnAuth() (Alexandru Hossu) [Orabug:
    39786323] {CVE-2026-64445}
    - tipc: fix out-of-bounds read in broadcast Gap ACK blocks (Samuel Page) [Orabug: 39786340]     {CVE-2026-64450}
    - 6lowpan: fix NHC entry use-after-free on error path (Yizhou Zhao) [Orabug: 39786344] {CVE-2026-64452}
    - usb: dwc3: run gadget disconnect from sleepable suspend context (Runyu Xiao) [Orabug: 39786349]     {CVE-2026-64454}
    - USB: chaoskey: Fix slab-use-after-free in chaoskey_release() (Alan Stern) [Orabug: 39786352]     {CVE-2026-64455}
    - hwrng: virtio: clamp device-reported used.len at copy_data() (Michael Bommarito) [Orabug: 39786356]     {CVE-2026-64456}
    - netfilter: ipset: fix race between dump and ip_set_list resize (Xiang Mei) [Orabug: 39760883]     {CVE-2026-64189}
    - usb: xhci: Fix sleep in atomic context in xhci_free_streams() (Lianqin Hu) [Orabug: 39786379]     {CVE-2026-64465}
    - Bluetooth: btusb: fix use-after-free on marvell probe failure (Johan Hovold) [Orabug: 39786393]     {CVE-2026-64470}
    - Bluetooth: btusb: fix use-after-free on registration failure (Johan Hovold) [Orabug: 39786397]     {CVE-2026-64471}
    - ALSA: usb-audio: avoid kobject path lookup in DualSense match (Darvell Long) [Orabug: 39786416]     {CVE-2026-64478}
    - ALSA: firewire: isight: bound the sample count to the packet payload (Maoyi Xie) [Orabug: 39786428]     {CVE-2026-64483}
    - ALSA: es1938: check snd_ctl_new1() return value (Zhao Dongdong) [Orabug: 39786432] {CVE-2026-64484}
    - ALSA: caiaq: fix out-of-bounds read in the Traktor Kontrol S4 input parser (Maoyi Xie) [Orabug:
    39786439] {CVE-2026-64487}
    - iio: event: Fix event FIFO reset race (Lars-Peter Clausen) [Orabug: 39786462] {CVE-2026-64496}
    - iio: accel: kxsd9: fix runtime PM imbalance on write_raw() error (Biren Pandya) [Orabug: 39786478]     {CVE-2026-64503}
    - iio: accel: bmc150: clamp the device-reported FIFO frame count (Bryam Vargas) [Orabug: 39786482]     {CVE-2026-64504}
    - NFSv4/flexfiles: reject zero filehandle version count (Michael Bommarito) [Orabug: 39753894]     {CVE-2026-53392}
    - fbdev: fbcon: fix out-of-bounds read in err_out of fbcon_do_set_font() (Mingyu Wang) [Orabug: 39753924]     {CVE-2026-53402}
    - i2c: core: fix adapter registration race (Johan Hovold) [Orabug: 39753916] {CVE-2026-53400}
    - block: Avoid mounting the bdev pseudo-filesystem in userspace (Denis Arefev) [Orabug: 39753985]     {CVE-2026-63810}
    - net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink (Maoyi Xie) [Orabug: 39754045]     {CVE-2026-63829}
    - net: skmsg: preserve sg.copy across SG transforms (Yiming Qian) [Orabug: 39754049] {CVE-2026-63830}
    - netfilter: nf_tables: restore set elements when delete set fails (Pablo Neira Ayuso) [Orabug: 36598010]     {CVE-2024-27012}
    - KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() (Sean     Christopherson) [Orabug: 39753972] {CVE-2026-63806}
    - userfaultfd: gate must_wait writability check on pte_present() (Kiryl Shutsemau) [Orabug: 39786515]     {CVE-2026-64514}
    - nfsd: reset write verifier on deferred writeback errors (Jeff Layton) [Orabug: 39753898]     {CVE-2026-53393}
    - nfsd: release layout stid on setlease failure (Chris Mason) [Orabug: 39753912] {CVE-2026-53399}
    - nvmet-tcp: fix race between ICReq handling and queue teardown (Chaitanya Kulkarni) [Orabug: 39460310]     {CVE-2026-46135}
    - net: tap: set skb->dev before parsing virtio net header in tap_get_user_xdp() (Dongli Zhang) [Orabug:
    39558744] {CVE-2026-74684}
    - net/rds: zero per-item info buffer before handing it to visitors (Michael Bommarito) [Orabug:
    39621715,39638197] {CVE-2026-52995}
    - x86/sev: Evict cache lines during SNP memory validation (Tom Lendacky) [Orabug: 38334919]     {CVE-2025-38560}
    - xfs: resample the data fork mapping after cycling ILOCK (Darrick Wong) [Orabug: 39776791]     {CVE-2026-64600}

Tenable has extracted the preceding description block directly from the Oracle 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 Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1793370479 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: Fix buffer overflow in     debugfs If the user tries to write more than 32 bytes then it results in memory corruption. Fortunately,     this is debugfs so it's limited to root users. (CVE-2025-38317)

  - In the Linux kernel, the following vulnerability has been resolved: drm/xe/pf: Clear all LMTT pages on     alloc Our LMEM buffer objects are not cleared by default on alloc and during VF provisioning we only setup     LMTT PTEs for the actually provisioned LMEM range. But beyond that valid range we might leave some stale     data that could either point to some other VFs allocations or even to the PF pages. Explicitly clear all     new LMTT page to avoid the risk that a malicious VF would try to exploit that gap. While around add     asserts to catch any undesired PTE overwrites and low-level debug traces to track LMTT PT life-cycle.
    (cherry picked from commit 3fae6918a3e27cce20ded2551f863fb05d4bef8d) (CVE-2025-38511)

  - In the Linux kernel, the following vulnerability has been resolved: wifi: ath12k: fix memory leak in     ath12k_service_ready_ext_event Currently, in ath12k_service_ready_ext_event(), svc_rdy_ext.mac_phy_caps is     not freed in the failure case, causing a memory leak. The following trace is observed in kmemleak:
    unreferenced object 0xffff8b3eb5789c00 (size 1024): comm softirq, pid 0, jiffies 4294942577 hex dump     (first 32 bytes): 00 00 00 00 01 00 00 00 00 00 00 00 7b 00 00 10 ............{... 01 00 00 00 00 00 00 00     01 00 00 00 1f 38 00 00 .............8.. backtrace (crc 44e1c357): __kmalloc_noprof+0x30b/0x410     ath12k_wmi_mac_phy_caps_parse+0x84/0x100 [ath12k] ath12k_wmi_tlv_iter+0x5e/0x140 [ath12k]     ath12k_wmi_svc_rdy_ext_parse+0x308/0x4c0 [ath12k] ath12k_wmi_tlv_iter+0x5e/0x140 [ath12k]     ath12k_service_ready_ext_event.isra.0+0x44/0xd0 [ath12k] ath12k_wmi_op_rx+0x2eb/0xd70 [ath12k]     ath12k_htc_rx_completion_handler+0x1f4/0x330 [ath12k] ath12k_ce_recv_process_cb+0x218/0x300 [ath12k]     ath12k_pci_ce_workqueue+0x1b/0x30 [ath12k] process_one_work+0x219/0x680 bh_worker+0x198/0x1f0     tasklet_action+0x13/0x30 handle_softirqs+0xca/0x460 __irq_exit_rcu+0xbe/0x110 irq_exit_rcu+0x9/0x30 Free     svc_rdy_ext.mac_phy_caps in the error case to fix this memory leak. Tested-on: QCN9274 hw2.0 PCI     WLAN.WBE.1.4.1-00199-QCAHKSWPL_SILICONZ-1 (CVE-2025-39890)

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Fix metadata_dst leak
    __bpf_redirect_neigh_v{4,6} Cilium has a BPF egress gateway feature which forces outgoing K8s Pod traffic     to pass through dedicated egress gateways which then SNAT the traffic in order to interact with stable IPs     outside the cluster. The traffic is directed to the gateway via vxlan tunnel in collect md mode. A recent     BPF change utilized the bpf_redirect_neigh() helper to forward packets after the arrival and decap on     vxlan, which turned out over time that the kmalloc-256 slab usage in kernel was ever-increasing. The issue     was that vxlan allocates the metadata_dst object and attaches it through a fake dst entry to the skb. The     latter was never released though given bpf_redirect_neigh() was merely setting the new dst entry via     skb_dst_set() without dropping an existing one first. (CVE-2025-40183)

  - In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_router: Fix neighbour     use-after-free We sometimes observe use-after-free when dereferencing a neighbour [1]. The problem seems     to be that the driver stores a pointer to the neighbour, but without holding a reference on it. A     reference is only taken when the neighbour is used by a nexthop. Fix by simplifying the reference counting     scheme. Always take a reference when storing a neighbour pointer in a neighbour entry. Avoid taking a     referencing when the neighbour is used by a nexthop as the neighbour entry associated with the nexthop     already holds a reference. Tested by running the test that uncovered the problem over 300 times. Without     this patch the problem was reproduced after a handful of iterations. [1] BUG: KASAN: slab-use-after-free     in mlxsw_sp_neigh_entry_update+0x2d4/0x310 Read of size 8 at addr ffff88817f8e3420 by task ip/3929 CPU: 3     UID: 0 PID: 3929 Comm: ip Not tainted 6.18.0-rc4-virtme-g36b21a067510 #3 PREEMPT(full) Hardware name:
    Nvidia SN5600/VMOD0013, BIOS 5.13 05/31/2023 Call Trace: <TASK> dump_stack_lvl+0x6f/0xa0     print_address_description.constprop.0+0x6e/0x300 print_report+0xfc/0x1fb kasan_report+0xe4/0x110     mlxsw_sp_neigh_entry_update+0x2d4/0x310 mlxsw_sp_router_rif_gone_sync+0x35f/0x510     mlxsw_sp_rif_destroy+0x1ea/0x730 mlxsw_sp_inetaddr_port_vlan_event+0xa1/0x1b0
    __mlxsw_sp_inetaddr_lag_event+0xcc/0x130 __mlxsw_sp_inetaddr_event+0xf5/0x3c0     mlxsw_sp_router_netdevice_event+0x1015/0x1580 notifier_call_chain+0xcc/0x150     call_netdevice_notifiers_info+0x7e/0x100 __netdev_upper_dev_unlink+0x10b/0x210     netdev_upper_dev_unlink+0x79/0xa0 vrf_del_slave+0x18/0x50 do_set_master+0x146/0x7d0     do_setlink.isra.0+0x9a0/0x2880 rtnl_newlink+0x637/0xb20 rtnetlink_rcv_msg+0x6fe/0xb90     netlink_rcv_skb+0x123/0x380 netlink_unicast+0x4a3/0x770 netlink_sendmsg+0x75b/0xc90
    __sock_sendmsg+0xbe/0x160 ____sys_sendmsg+0x5b2/0x7d0 ___sys_sendmsg+0xfd/0x180 __sys_sendmsg+0x124/0x1c0     do_syscall_64+0xbb/0xfd0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 [...] Allocated by task 109:
    kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_kmalloc+0x7b/0x90
    __kmalloc_noprof+0x2c1/0x790 neigh_alloc+0x6af/0x8f0 ___neigh_create+0x63/0xe90     mlxsw_sp_nexthop_neigh_init+0x430/0x7e0 mlxsw_sp_nexthop_type_init+0x212/0x960     mlxsw_sp_nexthop6_group_info_init.constprop.0+0x81f/0x1280 mlxsw_sp_nexthop6_group_get+0x392/0x6a0     mlxsw_sp_fib6_entry_create+0x46a/0xfd0 mlxsw_sp_router_fib6_replace+0x1ed/0x5f0     mlxsw_sp_router_fib6_event_work+0x10a/0x2a0 process_one_work+0xd57/0x1390 worker_thread+0x4d6/0xd40     kthread+0x355/0x5b0 ret_from_fork+0x1d4/0x270 ret_from_fork_asm+0x11/0x20 Freed by task 154:
    kasan_save_stack+0x30/0x50 kasan_save_track+0x14/0x30 __kasan_save_free_info+0x3b/0x60
    __kasan_slab_free+0x43/0x70 kmem_cache_free_bulk.part.0+0x1eb/0x5e0 kvfree_rcu_bulk+0x1f2/0x260     kfree_rcu_work+0x130/0x1b0 process_one_work+0xd57/0x1390 worker_thread+0x4d6/0xd40 kthread+0x355/0x5b0     ret_from_fork+0x1d4/0x270 ret_from_fork_asm+0x11/0x20 Last potentially related work creation:
    kasan_save_stack+0x30/0x50 kasan_record_aux_stack+0x8c/0xa0 kvfree_call_rcu+0x93/0x5b0     mlxsw_sp_router_neigh_event_work+0x67d/0x860 process_one_work+0xd57/0x1390 worker_thread+0x4d6/0xd40     kthread+0x355/0x5b0 ret_from_fork+0x1d4/0x270 ret_from_fork_asm+0x11/0x20 (CVE-2025-68801)

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.

  - dm thin metadata: fix metadata snapshot consistency on commit failure __reserve_metadata_snap() and
    __release_metadata_snap() modify the superblock's held_root directly in the block_manager's buffer. If the     subsequent metadata commit fails, the held_root gets flushed to disk through the abort_transaction path,     resulting in inconsistent metadata. Reproducer 1: __reserve_metadata_snap() 1. Create a 2 MiB metadata     device and make the region after the 14th block inaccessible, to trigger metadata commit failure in the     subsequent reserve_metadata_snap operation. The 14th block will be the shadow destination for the index     block. dmsetup create tmeta --table 0 112 linear /dev/sdc 0 112 3984 error 2. Create a 16 MiB thin-pool     dmsetup create tdata --table 0 32768 zero dd if=/dev/zero of=/dev/mapper/tmeta bs=4k count=1 dmsetup     create tpool --table 0 32768 thin-pool /dev/mapper/tmeta \ /dev/mapper/tdata 128 0 1 skip_block_zeroing     3. Take a metadata snapshot to trigger metadata commit failure and transaction abort. However, the     held_root is written to disk, breaking metadata consistency. dmsetup message tpool 0     reserve_metadata_snap thin_check v1.2.2 result: Bad reference count for metadata block 6. Expected 2,     but space map contains 1. Bad reference count for metadata block 7. Expected 2, but space map contains 1.
    Bad reference count for metadata block 13. Expected 1, but space map contains 0. Reproducer 2:
    __release_metadata_snap() 1. Create a 2 MiB metadata device and make the region after the 16th block     inaccessible, to trigger metadata commit failure in the subsequent release_metadata_snap operation. The     16th block will be the shadow destination for the index block. dmsetup create tmeta --table 0 128 linear     /dev/sdc 0 128 3968 error 2. Create a 16 MiB thin-pool dmsetup create tdata --table 0 32768 zero dd     if=/dev/zero of=/dev/mapper/tmeta bs=4k count=1 dmsetup create tpool --table 0 32768 thin-pool     /dev/mapper/tmeta \ /dev/mapper/tdata 128 0 1 skip_block_zeroing 3. Reserve then release the metadata     snapshot, to trigger metadata commit failure and transaction abort. The held_root gets removed from the     on-disk superblock, causing inconsistent metadata. dmsetup message tpool 0 reserve_metadata_snap dmsetup     message tpool 0 release_metadata_snap thin_check v1.2.2 result: Bad reference count for metadata block     6. Expected 1, but space map contains 2. Bad reference count for metadata block 7. Expected 1, but space     map contains 2. 1 metadata blocks have leaked. Fix by deferring the held_root update to commit time.
    Additionally, move the existing-snapshot check in __reserve_metadata_snap before the shadow operation to     avoid unnecessary work. In __release_metadata_snap, clear pmd->held_root before btree deletion so partial     failure leaks blocks rather than leaving a stale reference, and unlock the snapshot block before     decrementing its refcount. (CVE-2026-72108)

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

The CentOS Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare CENTOS7:CLSA-2026:1792976962 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: avoid uninit memory read     in ath9k_htc_rx_msg() syzbot is reporting uninit value at ath9k_htc_rx_msg() [1], for     ioctl(USB_RAW_IOCTL_EP_WRITE) can call ath9k_hif_usb_rx_stream() with pkt_len = 0 but     ath9k_hif_usb_rx_stream() uses __dev_alloc_skb(pkt_len + 32, GFP_ATOMIC) based on an assumption that     pkt_len is valid. As a result, ath9k_hif_usb_rx_stream() allocates skb with uninitialized memory and     ath9k_htc_rx_msg() is reading from uninitialized memory. Since bytes accessed by ath9k_htc_rx_msg() is not     known until ath9k_htc_rx_msg() is called, it would be difficult to check minimal valid pkt_len at if     (pkt_len > 2 * MAX_RX_BUF_SIZE) { line in ath9k_hif_usb_rx_stream(). We have two choices. One is to     workaround by adding __GFP_ZERO so that ath9k_htc_rx_msg() sees 0 if pkt_len is invalid. The other is to     let ath9k_htc_rx_msg() validate pkt_len before accessing. This patch chose the latter. Note that I'm not     sure threshold condition is correct, for I can't find details on possible packet length used by this     protocol. (CVE-2022-50709)

  - In the Linux kernel, the following vulnerability has been resolved: configfs: fix possible memory leak in     configfs_create_dir() kmemleak reported memory leaks in configfs_create_dir(): unreferenced object     0xffff888009f6af00 (size 192): comm modprobe, pid 3777, jiffies 4295537735 (age 233.784s) backtrace:
    kmem_cache_alloc (mm/slub.c:3250 mm/slub.c:3256 mm/slub.c:3263 mm/slub.c:3273) new_fragment     (./include/linux/slab.h:600 fs/configfs/dir.c:163) configfs_register_subsystem (fs/configfs/dir.c:1857)     basic_write (drivers/hwtracing/stm/p_basic.c:14) stm_p_basic do_one_initcall (init/main.c:1296)     do_init_module (kernel/module/main.c:2455) ... unreferenced object 0xffff888003ba7180 (size 96): comm     modprobe, pid 3777, jiffies 4295537735 (age 233.784s) backtrace: kmem_cache_alloc (mm/slub.c:3250     mm/slub.c:3256 mm/slub.c:3263 mm/slub.c:3273) configfs_new_dirent (./include/linux/slab.h:723     fs/configfs/dir.c:194) configfs_make_dirent (fs/configfs/dir.c:248) configfs_create_dir     (fs/configfs/dir.c:296) configfs_attach_group.isra.28 (fs/configfs/dir.c:816 fs/configfs/dir.c:852)     configfs_register_subsystem (fs/configfs/dir.c:1881) basic_write (drivers/hwtracing/stm/p_basic.c:14)     stm_p_basic do_one_initcall (init/main.c:1296) do_init_module (kernel/module/main.c:2455) ... This is     because the refcount is not correct in configfs_make_dirent(). For normal stage, the refcount is changing     as: configfs_register_subsystem() configfs_create_dir() configfs_make_dirent() configfs_new_dirent() # set     s_count = 1 dentry->d_fsdata = configfs_get(sd); # s_count = 2 ... configfs_unregister_subsystem()     configfs_remove_dir() remove_dir() configfs_remove_dirent() # s_count = 1 dput() ...
    *dentry_unlink_inode()* configfs_d_iput() # s_count = 0, release However, if we failed in     configfs_create(): configfs_register_subsystem() configfs_create_dir() configfs_make_dirent() # s_count =     2 ... configfs_create() # fail ->out_remove: configfs_remove_dirent(dentry) configfs_put(sd) # s_count = 1     return PTR_ERR(inode); There is no inode in the error path, so the configfs_d_iput() is lost and makes sd     and fragment memory leaked. To fix this, when we failed in configfs_create(), manually call     configfs_put(sd) to keep the refcount correct. (CVE-2022-50751)

  - In the Linux kernel, the following vulnerability has been resolved: pstore: Avoid kcore oops by vmap()ing     with VM_IOREMAP An oops can be induced by running 'cat /proc/kcore > /dev/null' on devices using pstore     with the ram backend because kmap_atomic() assumes lowmem pages are accessible with __va(). Unable to     handle kernel paging request at virtual address ffffff807ff2b000 Mem abort info: ESR = 0x96000006 EC =     0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x06: level 2 translation     fault Data abort info: ISV = 0, ISS = 0x00000006 CM = 0, WnR = 0 swapper pgtable: 4k pages, 39-bit VAs,     pgdp=0000000081d87000 [ffffff807ff2b000] pgd=180000017fe18003, p4d=180000017fe18003, pud=180000017fe18003,     pmd=0000000000000000 Internal error: Oops: 96000006 [#1] PREEMPT SMP Modules linked in: dm_integrity CPU:
    7 PID: 21179 Comm: perf Not tainted 5.15.67-10882-ge4eb2eb988cd #1     baa443fb8e8477896a370b31a821eb2009f9bfba Hardware name: Google Lazor (rev3 - 8) (DT) pstate: a0400009     (NzCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : __memcpy+0x110/0x260 lr : vread+0x194/0x294 sp :
    ffffffc013ee39d0 x29: ffffffc013ee39f0 x28: 0000000000001000 x27: ffffff807ff2b000 x26: 0000000000001000     x25: ffffffc0085a2000 x24: ffffff802d4b3000 x23: ffffff80f8a60000 x22: ffffff802d4b3000 x21:
    ffffffc0085a2000 x20: ffffff8080b7bc68 x19: 0000000000001000 x18: 0000000000000000 x17: 0000000000000000     x16: 0000000000000000 x15: ffffffd3073f2e60 x14: ffffffffad588000 x13: 0000000000000000 x12:
    0000000000000001 x11: 00000000000001a2 x10: 00680000fff2bf0b x9 : 03fffffff807ff2b x8 : 0000000000000001     x7 : 0000000000000000 x6 : 0000000000000000 x5 : ffffff802d4b4000 x4 : ffffff807ff2c000 x3 :
    ffffffc013ee3a78 x2 : 0000000000001000 x1 : ffffff807ff2b000 x0 : ffffff802d4b3000 Call trace:
    __memcpy+0x110/0x260 read_kcore+0x584/0x778 proc_reg_read+0xb4/0xe4 During early boot, memblock reserves     the pages for the ramoops reserved memory node in DT that would otherwise be part of the direct lowmem     mapping. Pstore's ram backend reuses those reserved pages to change the memory type (writeback or non-     cached) by passing the pages to vmap() (see pfn_to_page() usage in persistent_ram_vmap() for more details)     with specific flags. When read_kcore() starts iterating over the vmalloc region, it runs over the virtual     address that vmap() returned for ramoops. In aligned_vread() the virtual address is passed to     vmalloc_to_page() which returns the page struct for the reserved lowmem area. That lowmem page is passed     to kmap_atomic(), which effectively calls page_to_virt() that assumes a lowmem page struct must be     directly accessible with __va() and friends. These pages are mapped via vmap() though, and the lowmem     mapping was never made, so accessing them via the lowmem virtual address oopses like above. Let's side-     step this problem by passing VM_IOREMAP to vmap(). This will tell vread() to not include the ramoops     region in the kcore. Instead the area will look like a bunch of zeros. The alternative is to teach kmap()     about vmalloc areas that intersect with lowmem. Presumably such a change isn't a one-liner, and there     isn't much interest in inspecting the ramoops region in kcore files anyway, so the most expedient route is     taken for now. (CVE-2022-50849)

  - In the Linux kernel, the following vulnerability has been resolved: hwrng: amd - Fix PCI device refcount     leak for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it     will increase the reference count for the returned pci_dev and also decrease the reference count for the     input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop with pdev not NULL, we need to     call pci_dev_put() to decrease the reference count. Add the missing pci_dev_put() for the normal and error     path. (CVE-2022-50868)

  - In the Linux kernel, the following vulnerability has been resolved: RDMA/srp: Do not call scsi_done() from     srp_abort() After scmd_eh_abort_handler() has called the SCSI LLD eh_abort_handler callback, it performs     one of the following actions: * Call scsi_queue_insert(). * Call scsi_finish_command(). * Call     scsi_eh_scmd_add(). Hence, SCSI abort handlers must not call scsi_done(). Otherwise all the above actions     would trigger a use-after-free. Hence remove the scsi_done() call from srp_abort(). Keep the     srp_free_req() call before returning SUCCESS because we may not see the command again if SUCCESS is     returned. (CVE-2023-52515)

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

The remote Ubuntu 24.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-8886-1 advisory.

    Several security issues were discovered in the Linux kernel. An attacker could possibly use these to     compromise the system. This update corrects flaws in the following subsystems:

    - NVDIMM (Non-Volatile Memory Device) drivers;

    - Handshake API;

    - ARM32 architecture;

    - ARM64 architecture;

    - MIPS architecture;

    - OpenRISC architecture;

    - PowerPC architecture;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Intel NPU Driver;

    - Android drivers;

    - Rados block device (RBD) driver;

    - Bluetooth drivers;

    - Hardware random number generator core;

    - TPM device driver;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - DMA engine subsystem;

    - FireWire subsystem;

    - Arm Firmware Framework for ARMv8-A(FFA);

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Hardware monitoring drivers;

    - CoreSight HW tracing drivers;

    - I2C subsystem;

    - IIO ADC drivers;

    - IIO subsystem;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Mouse) drivers;

    - IOMMU subsystem;

    - Multiple devices driver;

    - Media drivers;

    - Multifunction device drivers;

    - Fastrpc Driver;

    - Amazon Nitro Secure Module driver;

    - MMC subsystem;

    - MTD block device drivers;

    - Ethernet bonding driver;

    - Network drivers;

    - Mellanox network drivers;

    - Texas Instruments network drivers;

    - NTB driver;

    - NVME drivers;

    - NVMEM (Non Volatile Memory) drivers;

    - Parport drivers;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - i.MX PM domains;

    - System reset/shutdown drivers;

    - PTP clock framework;

    - Voltage and Current Regulator drivers;

    - S/390 drivers;

    - SCSI subsystem;

    - SPI subsystem;

    - Realtek RTL8723BS SDIO drivers;

    - VME bus staging drivers;

    - Thermal drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - DesignWare USB2 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - USB Dual Role (OTG-ready) Controller drivers;

    - USB Serial drivers;

    - USB Type-C Port Controller Manager driver;

    - vDPA drivers;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - Watchdog drivers;

    - 9P distributed file system;

    - AFS file system;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - EROFS file system;

    - exFAT file system;

    - F2FS file system;

    - FUSE (File system in Userspace);

    - Journaling layer for block devices (JBD2);

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NTFS3 file system;

    - OCFS2 file system;

    - Proc file system;

    - SMB network file system;

    - Tracing file system;

    - UDF file system;

    - XFS file system;

    - Key management;

    - BPF subsystem;

    - Control group (cgroup);

    - Glob pattern matching library;

    - MAC80211 subsystem;

    - Mellanox drivers;

    - Networking core;

    - Network sockets;

    - IPv6 networking;

    - Bluetooth subsystem;

    - Wireless networking;

    - IPv4 networking;

    - Netfilter;

    - Network traffic control;

    - SCTP protocol;

    - TCP network protocol;

    - XFRM subsystem;

    - RDMA verbs API;

    - io_uring subsystem;

    - IPC subsystem;

    - Audit subsystem;

    - Kernel CPU control infrastructure;

    - Perf events;

    - Kernel exit() syscall;

    - Kernel fork() syscall;

    - Scheduler infrastructure;

    - Signal handling mechanism;

    - Timer subsystem;

    - Tracing infrastructure;

    - Resizable hashtable library;

    - Memory management;

    - 6LoWPAN network protocol;

    - Asynchronous Transfer Mode (ATM) subsystem;

    - B.A.T.M.A.N. meshing protocol;

    - Ethernet bridge;

    - CAN network layer;

    - Ceph Core library;

    - Ethtool driver;

    - HSR network protocol;

    - IEEE802154.4 network protocol;

    - IUCV driver;

    - KCM (Kernel Connection Multiplexor) sockets driver;

    - IEEE 802.15.4 subsystem;

    - Multipath TCP;

    - Open vSwitch;

    - Packet sockets;

    - Phonet protocol;

    - Qualcomm IPC Router (QRTR);

    - RDS protocol;

    - RxRPC session sockets;

    - SMC sockets;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - VMware vSockets driver;

    - X.25 network layer;

    - eXpress Data Path;

    - AppArmor security module;

    - Integrity Measurement Architecture(IMA) framework;

    - SELinux security module;

    - ALSA framework;

    - HD-audio driver;

    - QCOM ASoC drivers;

    - Simple audio multiplexer codec driver;

    - Texas InstrumentS Audio (ASoC/HDA) drivers;

    - SoC Audio for Freescale CPUs drivers;

    - Amlogic Meson SoC drivers;

    - SOF drivers;

    - NVIDIA Tegra ASoC drivers;

    - USB sound devices;

    - Perf tools;

    - KVM subsystem; (CVE-2025-37807, CVE-2026-23265, CVE-2026-43022, CVE-2026-46321, CVE-2026-46322,     CVE-2026-52917, CVE-2026-52923, CVE-2026-52927, CVE-2026-52929, CVE-2026-52935, CVE-2026-52942,     CVE-2026-52943, CVE-2026-52947, CVE-2026-52994, CVE-2026-53136, CVE-2026-53137, CVE-2026-53138,     CVE-2026-53143, CVE-2026-53146, CVE-2026-53147, CVE-2026-53149, CVE-2026-53156, CVE-2026-53157,     CVE-2026-53160, CVE-2026-53161, CVE-2026-53184, CVE-2026-53189, CVE-2026-53194, CVE-2026-53195,     CVE-2026-53199, CVE-2026-53202, CVE-2026-53205, CVE-2026-53209, CVE-2026-53223, CVE-2026-53229,     CVE-2026-53253, CVE-2026-53255, CVE-2026-53267, CVE-2026-53268, CVE-2026-53272, CVE-2026-53329,     CVE-2026-53330, CVE-2026-53356, CVE-2026-53362, CVE-2026-53365, CVE-2026-53366, CVE-2026-53381,     CVE-2026-53383, CVE-2026-53387, CVE-2026-53388, CVE-2026-53389, CVE-2026-53390, CVE-2026-53391,     CVE-2026-53392, CVE-2026-53397, CVE-2026-53400, CVE-2026-53401, CVE-2026-53402, CVE-2026-63794,     CVE-2026-63802, CVE-2026-63803, CVE-2026-63805, CVE-2026-63806, CVE-2026-63809, CVE-2026-63812,     CVE-2026-63814, CVE-2026-63816, CVE-2026-63817, CVE-2026-63819, CVE-2026-63823, CVE-2026-63824,     CVE-2026-63827, CVE-2026-63833, CVE-2026-63867, CVE-2026-63869, CVE-2026-63870, CVE-2026-63875,     CVE-2026-63879, CVE-2026-63881, CVE-2026-63884, CVE-2026-63889, CVE-2026-63909, CVE-2026-63913,     CVE-2026-63920, CVE-2026-63925, CVE-2026-63927, CVE-2026-63930, CVE-2026-63942, CVE-2026-63954,     CVE-2026-63968, CVE-2026-63970, CVE-2026-63971, CVE-2026-63985, CVE-2026-64002, CVE-2026-64003,     CVE-2026-64004, CVE-2026-64005, CVE-2026-64009, CVE-2026-64017, CVE-2026-64023, CVE-2026-64026,     CVE-2026-64036, CVE-2026-64095, CVE-2026-64123, CVE-2026-64188, CVE-2026-64189, CVE-2026-64210,     CVE-2026-64222, CVE-2026-64239, CVE-2026-64242, CVE-2026-64243, CVE-2026-64245, CVE-2026-64246,     CVE-2026-64266, CVE-2026-64270, CVE-2026-64271, CVE-2026-64272, CVE-2026-64273, CVE-2026-64274,     CVE-2026-64276, CVE-2026-64277, CVE-2026-64279, CVE-2026-64283, CVE-2026-64286, CVE-2026-64287,     CVE-2026-64296, CVE-2026-64298, CVE-2026-64299, CVE-2026-64304, CVE-2026-64312, CVE-2026-64317,     CVE-2026-64318, CVE-2026-64322, CVE-2026-64323, CVE-2026-64324, CVE-2026-64333, CVE-2026-64368,     CVE-2026-64372, CVE-2026-64374, CVE-2026-64375, CVE-2026-64378, CVE-2026-64379, CVE-2026-64380,     CVE-2026-64388, CVE-2026-64389, CVE-2026-64395, CVE-2026-64398, CVE-2026-64401, CVE-2026-64402,     CVE-2026-64403, CVE-2026-64411, CVE-2026-64412, CVE-2026-64413, CVE-2026-64418, CVE-2026-64420,     CVE-2026-64422, CVE-2026-64423, CVE-2026-64430, CVE-2026-64432, CVE-2026-64435, CVE-2026-64436,     CVE-2026-64440, CVE-2026-64442, CVE-2026-64443, CVE-2026-64444, CVE-2026-64448, CVE-2026-64449,     CVE-2026-64452, CVE-2026-64456, CVE-2026-64463, CVE-2026-64468, CVE-2026-64469, CVE-2026-64481,     CVE-2026-64496, CVE-2026-64524, CVE-2026-64532, CVE-2026-64533, CVE-2026-64536, CVE-2026-64539,     CVE-2026-64540, CVE-2026-64543, CVE-2026-64545, CVE-2026-64546, CVE-2026-64547, CVE-2026-64550,     CVE-2026-64556, CVE-2026-64560, CVE-2026-64563, CVE-2026-64567, CVE-2026-64568, CVE-2026-64570,     CVE-2026-64574, CVE-2026-64576, CVE-2026-64577, CVE-2026-64578, CVE-2026-64580, CVE-2026-64581,     CVE-2026-64582, CVE-2026-64583, CVE-2026-64584, CVE-2026-64585, CVE-2026-64599, CVE-2026-64600,     CVE-2026-68091, CVE-2026-68096, CVE-2026-68097, CVE-2026-68098, CVE-2026-68100, CVE-2026-68104,     CVE-2026-68106, CVE-2026-68107, CVE-2026-68108, CVE-2026-68116, CVE-2026-68118, CVE-2026-68119,     CVE-2026-68121, CVE-2026-68125, CVE-2026-68129, CVE-2026-68131, CVE-2026-68140, CVE-2026-68141,     CVE-2026-68142, CVE-2026-68143, CVE-2026-68145, CVE-2026-68148, CVE-2026-68149, CVE-2026-68153,     CVE-2026-68155, CVE-2026-68157, CVE-2026-68178, CVE-2026-68179, CVE-2026-68189, CVE-2026-68192,     CVE-2026-68196, CVE-2026-68199, CVE-2026-68202, CVE-2026-68204, CVE-2026-68216, CVE-2026-68219,     CVE-2026-68222, CVE-2026-68236, CVE-2026-68245, CVE-2026-68253, CVE-2026-68255, CVE-2026-68258,     CVE-2026-68260, CVE-2026-68262, CVE-2026-68263, CVE-2026-68266, CVE-2026-68273, CVE-2026-68284,     CVE-2026-68287, CVE-2026-68290, CVE-2026-68293, CVE-2026-68294, CVE-2026-68297, CVE-2026-68299,     CVE-2026-68314, CVE-2026-68315, CVE-2026-68320, CVE-2026-68322, CVE-2026-68323, CVE-2026-68326,     CVE-2026-68329, CVE-2026-68335, CVE-2026-68338, CVE-2026-68340, CVE-2026-68348, CVE-2026-68352,     CVE-2026-68353, CVE-2026-68354, CVE-2026-68370, CVE-2026-68371, CVE-2026-68373, CVE-2026-68376,     CVE-2026-68377, CVE-2026-68383, CVE-2026-68389, CVE-2026-68391, CVE-2026-68392, CVE-2026-68397,     CVE-2026-68398, CVE-2026-68399, CVE-2026-68400, CVE-2026-68401, CVE-2026-68402, CVE-2026-68404,     CVE-2026-68408, CVE-2026-68409, CVE-2026-68414, CVE-2026-68417, CVE-2026-68419, CVE-2026-68425,     CVE-2026-68432, CVE-2026-68433, CVE-2026-68442, CVE-2026-68445, CVE-2026-68446, CVE-2026-68447,     CVE-2026-68451, CVE-2026-68452, CVE-2026-68453, CVE-2026-68454, CVE-2026-68466, CVE-2026-68467,     CVE-2026-68471, CVE-2026-68474, CVE-2026-68479, CVE-2026-72005, CVE-2026-72009, CVE-2026-72012,     CVE-2026-72019, CVE-2026-72021, CVE-2026-72024, CVE-2026-72029, CVE-2026-72035, CVE-2026-72036,     CVE-2026-72045, CVE-2026-72049, CVE-2026-72051, CVE-2026-72052, CVE-2026-72053, CVE-2026-72054,     CVE-2026-72055, CVE-2026-72057, CVE-2026-72061, CVE-2026-72066, CVE-2026-72067, CVE-2026-72072,     CVE-2026-72089, CVE-2026-72099, CVE-2026-72102, CVE-2026-72105, CVE-2026-72107, CVE-2026-72108,     CVE-2026-72109, CVE-2026-72110, CVE-2026-72113, CVE-2026-72114, CVE-2026-72115, CVE-2026-72116,     CVE-2026-72117, CVE-2026-72118, CVE-2026-72119, CVE-2026-72120, CVE-2026-72121, CVE-2026-72122,     CVE-2026-72123, CVE-2026-72133, CVE-2026-72135, CVE-2026-72136, CVE-2026-72144, CVE-2026-72146,     CVE-2026-72148, CVE-2026-72149, CVE-2026-72157, CVE-2026-72160, CVE-2026-72162, CVE-2026-72164,     CVE-2026-72165, CVE-2026-72170, CVE-2026-72171, CVE-2026-72172, CVE-2026-72175, CVE-2026-72181,     CVE-2026-72195, CVE-2026-72196, CVE-2026-72197, CVE-2026-72213, CVE-2026-72225, CVE-2026-72227,     CVE-2026-72231, CVE-2026-72232, CVE-2026-72233, CVE-2026-72235, CVE-2026-72242, CVE-2026-72243,     CVE-2026-72244, CVE-2026-72247, CVE-2026-72250, CVE-2026-72252, CVE-2026-72253, CVE-2026-72254,     CVE-2026-72261, CVE-2026-72262, CVE-2026-72282, CVE-2026-72284, CVE-2026-72297, CVE-2026-72298,     CVE-2026-72301, CVE-2026-72302, CVE-2026-72304, CVE-2026-72310, CVE-2026-72312, CVE-2026-72314,     CVE-2026-72330, CVE-2026-72334, CVE-2026-72335, CVE-2026-72338, CVE-2026-72340, CVE-2026-72342,     CVE-2026-72343, CVE-2026-72347, CVE-2026-72350, CVE-2026-72352, CVE-2026-72369, CVE-2026-72371,     CVE-2026-72373, CVE-2026-72374, CVE-2026-72375, CVE-2026-72378, CVE-2026-72382, CVE-2026-72389,     CVE-2026-72390, CVE-2026-72397, CVE-2026-72400, CVE-2026-72404, CVE-2026-72405, CVE-2026-72406,     CVE-2026-72409, CVE-2026-72410, CVE-2026-72416, CVE-2026-72418, CVE-2026-72419, CVE-2026-72420,     CVE-2026-72423, CVE-2026-72425, CVE-2026-72427, CVE-2026-72435, CVE-2026-72438, CVE-2026-72440,     CVE-2026-72444, CVE-2026-72449, CVE-2026-72450, CVE-2026-72459, CVE-2026-72460, CVE-2026-72464,     CVE-2026-72469, CVE-2026-72470, CVE-2026-72476, CVE-2026-72478, CVE-2026-72480, CVE-2026-72483,     CVE-2026-72485, CVE-2026-72492, CVE-2026-72502, CVE-2026-74256, CVE-2026-74257, CVE-2026-74258,     CVE-2026-74262, CVE-2026-74270, CVE-2026-74281, CVE-2026-74282, CVE-2026-74283, CVE-2026-74288,     CVE-2026-74289, CVE-2026-74292, CVE-2026-74293, CVE-2026-74294, CVE-2026-74295, CVE-2026-74296,     CVE-2026-74297, CVE-2026-74300, CVE-2026-74312, CVE-2026-74313, CVE-2026-74314, CVE-2026-74317,     CVE-2026-74321, CVE-2026-74330, CVE-2026-74334, CVE-2026-74338, CVE-2026-74340, CVE-2026-74341,     CVE-2026-74344, CVE-2026-74347, CVE-2026-74349, CVE-2026-74356, CVE-2026-74359, CVE-2026-74363,     CVE-2026-74365, CVE-2026-74374, CVE-2026-74375, CVE-2026-74377, CVE-2026-74378, CVE-2026-74380,     CVE-2026-74385, CVE-2026-74387, CVE-2026-74388, CVE-2026-74390, CVE-2026-74397, CVE-2026-74438,     CVE-2026-74443, CVE-2026-74444, CVE-2026-74446, CVE-2026-74450, CVE-2026-74453, CVE-2026-74454,     CVE-2026-74456, CVE-2026-74461, CVE-2026-74465, CVE-2026-74467, CVE-2026-74469, CVE-2026-74470,     CVE-2026-74471, CVE-2026-74479, CVE-2026-74481, CVE-2026-74482, CVE-2026-74485, CVE-2026-74488,     CVE-2026-74490, CVE-2026-74492, CVE-2026-74496, CVE-2026-74497, CVE-2026-74507, CVE-2026-74508,     CVE-2026-74509, CVE-2026-74510, CVE-2026-74512, CVE-2026-74515, CVE-2026-74516, CVE-2026-74518,     CVE-2026-74519, CVE-2026-74522, CVE-2026-74523, CVE-2026-74527, CVE-2026-74530, CVE-2026-74531,     CVE-2026-74533, CVE-2026-74534, CVE-2026-74535, CVE-2026-74536, CVE-2026-74537, CVE-2026-74540,     CVE-2026-74544, CVE-2026-74548, CVE-2026-74549, CVE-2026-74550, CVE-2026-74551, CVE-2026-74557,     CVE-2026-74563, CVE-2026-74564, CVE-2026-74565, CVE-2026-74567, CVE-2026-74572, CVE-2026-74574,     CVE-2026-74575, CVE-2026-74578, CVE-2026-74579, CVE-2026-74580, CVE-2026-74581, CVE-2026-74582,     CVE-2026-74583, CVE-2026-74584, CVE-2026-74586, CVE-2026-74587, CVE-2026-74588, CVE-2026-74589,     CVE-2026-74590, CVE-2026-74592, CVE-2026-74594, CVE-2026-74595, CVE-2026-74597, CVE-2026-74598,     CVE-2026-74601, CVE-2026-74603, CVE-2026-74604, CVE-2026-74605, CVE-2026-74606, CVE-2026-74607,     CVE-2026-74608, CVE-2026-74609, CVE-2026-74610, CVE-2026-74611, CVE-2026-74612, CVE-2026-74613,     CVE-2026-74614, CVE-2026-74615, CVE-2026-74616, CVE-2026-74621, CVE-2026-74624, CVE-2026-74625,     CVE-2026-74626, CVE-2026-74628, CVE-2026-74630, CVE-2026-74631, CVE-2026-74632, CVE-2026-74634,     CVE-2026-74635, CVE-2026-74637, CVE-2026-74641, CVE-2026-74646, CVE-2026-74647, CVE-2026-74648,     CVE-2026-74649, CVE-2026-74651, CVE-2026-74656, CVE-2026-74660, CVE-2026-74661, CVE-2026-74662,     CVE-2026-74663, CVE-2026-74666, CVE-2026-74667, CVE-2026-74668, CVE-2026-74669, CVE-2026-74670,     CVE-2026-74675, CVE-2026-74678, CVE-2026-74684, CVE-2026-74687, CVE-2026-74688, CVE-2026-74689,     CVE-2026-74690, CVE-2026-74691, CVE-2026-74692, CVE-2026-74695, CVE-2026-74696, CVE-2026-74697,     CVE-2026-74700, CVE-2026-74701, CVE-2026-74704, CVE-2026-74705, CVE-2026-74710, CVE-2026-74711,     CVE-2026-74713, CVE-2026-74714, CVE-2026-74715, CVE-2026-74717, CVE-2026-74720, CVE-2026-74723,     CVE-2026-74724, CVE-2026-74725, CVE-2026-74726, CVE-2026-74730, CVE-2026-74733, CVE-2026-74736,     CVE-2026-74737, CVE-2026-74739, CVE-2026-74743, CVE-2026-74744, CVE-2026-74746, CVE-2026-74747,     CVE-2026-74748, CVE-2026-74752, CVE-2026-80521, CVE-2026-80526, CVE-2026-80527, CVE-2026-80528,     CVE-2026-80536, CVE-2026-80540, CVE-2026-80541, CVE-2026-80547, CVE-2026-80548, CVE-2026-80549,     CVE-2026-80550, CVE-2026-80551, CVE-2026-80552, CVE-2026-80553, CVE-2026-80554, CVE-2026-80555,     CVE-2026-80556, CVE-2026-80557, CVE-2026-80558, CVE-2026-80559, CVE-2026-80560, CVE-2026-80561,     CVE-2026-80565, CVE-2026-80568, CVE-2026-80569, CVE-2026-80570, CVE-2026-80572, CVE-2026-80574,     CVE-2026-80576, CVE-2026-80578, CVE-2026-80579, CVE-2026-80580, CVE-2026-80583, CVE-2026-80584,     CVE-2026-80585, CVE-2026-80586, CVE-2026-80587, CVE-2026-80589, CVE-2026-80721, CVE-2026-80901,     CVE-2026-97509)

Tenable has extracted the preceding description block directly from the Ubuntu 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	名称	产品	系列	发布时间	最近更新时间	严重程度
376201	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1793786843)	Nessus	Alma Linux Local Security Checks	2026/11/5	2026/11/5	high
343048	Oracle Linux 8 / 9 : Unbreakable Enterprise kernel (ELSA-2026-500249)	Nessus	Oracle Linux Local Security Checks	2026/9/4	2026/10/21	high
374300	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1793370479)	Nessus	Rocky Linux Local Security Checks	2026/10/30	2026/10/30	high
377778	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel (NVIDIA Tegra) vulnerabilities (USN-8963-1)	Nessus	Ubuntu Local Security Checks	2026/11/9	2026/11/9	high
376715	EulerOS 2.0 SP12 : kernel (EulerOS-SA-2026-4488)	Nessus	Huawei Local Security Checks	2026/11/6	2026/11/6	high
337239	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-2057)	Nessus	Amazon Linux Local Security Checks	2026/8/18	2026/9/23	high
337158	Linux Distros Unpatched Vulnerability : CVE-2026-72108	Nessus	Misc.	2026/8/18	2026/11/7	high
374124	CentOS Linux 7 [TuxCare] Security Update: bpftool / kernel / kernel-debug / kernel-debug-devel / kernel-devel / etc Multiple Vulnerabilities (CENTOS7:CLSA-2026:1792976962)	Nessus	CentOS Local Security Checks	2026/10/30	2026/10/30	high
337224	Amazon Linux 2 : kernel (ALASKERNEL-5.10-2026-129)	Nessus	Amazon Linux Local Security Checks	2026/8/18	2026/9/10	high
339536	Amazon Linux 2 : kernel (ALASKERNEL-5.15-2026-113)	Nessus	Amazon Linux Local Security Checks	2026/8/25	2026/9/10	high
365457	Ubuntu 24.04 LTS : Linux kernel (NVIDIA Tegra) vulnerabilities (USN-8886-1)	Nessus	Ubuntu Local Security Checks	2026/10/13	2026/10/13	high
365463	Ubuntu 26.04 LTS : Linux kernel (OEM) vulnerabilities (USN-8889-1)	Nessus	Ubuntu Local Security Checks	2026/10/13	2026/10/13	medium

检测

插件搜索

high

high

high

high

high

high

high

high

high

high

high

medium