In the Linux kernel, the following vulnerability has been resolved: KVM: x86: hyper-v: Bound the bank index when querying sparse banks When checking if a VP ID is included in a sparse bank set, explicitly check that the ID can actually be contained in a sparse bank (the TLFS allows for a maximum of 64 banks of 64 vCPUs each). When handling a paravirtual TLB flush for L2, the VP ID is copied verbatim from the enlightened VMCS, without any bounds check, i.e. isn't guaranteed to be under the limit of 4096. Failure to check the bounds of the VP ID leads to an out-of-bounds read when testing the sparse bank, and super strictly speaking could lead to KVM performing an unnecessary TLB flush for an L2 vCPU. ================================================================== BUG: KASAN: use-after-free in hv_is_vp_in_sparse_set+0x85/0x100 [kvm] Read of size 8 at addr ffff88811ba5f598 by task hyperv_evmcs/2802 CPU: 12 UID: 1000 PID: 2802 Comm: hyperv_evmcs Not tainted 7.1.0-rc2 #7 PREEMPT Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 Call Trace: <TASK> dump_stack_lvl+0x51/0x60 print_report+0xcb/0x5d0 kasan_report+0xb4/0xe0 kasan_check_range+0x35/0x1b0 hv_is_vp_in_sparse_set+0x85/0x100 [kvm] kvm_hv_flush_tlb+0xe9e/0x16c0 [kvm] kvm_hv_hypercall+0xe6b/0x1e60 [kvm] vmx_handle_exit+0x485/0x1b60 [kvm_intel] kvm_arch_vcpu_ioctl_run+0x22e3/0x5070 [kvm] kvm_vcpu_ioctl+0x5d0/0x10c0 [kvm] __x64_sys_ioctl+0x129/0x1a0 do_syscall_64+0xb9/0xcf0 entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f0e62d1a9bf </TASK> The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffffffffffffffff pfn:0x11ba5f flags: 0x4000000000000000(zone=1) raw: 4000000000000000 0000000000000000 00000000ffffffff 0000000000000000 raw: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected Memory state around the buggy address: ffff88811ba5f480: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88811ba5f500: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff88811ba5f580: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88811ba5f600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88811ba5f680: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== Disabling lock debugging due to kernel taint Opportunistically add a compile time assertion to ensure the maximum number of sparse banks exactly matches the number of possible bits in the passed in mask. [sean: add KASAN splat, drop comment, add assert, massage changelog]

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

    It was discovered that some Arm processors could complete a broadcast translation lookaside buffer (TLB)     invalidation before memory writes made through the invalidated translation were globally observed. A local     attacker could possibly use this to write to memory after permission to do so had been revoked, bypassing     memory protections or escalating privileges. (CVE-2025-10263)

    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:

    - ARM64 architecture;

    - User-space API (UAPI);

    - Kernel build system;

    - ARM32 architecture;

    - RISC-V architecture;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Compute Acceleration Framework;

    - Intel NPU Driver;

    - ACPI drivers;

    - Android drivers;

    - Drivers core;

    - Compressed RAM block device driver;

    - Bluetooth drivers;

    - Character device driver;

    - Hardware random number generator core;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - Buffer Sharing and Synchronization framework;

    - Intel Stratix 10 firmware drivers;

    - FPGA Framework;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - CoreSight HW tracing drivers;

    - I2C subsystem;

    - IIO subsystem;

    - IIO ADC drivers;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Mouse) drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - Multiple devices driver;

    - Media drivers;

    - Multifunction device drivers;

    - Fastrpc Driver;

    - MMC subsystem;

    - Ethernet bonding driver;

    - Network drivers;

    - Mellanox network drivers;

    - MediaTek network drivers;

    - NTB driver;

    - NVME drivers;

    - NVMEM (Non Volatile Memory) drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - System reset/shutdown drivers;

    - Power sequencing drivers;

    - PTP clock framework;

    - Voltage and Current Regulator drivers;

    - RPMSG subsystem;

    - SLIMbus drivers;

    - SPI subsystem;

    - Media staging drivers;

    - Realtek RTL8723BS SDIO drivers;

    - VME bus staging drivers;

    - Trusted Execution Environment drivers;

    - TTY drivers;

    - Cadence USB3 driver;

    - ULPI bus;

    - USB core drivers;

    - DesignWare USB3 driver;

    - Faraday FOTG210 USB2 dual-role controller driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - USB ChaosKey driver;

    - Siemens ID Mouse USB driver;

    - IOWarrior USB driver;

    - LD Didactic USB driver;

    - LEGO USB Tower driver;

    - Intel USBIO USB I/O expander driver;

    - USS720 USB parallel port adapter driver;

    - MediaTek USB3 DRD driver;

    - USB Serial drivers;

    - USB Type-C Port Controller Manager driver;

    - USB Type-C Connector System Software Interface driver;

    - USB over IP driver;

    - VFIO drivers;

    - Framebuffer layer;

    - Virtio drivers;

    - BTRFS file system;

    - EROFS file system;

    - exFAT file system;

    - F2FS file system;

    - File systems infrastructure;

    - FUSE (File system in Userspace);

    - GFS2 file system;

    - HFS file system;

    - HFS+ file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - NTFS3 file system;

    - OCFS2 file system;

    - Proc file system;

    - SMB network file system;

    - UDF file system;

    - XFS file system;

    - Key management;

    - BPF subsystem;

    - Memory management;

    - Software nodes and device properties;

    - Glob pattern matching library;

    - Memory Management;

    - KVM subsystem;

    - Mellanox drivers;

    - Restartable sequences system call mechanism;

    - Socket messages infrastructure;

    - Network traffic control;

    - Bluetooth subsystem;

    - Netfilter;

    - Networking core;

    - Network sockets;

    - TCP network protocol;

    - io_uring subsystem;

    - IPC subsystem;

    - Audit subsystem;

    - Perf events;

    - Kernel fork() syscall;

    - Locking primitives;

    - Kernel module support;

    - Scheduler infrastructure;

    - Signal handling mechanism;

    - Timer subsystem;

    - Tracing infrastructure;

    - Debug objects infrastructure;

    - 6LoWPAN network protocol;

    - IEEE 802 network protocols;

    - 9P file system network protocol;

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

    - Ethernet bridge;

    - Devlink API;

    - HSR network protocol;

    - IEEE802154.4 network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - XFRM subsystem;

    - L2TP protocol;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Multipath TCP;

    - NetLabel subsystem;

    - Open vSwitch;

    - Phonet protocol;

    - Qualcomm IPC Router (QRTR);

    - RDS protocol;

    - SCTP protocol;

    - SMC sockets;

    - TIPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - VMware vSockets driver;

    - Wireless networking;

    - eXpress Data Path;

    - AppArmor security module;

    - Linux Security Modules (LSM) Framework;

    - Apple Onboard Audio ALSA driver;

    - ALSA framework;

    - FireWire sound drivers;

    - HD-audio driver;

    - Gravis UltraSound ALSA driver;

    - C-Media CMI8x38 ALSA driver;

    - ESS Solo-1 ALSA driver;

    - ICE1712/ICE1724 (Envy24) ALSA driver;

    - Yamaha YMFPCI ALSA driver;

    - Wolfson Microelectronics audio codecs;

    - SoundWire (SDCA) ASoC drivers;

    - USB sound devices;

    - Virtio sound driver; (CVE-2026-52908, CVE-2026-52909, CVE-2026-52910, CVE-2026-52917, CVE-2026-52929,     CVE-2026-52930, CVE-2026-52935, CVE-2026-52938, CVE-2026-52939, CVE-2026-52940, CVE-2026-52942,     CVE-2026-52947, CVE-2026-52948, CVE-2026-53132, CVE-2026-53133, CVE-2026-53134, CVE-2026-53135,     CVE-2026-53136, CVE-2026-53137, CVE-2026-53138, CVE-2026-53139, CVE-2026-53140, CVE-2026-53141,     CVE-2026-53142, CVE-2026-53143, CVE-2026-53144, CVE-2026-53145, CVE-2026-53152, CVE-2026-53153,     CVE-2026-53154, CVE-2026-53155, CVE-2026-53156, CVE-2026-53157, CVE-2026-53158, CVE-2026-53159,     CVE-2026-53160, CVE-2026-53161, CVE-2026-53162, CVE-2026-53163, CVE-2026-53164, CVE-2026-53165,     CVE-2026-53167, CVE-2026-53168, CVE-2026-53169, CVE-2026-53170, CVE-2026-53171, CVE-2026-53172,     CVE-2026-53173, CVE-2026-53177, CVE-2026-53178, CVE-2026-53179, CVE-2026-53180, CVE-2026-53181,     CVE-2026-53182, CVE-2026-53183, CVE-2026-53184, CVE-2026-53185, CVE-2026-53187, CVE-2026-53188,     CVE-2026-53189, CVE-2026-53190, CVE-2026-53191, CVE-2026-53192, CVE-2026-53193, CVE-2026-53194,     CVE-2026-53195, CVE-2026-53196, CVE-2026-53197, CVE-2026-53198, CVE-2026-53199, CVE-2026-53200,     CVE-2026-53201, CVE-2026-53202, CVE-2026-53203, CVE-2026-53204, CVE-2026-53205, CVE-2026-53206,     CVE-2026-53207, CVE-2026-53208, CVE-2026-53209, CVE-2026-53210, CVE-2026-53211, CVE-2026-53213,     CVE-2026-53214, CVE-2026-53217, CVE-2026-53218, CVE-2026-53219, CVE-2026-53220, CVE-2026-53222,     CVE-2026-53223, CVE-2026-53226, CVE-2026-53227, CVE-2026-53229, CVE-2026-53230, CVE-2026-53231,     CVE-2026-53232, CVE-2026-53233, CVE-2026-53234, CVE-2026-53235, CVE-2026-53236, CVE-2026-53237,     CVE-2026-53238, CVE-2026-53239, CVE-2026-53240, CVE-2026-53241, CVE-2026-53242, CVE-2026-53243,     CVE-2026-53244, CVE-2026-53245, CVE-2026-53248, CVE-2026-53249, CVE-2026-53250, CVE-2026-53251,     CVE-2026-53252, CVE-2026-53253, CVE-2026-53254, CVE-2026-53255, CVE-2026-53256, CVE-2026-53257,     CVE-2026-53258, CVE-2026-53259, CVE-2026-53261, CVE-2026-53262, CVE-2026-53263, CVE-2026-53264,     CVE-2026-53265, CVE-2026-53266, CVE-2026-53267, CVE-2026-53268, CVE-2026-53269, CVE-2026-53270,     CVE-2026-53271, CVE-2026-53272, CVE-2026-53273, CVE-2026-53274, CVE-2026-53275, CVE-2026-53276,     CVE-2026-53325, CVE-2026-53326, CVE-2026-53327, CVE-2026-53328, CVE-2026-53329, CVE-2026-53330,     CVE-2026-53331, CVE-2026-53332, CVE-2026-53333, CVE-2026-53334, CVE-2026-53335, CVE-2026-53336,     CVE-2026-53337, CVE-2026-53338, CVE-2026-53339, CVE-2026-53340, CVE-2026-53341, CVE-2026-53342,     CVE-2026-53343, CVE-2026-53344, CVE-2026-53345, CVE-2026-53346, CVE-2026-53347, CVE-2026-53348,     CVE-2026-53349, CVE-2026-53350, CVE-2026-53351, CVE-2026-53352, CVE-2026-53353, CVE-2026-53354,     CVE-2026-53355, CVE-2026-53356, CVE-2026-53361, CVE-2026-53362, CVE-2026-53363, CVE-2026-53366,     CVE-2026-53381, CVE-2026-53382, CVE-2026-53383, CVE-2026-53384, CVE-2026-53385, CVE-2026-53386,     CVE-2026-53387, CVE-2026-53388, CVE-2026-53389, CVE-2026-53390, CVE-2026-53391, CVE-2026-53392,     CVE-2026-53393, CVE-2026-53394, CVE-2026-53395, CVE-2026-53396, CVE-2026-53397, CVE-2026-53398,     CVE-2026-53399, CVE-2026-53400, CVE-2026-53401, CVE-2026-53402, CVE-2026-53403, CVE-2026-63794,     CVE-2026-63795, CVE-2026-63796, CVE-2026-63797, CVE-2026-63798, CVE-2026-63799, CVE-2026-63800,     CVE-2026-63801, CVE-2026-63802, CVE-2026-63803, CVE-2026-63804, CVE-2026-63805, CVE-2026-63806,     CVE-2026-63807, CVE-2026-63808, CVE-2026-63809, CVE-2026-63810, CVE-2026-63811, CVE-2026-63812,     CVE-2026-63813, CVE-2026-63814, CVE-2026-63815, CVE-2026-63816, CVE-2026-63817, CVE-2026-63818,     CVE-2026-63819, CVE-2026-63820, CVE-2026-63821, CVE-2026-63822, CVE-2026-63823, CVE-2026-63824,     CVE-2026-63825, CVE-2026-63826, CVE-2026-63827, CVE-2026-63828, CVE-2026-63829, CVE-2026-63830,     CVE-2026-63831, CVE-2026-63832, CVE-2026-63833, CVE-2026-63834, CVE-2026-63835, CVE-2026-63836,     CVE-2026-63867, CVE-2026-63868, CVE-2026-63869, CVE-2026-63870, CVE-2026-63871, CVE-2026-63873,     CVE-2026-63874, CVE-2026-64187, CVE-2026-64188, CVE-2026-64189, CVE-2026-64191, CVE-2026-64192,     CVE-2026-64205, CVE-2026-64206, CVE-2026-64207, CVE-2026-64244, CVE-2026-64245, CVE-2026-64246,     CVE-2026-64247, CVE-2026-64249, CVE-2026-64251, CVE-2026-64253, CVE-2026-64254, CVE-2026-64255,     CVE-2026-64256, CVE-2026-64258, CVE-2026-64259, CVE-2026-64260, CVE-2026-64261, CVE-2026-64262,     CVE-2026-64263, CVE-2026-64264, CVE-2026-64265, CVE-2026-64266, CVE-2026-64267, CVE-2026-64268,     CVE-2026-64269, CVE-2026-64270, CVE-2026-64271, CVE-2026-64272, CVE-2026-64273, CVE-2026-64274,     CVE-2026-64275, CVE-2026-64276, CVE-2026-64277, CVE-2026-64278, CVE-2026-64279, CVE-2026-64280,     CVE-2026-64282, CVE-2026-64283, CVE-2026-64284, CVE-2026-64285, CVE-2026-64286, CVE-2026-64287,     CVE-2026-64288, CVE-2026-64289, CVE-2026-64290, CVE-2026-64291, CVE-2026-64292, CVE-2026-64293,     CVE-2026-64294, CVE-2026-64295, CVE-2026-64296, CVE-2026-64297, CVE-2026-64298, CVE-2026-64299,     CVE-2026-64300, CVE-2026-64301, CVE-2026-64302, CVE-2026-64303, CVE-2026-64304, CVE-2026-64305,     CVE-2026-64306, CVE-2026-64307, CVE-2026-64308, CVE-2026-64309, CVE-2026-64310, CVE-2026-64312,     CVE-2026-64313, CVE-2026-64314, CVE-2026-64315, CVE-2026-64316, CVE-2026-64317, CVE-2026-64318,     CVE-2026-64319, CVE-2026-64320, CVE-2026-64321, CVE-2026-64322, CVE-2026-64323, CVE-2026-64324,     CVE-2026-64325, CVE-2026-64326, CVE-2026-64327, CVE-2026-64328, CVE-2026-64329, CVE-2026-64330,     CVE-2026-64331, CVE-2026-64332, CVE-2026-64333, CVE-2026-64334, CVE-2026-64335, CVE-2026-64336,     CVE-2026-64337, CVE-2026-64338, CVE-2026-64339, CVE-2026-64340, CVE-2026-64341, CVE-2026-64342,     CVE-2026-64343, CVE-2026-64344, CVE-2026-64345, CVE-2026-64346, CVE-2026-64347, CVE-2026-64348,     CVE-2026-64350, CVE-2026-64351, CVE-2026-64352, CVE-2026-64353, CVE-2026-64354, CVE-2026-64355,     CVE-2026-64356, CVE-2026-64357, CVE-2026-64358, CVE-2026-64359, CVE-2026-64360, CVE-2026-64361,     CVE-2026-64362, CVE-2026-64363, CVE-2026-64364, CVE-2026-64365, CVE-2026-64366, CVE-2026-64367,     CVE-2026-64368, CVE-2026-64369, CVE-2026-64370, CVE-2026-64371, CVE-2026-64372, CVE-2026-64373,     CVE-2026-64374, CVE-2026-64375, CVE-2026-64376, CVE-2026-64377, CVE-2026-64378, CVE-2026-64379,     CVE-2026-64380, CVE-2026-64381, CVE-2026-64382, CVE-2026-64383, CVE-2026-64384, CVE-2026-64385,     CVE-2026-64386, CVE-2026-64387, CVE-2026-64388, CVE-2026-64389, CVE-2026-64390, CVE-2026-64391,     CVE-2026-64392, CVE-2026-64393, CVE-2026-64394, CVE-2026-64395, CVE-2026-64396, CVE-2026-64397,     CVE-2026-64398, CVE-2026-64399, CVE-2026-64400, CVE-2026-64401, CVE-2026-64402, CVE-2026-64403,     CVE-2026-64404, CVE-2026-64405, CVE-2026-64406, CVE-2026-64407, CVE-2026-64408, CVE-2026-64409,     CVE-2026-64410, CVE-2026-64411, CVE-2026-64412, CVE-2026-64413, CVE-2026-64414, CVE-2026-64415,     CVE-2026-64416, CVE-2026-64417, CVE-2026-64418, CVE-2026-64419, CVE-2026-64420, CVE-2026-64421,     CVE-2026-64422, CVE-2026-64423, CVE-2026-64424, CVE-2026-64425, CVE-2026-64426, CVE-2026-64428,     CVE-2026-64429, CVE-2026-64430, CVE-2026-64432, CVE-2026-64433, CVE-2026-64434, CVE-2026-64435,     CVE-2026-64436, CVE-2026-64438, CVE-2026-64439, CVE-2026-64440, CVE-2026-64441, CVE-2026-64442,     CVE-2026-64443, CVE-2026-64444, CVE-2026-64445, CVE-2026-64446, CVE-2026-64447, CVE-2026-64448,     CVE-2026-64449, CVE-2026-64450, CVE-2026-64451, CVE-2026-64452, CVE-2026-64453, CVE-2026-64454,     CVE-2026-64455, CVE-2026-64456, CVE-2026-64457, CVE-2026-64458, CVE-2026-64459, CVE-2026-64460,     CVE-2026-64461, CVE-2026-64462, CVE-2026-64463, CVE-2026-64464, CVE-2026-64465, CVE-2026-64466,     CVE-2026-64467, CVE-2026-64468, CVE-2026-64469, CVE-2026-64470, CVE-2026-64471, CVE-2026-64472,     CVE-2026-64473, CVE-2026-64474, CVE-2026-64475, CVE-2026-64476, CVE-2026-64477, CVE-2026-64478,     CVE-2026-64479, CVE-2026-64480, CVE-2026-64481, CVE-2026-64482, CVE-2026-64483, CVE-2026-64484,     CVE-2026-64485, CVE-2026-64486, CVE-2026-64487, CVE-2026-64488, CVE-2026-64489, CVE-2026-64490,     CVE-2026-64491, CVE-2026-64492, CVE-2026-64493, CVE-2026-64494, CVE-2026-64495, CVE-2026-64496,     CVE-2026-64497, CVE-2026-64499, CVE-2026-64500, CVE-2026-64501, CVE-2026-64502, CVE-2026-64503,     CVE-2026-64504, CVE-2026-64505, CVE-2026-64507, CVE-2026-64508, CVE-2026-64509, CVE-2026-64510,     CVE-2026-64511, CVE-2026-64512, CVE-2026-64513, CVE-2026-64514, CVE-2026-64529, CVE-2026-64536,     CVE-2026-64556, CVE-2026-64588, CVE-2026-64589, CVE-2026-64590, CVE-2026-64591, CVE-2026-64592,     CVE-2026-64593, CVE-2026-64594, CVE-2026-64596, CVE-2026-64597, CVE-2026-64598, CVE-2026-64599,     CVE-2026-64600, CVE-2026-64601, CVE-2026-64602, CVE-2026-64603, CVE-2026-64604, CVE-2026-68084,     CVE-2026-68085, CVE-2026-68087, CVE-2026-68088, CVE-2026-68089, CVE-2026-68090, CVE-2026-68091,     CVE-2026-68092, CVE-2026-68372, CVE-2026-68459, CVE-2026-68460, CVE-2026-68461, CVE-2026-74584,     CVE-2026-80591)

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.

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

    It was discovered that some Arm processors could complete a broadcast translation lookaside buffer (TLB)     invalidation before memory writes made through the invalidated translation were globally observed. A local     attacker could possibly use this to write to memory after permission to do so had been revoked, bypassing     memory protections or escalating privileges. (CVE-2025-10263)

    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:

    - ARM64 architecture;

    - User-space API (UAPI);

    - Kernel build system;

    - ARM32 architecture;

    - RISC-V architecture;

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Compute Acceleration Framework;

    - Intel NPU Driver;

    - ACPI drivers;

    - Android drivers;

    - Drivers core;

    - Compressed RAM block device driver;

    - Bluetooth drivers;

    - Character device driver;

    - Hardware random number generator core;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - Buffer Sharing and Synchronization framework;

    - Intel Stratix 10 firmware drivers;

    - FPGA Framework;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - CoreSight HW tracing drivers;

    - I2C subsystem;

    - IIO subsystem;

    - IIO ADC drivers;

    - InfiniBand drivers;

    - Input Device core drivers;

    - Input Device (Mouse) drivers;

    - IOMMU subsystem;

    - IRQ chip drivers;

    - Multiple devices driver;

    - Media drivers;

    - Multifunction device drivers;

    - Fastrpc Driver;

    - MMC subsystem;

    - Ethernet bonding driver;

    - Network drivers;

    - Mellanox network drivers;

    - MediaTek network drivers;

    - NTB driver;

    - NVME drivers;

    - NVMEM (Non Volatile Memory) drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - System reset/shutdown drivers;

    - Power sequencing drivers;

    - PTP clock framework;

    - Voltage and Current Regulator drivers;

    - RPMSG subsystem;

    - SLIMbus drivers;

    - SPI subsystem;

    - Media staging drivers;

    - Realtek RTL8723BS SDIO drivers;

    - VME bus staging drivers;

    - Trusted Execution Environment drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - Cadence USB3 driver;

    - ULPI bus;

    - DesignWare USB3 driver;

    - Faraday FOTG210 USB2 dual-role controller driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - USB ChaosKey driver;

    - Siemens ID Mouse USB driver;

    - IOWarrior USB driver;

    - LD Didactic USB driver;

    - LEGO USB Tower driver;

    - Intel USBIO USB I/O expander driver;

    - USS720 USB parallel port adapter driver;

    - MediaTek USB3 DRD driver;

    - USB Serial drivers;

    - USB Type-C Port Controller Manager driver;

    - USB Type-C Connector System Software Interface driver;

    - USB over IP driver;

    - VFIO drivers;

    - Framebuffer layer;

    - Virtio drivers;

    - BTRFS file system;

    - EROFS file system;

    - exFAT file system;

    - F2FS file system;

    - File systems infrastructure;

    - FUSE (File system in Userspace);

    - GFS2 file system;

    - HFS file system;

    - HFS+ file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - NTFS3 file system;

    - OCFS2 file system;

    - Proc file system;

    - SMB network file system;

    - UDF file system;

    - XFS file system;

    - Key management;

    - BPF subsystem;

    - Memory management;

    - Software nodes and device properties;

    - Glob pattern matching library;

    - Memory Management;

    - KVM subsystem;

    - Mellanox drivers;

    - Restartable sequences system call mechanism;

    - Socket messages infrastructure;

    - Network traffic control;

    - Bluetooth subsystem;

    - Netfilter;

    - Networking core;

    - Network sockets;

    - TCP network protocol;

    - io_uring subsystem;

    - IPC subsystem;

    - Audit subsystem;

    - Perf events;

    - Kernel fork() syscall;

    - Locking primitives;

    - Kernel module support;

    - Scheduler infrastructure;

    - Signal handling mechanism;

    - Timer subsystem;

    - Tracing infrastructure;

    - Debug objects infrastructure;

    - 6LoWPAN network protocol;

    - IEEE 802 network protocols;

    - 9P file system network protocol;

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

    - Ethernet bridge;

    - Devlink API;

    - HSR network protocol;

    - IEEE802154.4 network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - XFRM subsystem;

    - L2TP protocol;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Multipath TCP;

    - NetLabel subsystem;

    - Open vSwitch;

    - Phonet protocol;

    - Qualcomm IPC Router (QRTR);

    - RDS protocol;

    - SCTP protocol;

    - SMC sockets;

    - TIPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - VMware vSockets driver;

    - Wireless networking;

    - eXpress Data Path;

    - AppArmor security module;

    - Linux Security Modules (LSM) Framework;

    - Apple Onboard Audio ALSA driver;

    - ALSA framework;

    - FireWire sound drivers;

    - HD-audio driver;

    - Gravis UltraSound ALSA driver;

    - C-Media CMI8x38 ALSA driver;

    - ESS Solo-1 ALSA driver;

    - ICE1712/ICE1724 (Envy24) ALSA driver;

    - Yamaha YMFPCI ALSA driver;

    - Wolfson Microelectronics audio codecs;

    - SoundWire (SDCA) ASoC drivers;

    - USB sound devices;

    - Virtio sound driver; (CVE-2026-52908, CVE-2026-52909, CVE-2026-52910, CVE-2026-52917, CVE-2026-52929,     CVE-2026-52930, CVE-2026-52935, CVE-2026-52938, CVE-2026-52939, CVE-2026-52940, CVE-2026-52942,     CVE-2026-52947, CVE-2026-52948, CVE-2026-53132, CVE-2026-53133, CVE-2026-53134, CVE-2026-53135,     CVE-2026-53136, CVE-2026-53137, CVE-2026-53138, CVE-2026-53139, CVE-2026-53140, CVE-2026-53141,     CVE-2026-53142, CVE-2026-53143, CVE-2026-53144, CVE-2026-53145, CVE-2026-53146, CVE-2026-53147,     CVE-2026-53148, CVE-2026-53149, CVE-2026-53150, CVE-2026-53152, CVE-2026-53153, CVE-2026-53154,     CVE-2026-53155, CVE-2026-53156, CVE-2026-53157, CVE-2026-53158, CVE-2026-53159, CVE-2026-53160,     CVE-2026-53161, CVE-2026-53162, CVE-2026-53163, CVE-2026-53164, CVE-2026-53165, CVE-2026-53167,     CVE-2026-53168, CVE-2026-53169, CVE-2026-53170, CVE-2026-53171, CVE-2026-53172, CVE-2026-53173,     CVE-2026-53177, CVE-2026-53178, CVE-2026-53179, CVE-2026-53180, CVE-2026-53181, CVE-2026-53182,     CVE-2026-53183, CVE-2026-53184, CVE-2026-53185, CVE-2026-53187, CVE-2026-53188, CVE-2026-53189,     CVE-2026-53190, CVE-2026-53191, CVE-2026-53192, CVE-2026-53193, CVE-2026-53194, CVE-2026-53195,     CVE-2026-53196, CVE-2026-53197, CVE-2026-53198, CVE-2026-53199, CVE-2026-53200, CVE-2026-53201,     CVE-2026-53202, CVE-2026-53203, CVE-2026-53204, CVE-2026-53205, CVE-2026-53206, CVE-2026-53207,     CVE-2026-53208, CVE-2026-53209, CVE-2026-53210, CVE-2026-53211, CVE-2026-53213, CVE-2026-53214,     CVE-2026-53217, CVE-2026-53218, CVE-2026-53219, CVE-2026-53220, CVE-2026-53222, CVE-2026-53223,     CVE-2026-53226, CVE-2026-53227, CVE-2026-53229, CVE-2026-53230, CVE-2026-53231, CVE-2026-53232,     CVE-2026-53233, CVE-2026-53234, CVE-2026-53235, CVE-2026-53236, CVE-2026-53237, CVE-2026-53238,     CVE-2026-53239, CVE-2026-53240, CVE-2026-53241, CVE-2026-53242, CVE-2026-53243, CVE-2026-53244,     CVE-2026-53245, CVE-2026-53248, CVE-2026-53249, CVE-2026-53250, CVE-2026-53251, CVE-2026-53252,     CVE-2026-53253, CVE-2026-53254, CVE-2026-53255, CVE-2026-53256, CVE-2026-53257, CVE-2026-53258,     CVE-2026-53259, CVE-2026-53261, CVE-2026-53262, CVE-2026-53263, CVE-2026-53264, CVE-2026-53265,     CVE-2026-53266, CVE-2026-53267, CVE-2026-53268, CVE-2026-53269, CVE-2026-53270, CVE-2026-53271,     CVE-2026-53272, CVE-2026-53273, CVE-2026-53274, CVE-2026-53275, CVE-2026-53276, CVE-2026-53325,     CVE-2026-53326, CVE-2026-53327, CVE-2026-53328, CVE-2026-53329, CVE-2026-53330, CVE-2026-53331,     CVE-2026-53332, CVE-2026-53333, CVE-2026-53334, CVE-2026-53335, CVE-2026-53336, CVE-2026-53337,     CVE-2026-53338, CVE-2026-53339, CVE-2026-53340, CVE-2026-53341, CVE-2026-53342, CVE-2026-53343,     CVE-2026-53344, CVE-2026-53345, CVE-2026-53346, CVE-2026-53347, CVE-2026-53348, CVE-2026-53349,     CVE-2026-53350, CVE-2026-53351, CVE-2026-53352, CVE-2026-53353, CVE-2026-53354, CVE-2026-53355,     CVE-2026-53356, CVE-2026-53361, CVE-2026-53362, CVE-2026-53363, CVE-2026-53366, CVE-2026-53381,     CVE-2026-53382, CVE-2026-53383, CVE-2026-53384, CVE-2026-53385, CVE-2026-53386, CVE-2026-53387,     CVE-2026-53388, CVE-2026-53389, CVE-2026-53390, CVE-2026-53391, CVE-2026-53392, CVE-2026-53393,     CVE-2026-53394, CVE-2026-53395, CVE-2026-53396, CVE-2026-53397, CVE-2026-53398, CVE-2026-53399,     CVE-2026-53400, CVE-2026-53401, CVE-2026-53402, CVE-2026-53403, CVE-2026-63794, CVE-2026-63795,     CVE-2026-63796, CVE-2026-63797, CVE-2026-63798, CVE-2026-63799, CVE-2026-63800, CVE-2026-63801,     CVE-2026-63802, CVE-2026-63803, CVE-2026-63804, CVE-2026-63805, CVE-2026-63806, CVE-2026-63807,     CVE-2026-63808, CVE-2026-63809, CVE-2026-63810, CVE-2026-63811, CVE-2026-63812, CVE-2026-63813,     CVE-2026-63814, CVE-2026-63815, CVE-2026-63816, CVE-2026-63817, CVE-2026-63818, CVE-2026-63819,     CVE-2026-63820, CVE-2026-63821, CVE-2026-63822, CVE-2026-63823, CVE-2026-63824, CVE-2026-63825,     CVE-2026-63826, CVE-2026-63827, CVE-2026-63828, CVE-2026-63829, CVE-2026-63830, CVE-2026-63831,     CVE-2026-63832, CVE-2026-63833, CVE-2026-63834, CVE-2026-63835, CVE-2026-63836, CVE-2026-63867,     CVE-2026-63868, CVE-2026-63869, CVE-2026-63870, CVE-2026-63871, CVE-2026-63873, CVE-2026-63874,     CVE-2026-64187, CVE-2026-64188, CVE-2026-64189, CVE-2026-64191, CVE-2026-64192, CVE-2026-64205,     CVE-2026-64206, CVE-2026-64207, CVE-2026-64244, CVE-2026-64245, CVE-2026-64246, CVE-2026-64247,     CVE-2026-64249, CVE-2026-64251, CVE-2026-64253, CVE-2026-64254, CVE-2026-64255, CVE-2026-64256,     CVE-2026-64258, CVE-2026-64259, CVE-2026-64260, CVE-2026-64261, CVE-2026-64262, CVE-2026-64263,     CVE-2026-64264, CVE-2026-64265, CVE-2026-64266, CVE-2026-64267, CVE-2026-64268, CVE-2026-64269,     CVE-2026-64270, CVE-2026-64271, CVE-2026-64272, CVE-2026-64273, CVE-2026-64274, CVE-2026-64275,     CVE-2026-64276, CVE-2026-64277, CVE-2026-64278, CVE-2026-64279, CVE-2026-64280, CVE-2026-64282,     CVE-2026-64283, CVE-2026-64284, CVE-2026-64285, CVE-2026-64286, CVE-2026-64287, CVE-2026-64288,     CVE-2026-64289, CVE-2026-64290, CVE-2026-64291, CVE-2026-64292, CVE-2026-64293, CVE-2026-64294,     CVE-2026-64295, CVE-2026-64296, CVE-2026-64297, CVE-2026-64298, CVE-2026-64299, CVE-2026-64300,     CVE-2026-64301, CVE-2026-64302, CVE-2026-64303, CVE-2026-64304, CVE-2026-64305, CVE-2026-64306,     CVE-2026-64307, CVE-2026-64308, CVE-2026-64309, CVE-2026-64310, CVE-2026-64312, CVE-2026-64313,     CVE-2026-64314, CVE-2026-64315, CVE-2026-64316, CVE-2026-64317, CVE-2026-64318, CVE-2026-64319,     CVE-2026-64320, CVE-2026-64321, CVE-2026-64322, CVE-2026-64323, CVE-2026-64324, CVE-2026-64325,     CVE-2026-64326, CVE-2026-64327, CVE-2026-64328, CVE-2026-64329, CVE-2026-64330, CVE-2026-64331,     CVE-2026-64332, CVE-2026-64333, CVE-2026-64334, CVE-2026-64335, CVE-2026-64336, CVE-2026-64337,     CVE-2026-64338, CVE-2026-64339, CVE-2026-64340, CVE-2026-64341, CVE-2026-64342, CVE-2026-64343,     CVE-2026-64344, CVE-2026-64345, CVE-2026-64346, CVE-2026-64347, CVE-2026-64348, CVE-2026-64350,     CVE-2026-64351, CVE-2026-64352, CVE-2026-64353, CVE-2026-64354, CVE-2026-64355, CVE-2026-64356,     CVE-2026-64357, CVE-2026-64358, CVE-2026-64359, CVE-2026-64360, CVE-2026-64361, CVE-2026-64362,     CVE-2026-64363, CVE-2026-64364, CVE-2026-64365, CVE-2026-64366, CVE-2026-64367, CVE-2026-64368,     CVE-2026-64369, CVE-2026-64370, CVE-2026-64371, CVE-2026-64372, CVE-2026-64373, CVE-2026-64374,     CVE-2026-64375, CVE-2026-64376, CVE-2026-64377, CVE-2026-64378, CVE-2026-64379, CVE-2026-64380,     CVE-2026-64381, CVE-2026-64382, CVE-2026-64383, CVE-2026-64384, CVE-2026-64385, CVE-2026-64386,     CVE-2026-64387, CVE-2026-64388, CVE-2026-64389, CVE-2026-64390, CVE-2026-64391, CVE-2026-64392,     CVE-2026-64393, CVE-2026-64394, CVE-2026-64395, CVE-2026-64396, CVE-2026-64397, CVE-2026-64398,     CVE-2026-64399, CVE-2026-64400, CVE-2026-64401, CVE-2026-64402, CVE-2026-64403, CVE-2026-64404,     CVE-2026-64405, CVE-2026-64406, CVE-2026-64407, CVE-2026-64408, CVE-2026-64409, CVE-2026-64410,     CVE-2026-64411, CVE-2026-64412, CVE-2026-64413, CVE-2026-64414, CVE-2026-64415, CVE-2026-64416,     CVE-2026-64417, CVE-2026-64418, CVE-2026-64419, CVE-2026-64420, CVE-2026-64421, CVE-2026-64422,     CVE-2026-64423, CVE-2026-64424, CVE-2026-64425, CVE-2026-64426, CVE-2026-64428, CVE-2026-64429,     CVE-2026-64430, CVE-2026-64432, CVE-2026-64433, CVE-2026-64434, CVE-2026-64435, CVE-2026-64436,     CVE-2026-64438, CVE-2026-64439, CVE-2026-64440, CVE-2026-64441, CVE-2026-64442, CVE-2026-64443,     CVE-2026-64444, CVE-2026-64445, CVE-2026-64446, CVE-2026-64447, CVE-2026-64448, CVE-2026-64449,     CVE-2026-64450, CVE-2026-64451, CVE-2026-64452, CVE-2026-64453, CVE-2026-64454, CVE-2026-64455,     CVE-2026-64456, CVE-2026-64457, CVE-2026-64458, CVE-2026-64459, CVE-2026-64460, CVE-2026-64461,     CVE-2026-64462, CVE-2026-64463, CVE-2026-64464, CVE-2026-64465, CVE-2026-64466, CVE-2026-64467,     CVE-2026-64468, CVE-2026-64469, CVE-2026-64470, CVE-2026-64471, CVE-2026-64472, CVE-2026-64473,     CVE-2026-64474, CVE-2026-64475, CVE-2026-64476, CVE-2026-64477, CVE-2026-64478, CVE-2026-64479,     CVE-2026-64480, CVE-2026-64481, CVE-2026-64482, CVE-2026-64483, CVE-2026-64484, CVE-2026-64485,     CVE-2026-64486, CVE-2026-64487, CVE-2026-64488, CVE-2026-64489, CVE-2026-64490, CVE-2026-64491,     CVE-2026-64492, CVE-2026-64493, CVE-2026-64494, CVE-2026-64495, CVE-2026-64496, CVE-2026-64497,     CVE-2026-64499, CVE-2026-64500, CVE-2026-64501, CVE-2026-64502, CVE-2026-64503, CVE-2026-64504,     CVE-2026-64505, CVE-2026-64507, CVE-2026-64508, CVE-2026-64509, CVE-2026-64510, CVE-2026-64511,     CVE-2026-64512, CVE-2026-64513, CVE-2026-64514, CVE-2026-64529, CVE-2026-64536, CVE-2026-64556,     CVE-2026-64588, CVE-2026-64589, CVE-2026-64590, CVE-2026-64591, CVE-2026-64592, CVE-2026-64593,     CVE-2026-64594, CVE-2026-64596, CVE-2026-64597, CVE-2026-64598, CVE-2026-64599, CVE-2026-64600,     CVE-2026-64601, CVE-2026-64602, CVE-2026-64603, CVE-2026-64604, CVE-2026-68084, CVE-2026-68085,     CVE-2026-68087, CVE-2026-68088, CVE-2026-68089, CVE-2026-68090, CVE-2026-68091, CVE-2026-68092,     CVE-2026-68459, CVE-2026-68460, CVE-2026-68461, CVE-2026-74584, CVE-2026-80591)

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.

