In the Linux kernel, the following vulnerability has been resolved: x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP When running as an SNP or TDX guest under KVM, force the legacy PCI hole, i.e. memory between Top of Lower Usable DRAM and 4GiB, to be mapped as UC via a forced variable MTRR range. In most KVM-based setups, legacy devices such as the HPET and TPM are enumerated via ACPI. ACPI enumeration includes a Memory32Fixed entry, and optionally a SystemMemory descriptor for an OperationRegion, e.g. if the device needs to be accessed via a Control Method. If a SystemMemory entry is present, then the kernel's ACPI driver will auto-ioremap the region so that it can be accessed at will. However, the ACPI spec doesn't provide a way to enumerate the memory type of SystemMemory regions, i.e. there's no way to tell software that a region must be mapped as UC vs. WB, etc. As a result, Linux's ACPI driver always maps SystemMemory regions using ioremap_cache(), i.e. as WB on x86. The dedicated device drivers however, e.g. the HPET driver and TPM driver, want to map their associated memory as UC or WC, as accessing PCI devices using WB is unsupported. On bare metal and non-CoCO, the conflicting requirements "work" as firmware configures the PCI hole (and other device memory) to be UC in the MTRRs. So even though the ACPI mappings request WB, they are forced to UC- in the kernel's tracking due to the kernel properly handling the MTRR overrides, and thus are compatible with the drivers' requested WC/UC-. With force WB MTRRs on SNP and TDX guests, the ACPI mappings get their requested WB if the ACPI mappings are established before the dedicated driver code attempts to initialize the device. E.g. if acpi_init() runs before the corresponding device driver is probed, ACPI's WB mapping will "win", and result in the driver's ioremap() failing because the existing WB mapping isn't compatible with the requested WC/UC-. E.g. when a TPM is emulated by the hypervisor (ignoring the security implications of relying on what is allegedly an untrusted entity to store measurements), the TPM driver will request UC and fail: [ 1.730459] ioremap error for 0xfed40000-0xfed45000, requested 0x2, got 0x0 [ 1.732780] tpm_tis MSFT0101:00: probe with driver tpm_tis failed with error -12 Note, the '0x2' and '0x0' values refer to "enum page_cache_mode", not x86's memtypes (which frustratingly are an almost pure inversion; 2 == WB, 0 == UC). E.g. tracing mapping requests for TPM TIS yields: Mapping TPM TIS with req_type = 0 WARNING: CPU: 22 PID: 1 at arch/x86/mm/pat/memtype.c:530 memtype_reserve+0x2ab/0x460 Modules linked in: CPU: 22 UID: 0 PID: 1 Comm: swapper/0 Tainted: G W 6.16.0-rc7+ #2 VOLUNTARY Tainted: [W]=WARN Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/29/2025 RIP: 0010:memtype_reserve+0x2ab/0x460 __ioremap_caller+0x16d/0x3d0 ioremap_cache+0x17/0x30 x86_acpi_os_ioremap+0xe/0x20 acpi_os_map_iomem+0x1f3/0x240 acpi_os_map_memory+0xe/0x20 acpi_ex_system_memory_space_handler+0x273/0x440 acpi_ev_address_space_dispatch+0x176/0x4c0 acpi_ex_access_region+0x2ad/0x530 acpi_ex_field_datum_io+0xa2/0x4f0 acpi_ex_extract_from_field+0x296/0x3e0 acpi_ex_read_data_from_field+0xd1/0x460 acpi_ex_resolve_node_to_value+0x2ee/0x530 acpi_ex_resolve_to_value+0x1f2/0x540 acpi_ds_evaluate_name_path+0x11b/0x190 acpi_ds_exec_end_op+0x456/0x960 acpi_ps_parse_loop+0x27a/0xa50 acpi_ps_parse_aml+0x226/0x600 acpi_ps_execute_method+0x172/0x3e0 acpi_ns_evaluate+0x175/0x5f0 acpi_evaluate_object+0x213/0x490 acpi_evaluate_integer+0x6d/0x140 acpi_bus_get_status+0x93/0x150 acpi_add_single_object+0x43a/0x7c0 acpi_bus_check_add+0x149/0x3a0 acpi_bus_check_add_1+0x16/0x30 acpi_ns_walk_namespace+0x22c/0x360 acpi_walk_namespace+0x15c/0x170 acpi_bus_scan+0x1dd/0x200 acpi_scan_init+0xe5/0x2b0 acpi_init+0x264/0x5b0 do_one_i ---truncated---