An update of the linux package has been released.

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-2014 advisory.

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

    ipv6: use RCU in ip6_output() (CVE-2025-40158)

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

    gpio: Fix resource leaks on errors in gpiochip_add_data_with_key() (CVE-2026-31732)

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

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

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

    net: Drop the lock in skb_may_tx_timestamp() (CVE-2026-43216)

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

    bpf: Fix tcx/netkit detach permissions when prog fd isn't given (CVE-2026-45932)

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

    ip6_vti: set netns_immutable on the fallback device. (CVE-2026-52909)

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

    bonding: 3ad: implement proper RCU rules for port->aggregator (CVE-2026-52975)

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

    sched/psi: fix race between file release and pressure write (CVE-2026-52991)

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

    sctp: disable BH before calling udp_tunnel_xmit_skb() (CVE-2026-53070)

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

    fuse: limit FUSE_NOTIFY_RETRIEVE to uptodate folios (CVE-2026-53167)

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

    sctp: validate embedded INIT chunk and address list lengths in cookie (CVE-2026-53224)

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

    sctp: validate cached peer INIT chunk length in COOKIE_ECHO processing (CVE-2026-53246)

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

    fhandle: fix UAF due to unlocked ->mnt_ns read in may_decode_fh() (CVE-2026-53341)

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

    af_unix: Set gc_in_progress to true in unix_gc(). (CVE-2026-53361)

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

    virtiofs: fix UAF on submount umount

    iput() called from fuse_release_end() can Oops if the super block hasalready been destroyed.  Normally     this is prevented by waiting fornum_waiting to go down to zero before commencing with super block     shutdown.

    This only works, however, for the last submount instance, as the waitcounter is per connection, not per     superblock.

    Revert to using synchronous release requests for the auto_submounts case,which is virtiofs only at this     time. (CVE-2026-53381)

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

    vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write

    A KASAN null-ptr-deref was observed in vcs_notifier():

    BUG: KASAN: null-ptr-deref in vcs_notifier+0x98/0x130Read of size 2 at addr qmp_cmd_name:
    qmp_capabilities, arguments: {}

    The issue is a race condition in vcs_write(). When the console_lock istemporarily dropped (to copy data     from userspace), the vc_data pointerobtained from vcs_vc() may become stale. After re-acquiring the     lock,vcs_vc() is called again to re-validate the pointer. If the vc has beendeallocated in the meantime,     vcs_vc() returns NULL, and the while loopbreaks (with written > 0). However, after the loop,     vcs_scr_updated(vc)is still called with the now-NULL vc pointer, leading to a null pointerdereference in     the notifier chain (vcs_notifier dereferences param->vc).

    Fix this by adding a NULL check for vc before calling vcs_scr_updated(). (CVE-2026-53385)

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

    fuse: re-lock request before replacing page cache folio

    fuse_try_move_folio() unlocks the request on entry but does notre-lock it on the success path. This means     fuse_chan_abort() can end therequest and free the fuse_io_args (eg fuse_readpages_end()) while     thesubsequent copy chain logic after fuse_try_move_folio() accesses thefuse_io_args, leading to use-after-     free issues.

    Fix this by calling lock_request() before replace_page_cache_folio().This ensures the request is locked on     the success path which willprevent the fuse_io_args from being freed while the later copying logicruns,     and also ensures that the ap->folios[i]->mapping is never nullsince ap->folios[i] will always point to the     newfolio afterreplace_page_cache_folio(). (CVE-2026-53388)

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

    NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr (CVE-2026-53391)

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

    nfsd: reset write verifier on deferred writeback errors (CVE-2026-53393)

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

    nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race (CVE-2026-53394)

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

    nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)

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

    NFSD: Fix SECINFO_NO_NAME decode error cleanup (CVE-2026-53398)

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

    i2c: core: fix adapter registration race

    Adapters can be looked up based on their id using i2c_get_adapter()which takes a reference to the embedded     struct device.

    Make sure that the adapter (including its struct device) has beeninitialised before adding it to the IDR     to avoid accessing uninitialiseddata which could, for example, lead to NULL-pointer dereferences oruse-     after-free.

    Note that the i2c-dev chardev, which is registered from a bus notifier,currently uses i2c_get_adapter() so     the adapter needs to be added to theIDR before registration. (CVE-2026-53400)

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

    fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var

    info->var, a framebuffer's current mode, is expected to have a matchingentry in info->modelist.
    var_to_display() relies on this and treats afailed fb_match_mode() as This should not happen.
    fb_set_var() keeps ittrue by adding the mode to the list on every change, anddo_register_framebuffer()     does the same at registration.

    store_modes() replaces the modelist from userspace. fb_new_modelist()validates the new modes but does not     check that info->var still has amatch. It relies on fbcon_new_modelist() to re-point consoles, but     thatonly handles consoles mapped to the framebuffer. With fbcon unbound thereare none, so info->var is     left describing a mode that is no longer in thelist.

    A later console takeover runs var_to_display(), where fb_match_mode()returns NULL and leaves     fb_display[i].mode NULL. fbcon_switch() passes itto display_to_var(), and fb_videomode_to_var()     dereferences the NULL mode.

    Keep the current mode in the list in fb_new_modelist(), the same wayfb_set_var() does. (CVE-2026-53403)

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

    pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)

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

    tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done (CVE-2026-63801)

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

    blk-cgroup: fix UAF in __blkcg_rstat_flush() (CVE-2026-63802)

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

    KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() (CVE-2026-63806)

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

    KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level (CVE-2026-63807)

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

    exfat: fix potential use-after-free in exfat_find_dir_entry() (CVE-2026-63808)

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

    bpf: use kvfree() for replaced sysctl write buffer (CVE-2026-63809)

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

    block: Avoid mounting the bdev pseudo-filesystem in userspace (CVE-2026-63810)

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

    keys: Pin request_key_auth payload in instantiate paths (CVE-2026-63823)

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

    KEYS: fix overflow in keyctl_pkey_params_get_2() (CVE-2026-63824)

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

    fbdev: fix use-after-free in store_modes() (CVE-2026-63826)

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

    net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink (CVE-2026-63829)

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

    net: skmsg: preserve sg.copy across SG transforms (CVE-2026-63830)

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

    ntfs3: reject direct userspace writes to reserved $LX* xattrs

    NTFS3 uses $LXUID, $LXGID, $LXMOD and $LXDEV as internal WSLpermission metadata and reloads them into     i_uid, i_gid and i_modefrom ntfs_get_wsl_perm().

    Because the empty-prefix xattr handler also lets file owners callsetxattr() on these names directly, an     unprivileged writer on awritable ntfs3 mount can plant root ownership and S_ISUID on their ownfile and     gain euid 0 after inode reload.

    Reject direct userspace writes to the reserved $LX* names. Internalntfs3 metadata updates are unchanged     because ntfs_save_wsl_perm()writes them via ntfs_set_ea() directly.

    [almaz.alexandrovich@paragon-software.com: added an additional check for non privileged users]     (CVE-2026-63833)

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

    drivers/base/memory: set mem->altmap after successful device registration (CVE-2026-64244)

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

    fbdev: modedb: fix a possible UAF in fb_find_mode() (CVE-2026-64245)

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

    KVM: x86: hyper-v: Bound the bank index when querying sparse banks (CVE-2026-64247)

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

    MIPS: smp: report dying CPU to RCU in stop_this_cpu() (CVE-2026-64248)

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

    LoongArch: Report dying CPU to RCU in stop_this_cpu() (CVE-2026-64250)

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

    kernel/fork: clear PF_BLOCK_TS in copy_process() (CVE-2026-64253)

Tenable has extracted the preceding description block directly from the tested product security advisory.

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

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - KVM: x86: hyper-v: Bound the bank index when querying sparse banks When checking if a VP ID is included in     a sparse bank set, explicitly check that the ID can actually be contained in a sparse bank (the TLFS     allows for a maximum of 64 banks of 64 vCPUs each). When handling a paravirtual TLB flush for L2, the VP     ID is copied verbatim from the enlightened VMCS, without any bounds check, i.e. isn't guaranteed to be     under the limit of 4096. Failure to check the bounds of the VP ID leads to an out-of-bounds read when     testing the sparse bank, and super strictly speaking could lead to KVM performing an unnecessary TLB flush     for an L2 vCPU. ================================================================== BUG: KASAN: use-after-     free in hv_is_vp_in_sparse_set+0x85/0x100 [kvm] Read of size 8 at addr ffff88811ba5f598 by task     hyperv_evmcs/2802 CPU: 12 UID: 1000 PID: 2802 Comm: hyperv_evmcs Not tainted 7.1.0-rc2 #7 PREEMPT Hardware     name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 Call Trace: <TASK>     dump_stack_lvl+0x51/0x60 print_report+0xcb/0x5d0 kasan_report+0xb4/0xe0 kasan_check_range+0x35/0x1b0     hv_is_vp_in_sparse_set+0x85/0x100 [kvm] kvm_hv_flush_tlb+0xe9e/0x16c0 [kvm] kvm_hv_hypercall+0xe6b/0x1e60     [kvm] vmx_handle_exit+0x485/0x1b60 [kvm_intel] kvm_arch_vcpu_ioctl_run+0x22e3/0x5070 [kvm]     kvm_vcpu_ioctl+0x5d0/0x10c0 [kvm] __x64_sys_ioctl+0x129/0x1a0 do_syscall_64+0xb9/0xcf0     entry_SYSCALL_64_after_hwframe+0x4b/0x53 RIP: 0033:0x7f0e62d1a9bf </TASK> The buggy address belongs to the     physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffffffffffffffff pfn:0x11ba5f     flags: 0x4000000000000000(zone=1) raw: 4000000000000000 0000000000000000 00000000ffffffff 0000000000000000     raw: ffffffffffffffff 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad     access detected Memory state around the buggy address: ffff88811ba5f480: ff ff ff ff ff ff ff ff ff ff ff     ff ff ff ff ff ffff88811ba5f500: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff88811ba5f580: ff ff     ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88811ba5f600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff     ff ffff88811ba5f680: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff     ================================================================== Disabling lock debugging due to kernel     taint Opportunistically add a compile time assertion to ensure the maximum number of sparse banks exactly     matches the number of possible bits in the passed in mask. [sean: add KASAN splat, drop comment, add     assert, massage changelog] (CVE-2026-64247)

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

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2026-1969 advisory.

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

    sctp: disable BH before calling udp_tunnel_xmit_skb() (CVE-2026-53070)

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

    bpf: Fix same-register dst/src OOB read and pointer leak in sock_ops (CVE-2026-53078)

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

    KVM: x86: Fix shadow paging use-after-free due to unexpected role (CVE-2026-53359)

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

    af_unix: Set gc_in_progress to true in unix_gc(). (CVE-2026-53361)

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

    virtiofs: fix UAF on submount umount

    iput() called from fuse_release_end() can Oops if the super block hasalready been destroyed.  Normally     this is prevented by waiting fornum_waiting to go down to zero before commencing with super block     shutdown.

    This only works, however, for the last submount instance, as the waitcounter is per connection, not per     superblock.

    Revert to using synchronous release requests for the auto_submounts case,which is virtiofs only at this     time. (CVE-2026-53381)

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

    vc_screen: fix null-ptr-deref in vcs_notifier() during concurrent vcs_write

    A KASAN null-ptr-deref was observed in vcs_notifier():

    BUG: KASAN: null-ptr-deref in vcs_notifier+0x98/0x130Read of size 2 at addr qmp_cmd_name:
    qmp_capabilities, arguments: {}

    The issue is a race condition in vcs_write(). When the console_lock istemporarily dropped (to copy data     from userspace), the vc_data pointerobtained from vcs_vc() may become stale. After re-acquiring the     lock,vcs_vc() is called again to re-validate the pointer. If the vc has beendeallocated in the meantime,     vcs_vc() returns NULL, and the while loopbreaks (with written > 0). However, after the loop,     vcs_scr_updated(vc)is still called with the now-NULL vc pointer, leading to a null pointerdereference in     the notifier chain (vcs_notifier dereferences param->vc).

    Fix this by adding a NULL check for vc before calling vcs_scr_updated(). (CVE-2026-53385)

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

    fuse: re-lock request before replacing page cache folio

    fuse_try_move_folio() unlocks the request on entry but does notre-lock it on the success path. This means     fuse_chan_abort() can end therequest and free the fuse_io_args (eg fuse_readpages_end()) while     thesubsequent copy chain logic after fuse_try_move_folio() accesses thefuse_io_args, leading to use-after-     free issues.

    Fix this by calling lock_request() before replace_page_cache_folio().This ensures the request is locked on     the success path which willprevent the fuse_io_args from being freed while the later copying logicruns,     and also ensures that the ap->folios[i]->mapping is never nullsince ap->folios[i] will always point to the     newfolio afterreplace_page_cache_folio(). (CVE-2026-53388)

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

    net/tcp-ao: fix use-after-free of key in del_async path (CVE-2026-53389)

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

    NFSv4/pNFS: reject zero-length r_addr in nfs4_decode_mp_ds_addr (CVE-2026-53391)

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

    NFSv4/flexfiles: reject zero filehandle version count (CVE-2026-53392)

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

    nfsd: reset write verifier on deferred writeback errors (CVE-2026-53393)

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

    nfsd: avoid leaking pre-allocated openowner on unconfirmed retry race (CVE-2026-53394)

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

    nfsd: fix posix_acl leak on SETACL decode failure (CVE-2026-53397)

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

    NFSD: Fix SECINFO_NO_NAME decode error cleanup (CVE-2026-53398)

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

    i2c: core: fix adapter registration race

    Adapters can be looked up based on their id using i2c_get_adapter()which takes a reference to the embedded     struct device.

    Make sure that the adapter (including its struct device) has beeninitialised before adding it to the IDR     to avoid accessing uninitialiseddata which could, for example, lead to NULL-pointer dereferences oruse-     after-free.

    Note that the i2c-dev chardev, which is registered from a bus notifier,currently uses i2c_get_adapter() so     the adapter needs to be added to theIDR before registration. (CVE-2026-53400)

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

    fbdev: Fix fb_new_modelist to prevent null-ptr-deref in fb_videomode_to_var

    info->var, a framebuffer's current mode, is expected to have a matchingentry in info->modelist.
    var_to_display() relies on this and treats afailed fb_match_mode() as This should not happen.
    fb_set_var() keeps ittrue by adding the mode to the list on every change, anddo_register_framebuffer()     does the same at registration.

    store_modes() replaces the modelist from userspace. fb_new_modelist()validates the new modes but does not     check that info->var still has amatch. It relies on fbcon_new_modelist() to re-point consoles, but     thatonly handles consoles mapped to the framebuffer. With fbcon unbound thereare none, so info->var is     left describing a mode that is no longer in thelist.

    A later console takeover runs var_to_display(), where fb_match_mode()returns NULL and leaves     fb_display[i].mode NULL. fbcon_switch() passes itto display_to_var(), and fb_videomode_to_var()     dereferences the NULL mode.

    Keep the current mode in the list in fb_new_modelist(), the same wayfb_set_var() does. (CVE-2026-53403)

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

    pNFS: Fix use-after-free in pnfs_update_layout() (CVE-2026-63800)

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

    tipc: fix slab-use-after-free Read in tipc_aead_decrypt_done (CVE-2026-63801)

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

    blk-cgroup: fix UAF in __blkcg_rstat_flush() (CVE-2026-63802)

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

    KVM: Replace guest-triggerable BUG_ON() in ioeventfd datamatch with get_unaligned() (CVE-2026-63806)

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

    KVM: x86/mmu: Ensure hugepage is in by slot before checking max mapping level (CVE-2026-63807)

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

    exfat: fix potential use-after-free in exfat_find_dir_entry() (CVE-2026-63808)

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

    bpf: use kvfree() for replaced sysctl write buffer (CVE-2026-63809)

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

    block: Avoid mounting the bdev pseudo-filesystem in userspace (CVE-2026-63810)

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

    keys: Pin request_key_auth payload in instantiate paths (CVE-2026-63823)

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

    KEYS: fix overflow in keyctl_pkey_params_get_2() (CVE-2026-63824)

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

    fbdev: fix use-after-free in store_modes() (CVE-2026-63826)

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

    apparmor: mediate the implicit connect of TCP fast open sendmsg (CVE-2026-63828)

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

    net: ip_gre: require CAP_NET_ADMIN in the device netns for changelink (CVE-2026-63829)

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

    net: skmsg: preserve sg.copy across SG transforms (CVE-2026-63830)

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

    ntfs3: reject direct userspace writes to reserved $LX* xattrs

    NTFS3 uses $LXUID, $LXGID, $LXMOD and $LXDEV as internal WSLpermission metadata and reloads them into     i_uid, i_gid and i_modefrom ntfs_get_wsl_perm().

    Because the empty-prefix xattr handler also lets file owners callsetxattr() on these names directly, an     unprivileged writer on awritable ntfs3 mount can plant root ownership and S_ISUID on their ownfile and     gain euid 0 after inode reload.

    Reject direct userspace writes to the reserved $LX* names. Internalntfs3 metadata updates are unchanged     because ntfs_save_wsl_perm()writes them via ntfs_set_ea() directly.

    [almaz.alexandrovich@paragon-software.com: added an additional check for non privileged users]     (CVE-2026-63833)

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

    drivers/base/memory: set mem->altmap after successful device registration (CVE-2026-64244)

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

    fbdev: modedb: fix a possible UAF in fb_find_mode() (CVE-2026-64245)

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

    KVM: x86: hyper-v: Bound the bank index when querying sparse banks (CVE-2026-64247)

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

    MIPS: smp: report dying CPU to RCU in stop_this_cpu() (CVE-2026-64248)

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

    LoongArch: Report dying CPU to RCU in stop_this_cpu() (CVE-2026-64250)

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

    kernel/fork: clear PF_BLOCK_TS in copy_process() (CVE-2026-64253)