The remote Ubuntu 24.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-8048-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:

    - ARM64 architecture;

    - MIPS architecture;

    - Nios II architecture;

    - PA-RISC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - Sun Sparc architecture;

    - x86 architecture;

    - Xtensa architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Compute Acceleration Framework;

    - ACPI drivers;

    - Drivers core;

    - Network block device driver;

    - Bluetooth drivers;

    - Bus devices;

    - Hardware random number generator core;

    - Character device driver;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - CXL (Compute Express Link) drivers;

    - Device frequency scaling framework;

    - ARM SCMI message protocol;

    - GPIO subsystem;

    - GPU drivers;

    - Hardware monitoring drivers;

    - HW tracing;

    - InfiniBand drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - ISDN/mISDN subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - Fastrpc Driver;

    - PCI Endpoint Test driver;

    - VMware Balloon Driver;

    - MOST (Media Oriented Systems Transport) drivers;

    - Network drivers;

    - Mellanox network drivers;

    - STMicroelectronics network drivers;

    - NVME drivers;

    - PCI subsystem;

    - Performance monitor drivers;

    - Pin controllers subsystem;

    - Mellanox platform drivers;

    - x86 platform drivers;

    - ARM PM domains;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - PWM drivers;

    - Remote Processor subsystem;

    - SCSI subsystem;

    - SPI subsystem;

    - Trusted Execution Environment drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - UFS subsystem;

    - Userspace I/O drivers;

    - Cadence USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - vDPA drivers;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - EROFS file system;

    - Ext4 file system;

    - F2FS file system;

    - GFS2 file system;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - File system notification infrastructure;

    - NTFS3 file system;

    - Proc file system;

    - Diskquota system;

    - SMB network file system;

    - BPF subsystem;

    - Mellanox drivers;

    - Memory management;

    - Virtio network driver;

    - Bluetooth subsystem;

    - IP tunnels definitions;

    - io_uring subsystem;

    - Kernel crash support code;

    - Perf events;

    - Kernel futex primitives;

    - PID allocator;

    - Scheduler infrastructure;

    - Syscalls implementation;

    - Timer subsystem;

    - Tracing infrastructure;

    - 9P file system network protocol;

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Network traffic control;

    - SCTP protocol;

    - SMC sockets;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - VMware vSockets driver;

    - eXpress Data Path;

    - XFRM subsystem;

    - Integrity Measurement Architecture(IMA) framework;

    - ALSA framework;

    - HD-audio driver;

    - AMD SoC Alsa drivers;

    - WCD audio codecs;

    - Intel ASoC drivers;

    - USB sound devices;

    - KVM subsystem; (CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004, CVE-2025-40029,     CVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033, CVE-2025-40034, CVE-2025-40035,     CVE-2025-40036, CVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040, CVE-2025-40041,     CVE-2025-40042, CVE-2025-40043, CVE-2025-40044, CVE-2025-40045, CVE-2025-40046, CVE-2025-40047,     CVE-2025-40048, CVE-2025-40049, CVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053,     CVE-2025-40054, CVE-2025-40055, CVE-2025-40056, CVE-2025-40057, CVE-2025-40058, CVE-2025-40059,     CVE-2025-40060, CVE-2025-40061, CVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065,     CVE-2025-40066, CVE-2025-40067, CVE-2025-40068, CVE-2025-40069, CVE-2025-40070, CVE-2025-40071,     CVE-2025-40072, CVE-2025-40073, CVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077,     CVE-2025-40078, CVE-2025-40079, CVE-2025-40080, CVE-2025-40081, CVE-2025-40082, CVE-2025-40084,     CVE-2025-40085, CVE-2025-40086, CVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091,     CVE-2025-40092, CVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096, CVE-2025-40097,     CVE-2025-40098, CVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103,     CVE-2025-40104, CVE-2025-40105, CVE-2025-40106, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112,     CVE-2025-40113, CVE-2025-40115, CVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119,     CVE-2025-40120, CVE-2025-40121, CVE-2025-40122, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125,     CVE-2025-40126, CVE-2025-40127, CVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132,     CVE-2025-40133, CVE-2025-40134, CVE-2025-40135, CVE-2025-40136, CVE-2025-40137, CVE-2025-40138,     CVE-2025-40139, CVE-2025-40140, CVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145,     CVE-2025-40146, CVE-2025-40147, CVE-2025-40148, CVE-2025-40149, CVE-2025-40150, CVE-2025-40151,     CVE-2025-40152, CVE-2025-40153, CVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40158,     CVE-2025-40159, CVE-2025-40160, CVE-2025-40161, CVE-2025-40162, CVE-2025-40163, CVE-2025-40164,     CVE-2025-40165, CVE-2025-40166, CVE-2025-40167, CVE-2025-40168, CVE-2025-40169, CVE-2025-40170,     CVE-2025-40171, CVE-2025-40173, CVE-2025-40174, CVE-2025-40175, CVE-2025-40176, CVE-2025-40178,     CVE-2025-40179, CVE-2025-40180, CVE-2025-40181, CVE-2025-40182, CVE-2025-40183, CVE-2025-40184,     CVE-2025-40185, CVE-2025-40186, CVE-2025-40187, CVE-2025-40188, CVE-2025-40189, CVE-2025-40191,     CVE-2025-40192, CVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196, CVE-2025-40198,     CVE-2025-40199, CVE-2025-40200, CVE-2025-40201, CVE-2025-40203, CVE-2025-40204, CVE-2025-40205,     CVE-2025-40206, CVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210, CVE-2025-40211,     CVE-2025-40212, CVE-2025-40213, CVE-2025-40217, CVE-2025-40218, CVE-2025-40219, CVE-2025-40220,     CVE-2025-40221, CVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225, CVE-2025-40226,     CVE-2025-40227, CVE-2025-40228, CVE-2025-40229, CVE-2025-40230, CVE-2025-40231, CVE-2025-40233,     CVE-2025-40234, CVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238, CVE-2025-40239,     CVE-2025-40240, CVE-2025-40241, CVE-2025-40242, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245,     CVE-2025-40256, CVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270, CVE-2025-40271,     CVE-2025-40272, CVE-2025-40273, CVE-2025-40274, CVE-2025-40275, CVE-2025-40276, CVE-2025-40277,     CVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282, CVE-2025-40283,     CVE-2025-40284, CVE-2025-40285, CVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,     CVE-2025-40291, CVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295, CVE-2025-40296,     CVE-2025-40297, CVE-2025-40298, CVE-2025-40299, CVE-2025-40301, CVE-2025-40302, CVE-2025-40303,     CVE-2025-40304, CVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308, CVE-2025-40309,     CVE-2025-40310, CVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314, CVE-2025-40315,     CVE-2025-40316, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320, CVE-2025-40321,     CVE-2025-40322, CVE-2025-40323, CVE-2025-40324, CVE-2025-40326, CVE-2025-40327, CVE-2025-40328,     CVE-2025-40329, CVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333, CVE-2025-40334,     CVE-2025-40335, CVE-2025-40336, CVE-2025-40337, CVE-2025-40338, CVE-2025-40339, CVE-2025-40340,     CVE-2025-40341, CVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346, CVE-2025-40347,     CVE-2025-40349, CVE-2025-40350, CVE-2025-40351, CVE-2025-40352, CVE-2025-40353, CVE-2025-40354,     CVE-2025-40355, CVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359, CVE-2025-40360,     CVE-2025-40362, CVE-2025-40363, CVE-2025-68167, CVE-2025-68168, CVE-2025-68169, CVE-2025-68170,     CVE-2025-68171, CVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175, CVE-2025-68176,     CVE-2025-68177, CVE-2025-68178, CVE-2025-68179, CVE-2025-68180, CVE-2025-68181, CVE-2025-68182,     CVE-2025-68183, CVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187, CVE-2025-68188,     CVE-2025-68189, CVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68193, CVE-2025-68194,     CVE-2025-68196, CVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200, CVE-2025-68201,     CVE-2025-68202, CVE-2025-68204, CVE-2025-68205, CVE-2025-68206, CVE-2025-68207, CVE-2025-68208,     CVE-2025-68209, CVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240, CVE-2025-68241,     CVE-2025-68242, CVE-2025-68243, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246, CVE-2025-68247,     CVE-2025-68248, CVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253, CVE-2025-68309,     CVE-2025-68310, CVE-2025-68311, CVE-2025-68312, CVE-2025-68313, CVE-2025-68314, CVE-2025-68315,     CVE-2025-68317, CVE-2025-68318, CVE-2025-68319, CVE-2025-68320, CVE-2025-68321, CVE-2025-68322,     CVE-2025-68734)

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 25.10 host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-8029-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:

    - ARM64 architecture;

    - MIPS architecture;

    - Nios II architecture;

    - PA-RISC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - Sun Sparc architecture;

    - x86 architecture;

    - Xtensa architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Compute Acceleration Framework;

    - ACPI drivers;

    - Drivers core;

    - Network block device driver;

    - Bluetooth drivers;

    - Bus devices;

    - Hardware random number generator core;

    - Character device driver;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - CXL (Compute Express Link) drivers;

    - Device frequency scaling framework;

    - ARM SCMI message protocol;

    - GPIO subsystem;

    - GPU drivers;

    - Hardware monitoring drivers;

    - HW tracing;

    - InfiniBand drivers;

    - Input Device (Miscellaneous) drivers;

    - IOMMU subsystem;

    - ISDN/mISDN subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - Fastrpc Driver;

    - PCI Endpoint Test driver;

    - VMware Balloon Driver;

    - MOST (Media Oriented Systems Transport) drivers;

    - Network drivers;

    - Mellanox network drivers;

    - STMicroelectronics network drivers;

    - NVME drivers;

    - PCI subsystem;

    - Performance monitor drivers;

    - Pin controllers subsystem;

    - Mellanox platform drivers;

    - x86 platform drivers;

    - ARM PM domains;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - PWM drivers;

    - Remote Processor subsystem;

    - SCSI subsystem;

    - SPI subsystem;

    - Trusted Execution Environment drivers;

    - Thunderbolt and USB4 drivers;

    - TTY drivers;

    - UFS subsystem;

    - Userspace I/O drivers;

    - Cadence USB3 driver;

    - USB Gadget drivers;

    - USB Host Controller drivers;

    - vDPA drivers;

    - Virtio Host (VHOST) subsystem;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - EROFS file system;

    - Ext4 file system;

    - F2FS file system;

    - GFS2 file system;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - File system notification infrastructure;

    - NTFS3 file system;

    - Proc file system;

    - Diskquota system;

    - SMB network file system;

    - BPF subsystem;

    - Mellanox drivers;

    - Memory management;

    - Virtio network driver;

    - Bluetooth subsystem;

    - IP tunnels definitions;

    - io_uring subsystem;

    - Kernel crash support code;

    - Perf events;

    - Kernel futex primitives;

    - PID allocator;

    - Scheduler infrastructure;

    - Syscalls implementation;

    - Timer subsystem;

    - Tracing infrastructure;

    - 9P file system network protocol;

    - Ethernet bridge;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - Multipath TCP;

    - Netfilter;

    - NFC subsystem;

    - Network traffic control;

    - SCTP protocol;

    - SMC sockets;

    - Sun RPC protocol;

    - TIPC protocol;

    - TLS protocol;

    - VMware vSockets driver;

    - eXpress Data Path;

    - XFRM subsystem;

    - Integrity Measurement Architecture(IMA) framework;

    - ALSA framework;

    - HD-audio driver;

    - AMD SoC Alsa drivers;

    - WCD audio codecs;

    - Intel ASoC drivers;

    - USB sound devices;

    - KVM subsystem; (CVE-2025-40001, CVE-2025-40002, CVE-2025-40003, CVE-2025-40004, CVE-2025-40029,     CVE-2025-40030, CVE-2025-40031, CVE-2025-40032, CVE-2025-40033, CVE-2025-40034, CVE-2025-40035,     CVE-2025-40036, CVE-2025-40037, CVE-2025-40038, CVE-2025-40039, CVE-2025-40040, CVE-2025-40042,     CVE-2025-40043, CVE-2025-40044, CVE-2025-40045, CVE-2025-40046, CVE-2025-40047, CVE-2025-40048,     CVE-2025-40049, CVE-2025-40050, CVE-2025-40051, CVE-2025-40052, CVE-2025-40053, CVE-2025-40054,     CVE-2025-40055, CVE-2025-40056, CVE-2025-40057, CVE-2025-40058, CVE-2025-40059, CVE-2025-40060,     CVE-2025-40061, CVE-2025-40062, CVE-2025-40063, CVE-2025-40064, CVE-2025-40065, CVE-2025-40066,     CVE-2025-40067, CVE-2025-40068, CVE-2025-40069, CVE-2025-40070, CVE-2025-40071, CVE-2025-40072,     CVE-2025-40073, CVE-2025-40074, CVE-2025-40075, CVE-2025-40076, CVE-2025-40077, CVE-2025-40078,     CVE-2025-40079, CVE-2025-40080, CVE-2025-40081, CVE-2025-40082, CVE-2025-40084, CVE-2025-40085,     CVE-2025-40086, CVE-2025-40087, CVE-2025-40088, CVE-2025-40089, CVE-2025-40091, CVE-2025-40092,     CVE-2025-40093, CVE-2025-40094, CVE-2025-40095, CVE-2025-40096, CVE-2025-40097, CVE-2025-40098,     CVE-2025-40099, CVE-2025-40100, CVE-2025-40101, CVE-2025-40102, CVE-2025-40103, CVE-2025-40104,     CVE-2025-40105, CVE-2025-40106, CVE-2025-40110, CVE-2025-40111, CVE-2025-40112, CVE-2025-40113,     CVE-2025-40115, CVE-2025-40116, CVE-2025-40117, CVE-2025-40118, CVE-2025-40119, CVE-2025-40120,     CVE-2025-40121, CVE-2025-40122, CVE-2025-40123, CVE-2025-40124, CVE-2025-40125, CVE-2025-40126,     CVE-2025-40127, CVE-2025-40129, CVE-2025-40130, CVE-2025-40131, CVE-2025-40132, CVE-2025-40133,     CVE-2025-40134, CVE-2025-40135, CVE-2025-40136, CVE-2025-40137, CVE-2025-40138, CVE-2025-40139,     CVE-2025-40140, CVE-2025-40141, CVE-2025-40142, CVE-2025-40143, CVE-2025-40145, CVE-2025-40146,     CVE-2025-40147, CVE-2025-40148, CVE-2025-40149, CVE-2025-40150, CVE-2025-40152, CVE-2025-40153,     CVE-2025-40154, CVE-2025-40155, CVE-2025-40156, CVE-2025-40158, CVE-2025-40159, CVE-2025-40160,     CVE-2025-40161, CVE-2025-40162, CVE-2025-40163, CVE-2025-40164, CVE-2025-40165, CVE-2025-40166,     CVE-2025-40167, CVE-2025-40168, CVE-2025-40169, CVE-2025-40170, CVE-2025-40171, CVE-2025-40172,     CVE-2025-40173, CVE-2025-40174, CVE-2025-40175, CVE-2025-40176, CVE-2025-40177, CVE-2025-40178,     CVE-2025-40179, CVE-2025-40180, CVE-2025-40181, CVE-2025-40182, CVE-2025-40183, CVE-2025-40184,     CVE-2025-40185, CVE-2025-40186, CVE-2025-40187, CVE-2025-40188, CVE-2025-40189, CVE-2025-40191,     CVE-2025-40192, CVE-2025-40193, CVE-2025-40194, CVE-2025-40195, CVE-2025-40196, CVE-2025-40198,     CVE-2025-40199, CVE-2025-40200, CVE-2025-40201, CVE-2025-40203, CVE-2025-40204, CVE-2025-40205,     CVE-2025-40206, CVE-2025-40207, CVE-2025-40208, CVE-2025-40209, CVE-2025-40210, CVE-2025-40211,     CVE-2025-40212, CVE-2025-40213, CVE-2025-40217, CVE-2025-40218, CVE-2025-40219, CVE-2025-40220,     CVE-2025-40221, CVE-2025-40222, CVE-2025-40223, CVE-2025-40224, CVE-2025-40225, CVE-2025-40226,     CVE-2025-40227, CVE-2025-40228, CVE-2025-40229, CVE-2025-40230, CVE-2025-40231, CVE-2025-40233,     CVE-2025-40234, CVE-2025-40235, CVE-2025-40236, CVE-2025-40237, CVE-2025-40238, CVE-2025-40239,     CVE-2025-40240, CVE-2025-40241, CVE-2025-40242, CVE-2025-40243, CVE-2025-40244, CVE-2025-40245,     CVE-2025-40256, CVE-2025-40267, CVE-2025-40268, CVE-2025-40269, CVE-2025-40270, CVE-2025-40271,     CVE-2025-40272, CVE-2025-40273, CVE-2025-40274, CVE-2025-40275, CVE-2025-40276, CVE-2025-40277,     CVE-2025-40278, CVE-2025-40279, CVE-2025-40280, CVE-2025-40281, CVE-2025-40282, CVE-2025-40283,     CVE-2025-40284, CVE-2025-40285, CVE-2025-40286, CVE-2025-40287, CVE-2025-40288, CVE-2025-40289,     CVE-2025-40291, CVE-2025-40292, CVE-2025-40293, CVE-2025-40294, CVE-2025-40295, CVE-2025-40296,     CVE-2025-40297, CVE-2025-40298, CVE-2025-40299, CVE-2025-40301, CVE-2025-40302, CVE-2025-40303,     CVE-2025-40304, CVE-2025-40305, CVE-2025-40306, CVE-2025-40307, CVE-2025-40308, CVE-2025-40309,     CVE-2025-40310, CVE-2025-40311, CVE-2025-40312, CVE-2025-40313, CVE-2025-40314, CVE-2025-40315,     CVE-2025-40316, CVE-2025-40317, CVE-2025-40318, CVE-2025-40319, CVE-2025-40320, CVE-2025-40321,     CVE-2025-40322, CVE-2025-40323, CVE-2025-40324, CVE-2025-40326, CVE-2025-40327, CVE-2025-40328,     CVE-2025-40329, CVE-2025-40330, CVE-2025-40331, CVE-2025-40332, CVE-2025-40333, CVE-2025-40334,     CVE-2025-40335, CVE-2025-40336, CVE-2025-40337, CVE-2025-40338, CVE-2025-40339, CVE-2025-40340,     CVE-2025-40341, CVE-2025-40342, CVE-2025-40343, CVE-2025-40344, CVE-2025-40346, CVE-2025-40347,     CVE-2025-40349, CVE-2025-40350, CVE-2025-40351, CVE-2025-40352, CVE-2025-40353, CVE-2025-40354,     CVE-2025-40355, CVE-2025-40356, CVE-2025-40357, CVE-2025-40358, CVE-2025-40359, CVE-2025-40360,     CVE-2025-40362, CVE-2025-40363, CVE-2025-68167, CVE-2025-68168, CVE-2025-68169, CVE-2025-68170,     CVE-2025-68171, CVE-2025-68172, CVE-2025-68173, CVE-2025-68174, CVE-2025-68175, CVE-2025-68176,     CVE-2025-68177, CVE-2025-68178, CVE-2025-68179, CVE-2025-68180, CVE-2025-68181, CVE-2025-68182,     CVE-2025-68183, CVE-2025-68184, CVE-2025-68185, CVE-2025-68186, CVE-2025-68187, CVE-2025-68188,     CVE-2025-68189, CVE-2025-68190, CVE-2025-68191, CVE-2025-68192, CVE-2025-68193, CVE-2025-68194,     CVE-2025-68196, CVE-2025-68197, CVE-2025-68198, CVE-2025-68199, CVE-2025-68200, CVE-2025-68201,     CVE-2025-68202, CVE-2025-68204, CVE-2025-68205, CVE-2025-68206, CVE-2025-68207, CVE-2025-68208,     CVE-2025-68209, CVE-2025-68210, CVE-2025-68211, CVE-2025-68239, CVE-2025-68240, CVE-2025-68241,     CVE-2025-68242, CVE-2025-68243, CVE-2025-68244, CVE-2025-68245, CVE-2025-68246, CVE-2025-68247,     CVE-2025-68248, CVE-2025-68249, CVE-2025-68250, CVE-2025-68251, CVE-2025-68253, CVE-2025-68309,     CVE-2025-68310, CVE-2025-68311, CVE-2025-68312, CVE-2025-68313, CVE-2025-68314, CVE-2025-68315,     CVE-2025-68316, CVE-2025-68317, CVE-2025-68318, CVE-2025-68319, CVE-2025-68320, CVE-2025-68321,     CVE-2025-68322, CVE-2025-68734)

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.

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

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

    crypto: essiv - Check ssize for decryption and in-place encryption (CVE-2025-40019)

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

    mm/ksm: fix flag-dropping behavior in ksm_madvise (CVE-2025-40040)

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

    tracing: Fix race condition in kprobe initialization causing NULL pointer dereference (CVE-2025-40042)

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

    cifs: parse_dfs_referrals: prevent oob on malformed input (CVE-2025-40099)

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

    btrfs: do not assert we found block group item when creating free space tree (CVE-2025-40100)

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

    btrfs: fix memory leaks when rejecting a non SINGLE data profile without an RST (CVE-2025-40101)

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

    smb: client: Fix refcount leak for cifs_sb_tlink (CVE-2025-40103)

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

    ixgbevf: fix mailbox API compatibility by negotiating supported features (CVE-2025-40104)

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

    vfs: Don't leak disconnected dentries on umount (CVE-2025-40105)

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

    drm/vmwgfx: Fix a null-ptr access in the cursor snooper (CVE-2025-40110)

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

    drm/vmwgfx: Fix Use-after-free in validation (CVE-2025-40111)

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

    mptcp: Use __sk_dst_get() and dst_dev_rcu() in mptcp_active_enable(). (CVE-2025-40133)

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

    xsk: Harden userspace-supplied xdp_desc validation (CVE-2025-40159)

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

    xen/events: Return -EEXIST for bound VIRQs (CVE-2025-40160)

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

    ext4: detect invalid INLINE_DATA + EXTENTS flag combination (CVE-2025-40167)

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

    net/ip6_tunnel: Prevent perpetual tunnel growth (CVE-2025-40173)

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

    tls: wait for pending async decryptions if tls_strp_msg_hold fails (CVE-2025-40176)

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

    pid: Add a judgment for ns null in pid_nr_ns (CVE-2025-40178)

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

    ext4: verify orphan file size is not too big (CVE-2025-40179)

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

    x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP (CVE-2025-40181)

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

    bpf: Fix metadata_dst leak __bpf_redirect_neigh_v{4,6} (CVE-2025-40183)

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

    net/sctp: fix a null dereference in sctp_disposition sctp_sf_do_5_1D_ce() (CVE-2025-40187)

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

    ext4: guard against EA inode refcount underflow in xattr update (CVE-2025-40190)

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

    cpufreq: intel_pstate: Fix object lifecycle issue in update_qos_request() (CVE-2025-40194)

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

    mount: handle NULL values in mnt_ns_release() (CVE-2025-40195)

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

    fs: quota: create dedicated workqueue for quota_release_work (CVE-2025-40196)

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

    media: mc: Clear minor number before put device (CVE-2025-40197)

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

    ext4: avoid potential buffer over-read in parse_apply_sb_mount_options() (CVE-2025-40198)

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

    page_pool: Fix PP_MAGIC_MASK to avoid crashing on some 32-bit arches (CVE-2025-40199)

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

    Squashfs: reject negative file sizes in squashfs_read_inode() (CVE-2025-40200)

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

    kernel/sys.c: fix the racy usage of task_lock(tsk->group_leader) in sys_prlimit64() paths (CVE-2025-40201)

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

    ipmi: Rework user message limit handling (CVE-2025-40202)

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

    listmount: don't call path_put() under namespace semaphore (CVE-2025-40203)

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

    sctp: Fix MAC comparison to be constant-time (CVE-2025-40204)

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

    btrfs: avoid potential out-of-bounds in btrfs_encode_fh() (CVE-2025-40205)

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

    netfilter: nft_objref: validate objref and objrefmap expressions (CVE-2025-40206)

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

    media: v4l2-subdev: Fix alloc failure check in v4l2_subdev_call_state_try() (CVE-2025-40207)

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.

  - x86/kvm: Force legacy PCI hole to UC when overriding MTRRs for TDX/SNP When running as an SNP or TDX guest     under KVM, force the legacy PCI hole, i.e. memory between Top of Lower Usable DRAM and 4GiB, to be mapped     as UC via a forced variable MTRR range. In most KVM-based setups, legacy devices such as the HPET and TPM     are enumerated via ACPI. ACPI enumeration includes a Memory32Fixed entry, and optionally a SystemMemory     descriptor for an OperationRegion, e.g. if the device needs to be accessed via a Control Method. If a     SystemMemory entry is present, then the kernel's ACPI driver will auto-ioremap the region so that it can     be accessed at will. However, the ACPI spec doesn't provide a way to enumerate the memory type of     SystemMemory regions, i.e. there's no way to tell software that a region must be mapped as UC vs. WB, etc.
    As a result, Linux's ACPI driver always maps SystemMemory regions using ioremap_cache(), i.e. as WB on     x86. The dedicated device drivers however, e.g. the HPET driver and TPM driver, want to map their     associated memory as UC or WC, as accessing PCI devices using WB is unsupported. On bare metal and non-     CoCO, the conflicting requirements work as firmware configures the PCI hole (and other device memory) to     be UC in the MTRRs. So even though the ACPI mappings request WB, they are forced to UC- in the kernel's     tracking due to the kernel properly handling the MTRR overrides, and thus are compatible with the drivers'     requested WC/UC-. With force WB MTRRs on SNP and TDX guests, the ACPI mappings get their requested WB if     the ACPI mappings are established before the dedicated driver code attempts to initialize the device. E.g.
    if acpi_init() runs before the corresponding device driver is probed, ACPI's WB mapping will win, and     result in the driver's ioremap() failing because the existing WB mapping isn't compatible with the     requested WC/UC-. E.g. when a TPM is emulated by the hypervisor (ignoring the security implications of     relying on what is allegedly an untrusted entity to store measurements), the TPM driver will request UC     and fail: [ 1.730459] ioremap error for 0xfed40000-0xfed45000, requested 0x2, got 0x0 [ 1.732780] tpm_tis     MSFT0101:00: probe with driver tpm_tis failed with error -12 Note, the '0x2' and '0x0' values refer to     enum page_cache_mode, not x86's memtypes (which frustratingly are an almost pure inversion; 2 == WB, 0     == UC). E.g. tracing mapping requests for TPM TIS yields: Mapping TPM TIS with req_type = 0 WARNING: CPU:
    22 PID: 1 at arch/x86/mm/pat/memtype.c:530 memtype_reserve+0x2ab/0x460 Modules linked in: CPU: 22 UID: 0     PID: 1 Comm: swapper/0 Tainted: G W 6.16.0-rc7+ #2 VOLUNTARY Tainted: [W]=WARN Hardware name: Google     Google Compute Engine/Google Compute Engine, BIOS Google 05/29/2025 RIP: 0010:memtype_reserve+0x2ab/0x460
    __ioremap_caller+0x16d/0x3d0 ioremap_cache+0x17/0x30 x86_acpi_os_ioremap+0xe/0x20     acpi_os_map_iomem+0x1f3/0x240 acpi_os_map_memory+0xe/0x20 acpi_ex_system_memory_space_handler+0x273/0x440     acpi_ev_address_space_dispatch+0x176/0x4c0 acpi_ex_access_region+0x2ad/0x530     acpi_ex_field_datum_io+0xa2/0x4f0 acpi_ex_extract_from_field+0x296/0x3e0     acpi_ex_read_data_from_field+0xd1/0x460 acpi_ex_resolve_node_to_value+0x2ee/0x530     acpi_ex_resolve_to_value+0x1f2/0x540 acpi_ds_evaluate_name_path+0x11b/0x190     acpi_ds_exec_end_op+0x456/0x960 acpi_ps_parse_loop+0x27a/0xa50 acpi_ps_parse_aml+0x226/0x600     acpi_ps_execute_method+0x172/0x3e0 acpi_ns_evaluate+0x175/0x5f0 acpi_evaluate_object+0x213/0x490     acpi_evaluate_integer+0x6d/0x140 acpi_bus_get_status+0x93/0x150 acpi_add_single_object+0x43a/0x7c0     acpi_bus_check_add+0x149/0x3a0 acpi_bus_check_add_1+0x16/0x30 acpi_ns_walk_namespace+0x22c/0x360     acpi_walk_namespace+0x15c/0x170 acpi_bus_scan+0x1dd/0x200 acpi_scan_init+0xe5/0x2b0 acpi_init+0x264/0x5b0     do_one_i ---truncated--- (CVE-2025-40181)

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

ID	Name	Product	Family	Severity
299715	SUSE SLES15 Security Update : kernel (SUSE-SU-2026:0587-1)	Nessus	SuSE Local Security Checks	high
299491	Ubuntu 24.04 LTS : Linux kernel (OEM) vulnerabilities (USN-8048-1)	Nessus	Ubuntu Local Security Checks	critical
298917	SUSE SLES15 Security Update : kernel (SUSE-SU-2026:0472-1)	Nessus	SuSE Local Security Checks	high
298897	Ubuntu 25.10 : Linux kernel vulnerabilities (USN-8029-1)	Nessus	Ubuntu Local Security Checks	critical
298739	SUSE SLED15 / SLES15 Security Update : kernel (SUSE-SU-2026:0447-1)	Nessus	SuSE Local Security Checks	high
277808	Amazon Linux 2023 : bpftool6.12, kernel6.12, kernel6.12-devel (ALAS2023-2025-1316)	Nessus	Amazon Linux Local Security Checks	high
275354	Linux Distros Unpatched Vulnerability : CVE-2025-40181	Nessus	Misc.	high

Detections

Analytics

CVE-2025-40181

medium

Tenable Plugins

high

critical

high

critical

high

high

high