Tenable has extracted the preceding description block directly from the tested product security advisory.

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

ID	Name	Product	Family	Type	Severity
343532	Ubuntu 24.04 LTS / Pro Realtime 24.04 LTS : Linux kernel (GCP) vulnerabilities (USN-8728-1)	Nessus	Ubuntu Local Security Checks	Local	high
343531	Ubuntu 26.04 LTS : Linux kernel (OEM) vulnerabilities (USN-8727-1)	Nessus	Ubuntu Local Security Checks	Local	high
343527	Ubuntu 24.04 LTS / 26.04 LTS / Pro Realtime 24.04 LTS : Linux kernel vulnerabilities (USN-8726-1)	Nessus	Ubuntu Local Security Checks	Local	high
343049	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2026-500248)	Nessus	Oracle Linux Local Security Checks	Local	high
333954	Photon OS 5.0: Linux PHSA-2026-5.0-92-0916	Nessus	PhotonOS Local Security Checks	Local	high
332042	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2026-2014)	Nessus	Amazon Linux Local Security Checks	Local	high
330181	Linux Distros Unpatched Vulnerability : CVE-2026-64247	Nessus	Misc.	Local	high
328468	Amazon Linux 2023 : bpftool6.18, kernel6.18, kernel6.18-devel (ALAS2023-2026-1969)	Nessus	Amazon Linux Local Security Checks	Local	high
326038	Photon OS 5.0: Linux PHSA-2026-5.0-0916	Nessus	PhotonOS Local Security Checks	Local	high

Detections

Analytics

CVE-2026-64247

high

Tenable Plugins

high

high

high

high

high

high

high

high

high