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

    - PowerPC architecture;

    - RISC-V architecture;

    - S390 architecture;

    - SuperH RISC architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - ACPI drivers;

    - Drivers core;

    - RAM backed block device driver;

    - Virtio block driver;

    - Data acquisition framework and drivers;

    - Hardware crypto device drivers;

    - DMA engine subsystem;

    - EDAC drivers;

    - ARM SCPI message protocol;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Microsoft Hyper-V drivers;

    - I3C subsystem;

    - IIO ADC drivers;

    - IIO subsystem;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - LED subsystem;

    - Multiple devices driver;

    - Media drivers;

    - Multifunction device drivers;

    - MMC subsystem;

    - MTD block device drivers;

    - Network drivers;

    - Mellanox network drivers;

    - Microsoft Azure Network Adapter (MANA) driver;

    - NVME drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - Power supply drivers;

    - Real Time Clock drivers;

    - SCSI subsystem;

    - SuperH / SH-Mobile drivers;

    - i.MX SoC drivers;

    - QCOM SoC drivers;

    - SPI subsystem;

    - Media staging drivers;

    - UFS subsystem;

    - DesignWare USB3 driver;

    - USB Gadget drivers;

    - USB Serial drivers;

    - USB Type-C Port Controller Manager driver;

    - VFIO drivers;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - AFS file system;

    - BTRFS file system;

    - Ceph distributed file system;

    - File systems infrastructure;

    - F2FS file system;

    - GFS2 file system;

    - JFFS2 file system;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - NTFS3 file system;

    - Overlay file system;

    - Proc file system;

    - Diskquota system;

    - SMB network file system;

    - UBI file system;

    - Timer subsystem;

    - VLANs driver;

    - LAPB network protocol;

    - Network namespace;

    - Kernel init infrastructure;

    - BPF subsystem;

    - Kernel CPU control infrastructure;

    - DMA mapping infrastructure;

    - KCSAN framework;

    - Tracing infrastructure;

    - Memory management;

    - 9P file system network protocol;

    - Bluetooth subsystem;

    - CAN network layer;

    - Networking core;

    - DCCP (Datagram Congestion Control Protocol);

    - Distributed Switch Architecture;

    - HSR network protocol;

    - IEEE802154.4 network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - IEEE 802.15.4 subsystem;

    - Multipath TCP;

    - Netfilter;

    - Netlink;

    - NET/ROM layer;

    - Packet sockets;

    - Network traffic control;

    - SCTP protocol;

    - SMC sockets;

    - Sun RPC protocol;

    - TIPC protocol;

    - VMware vSockets driver;

    - eXpress Data Path;

    - SELinux security module;

    - ALSA framework;

    - USB sound devices; (CVE-2024-53680, CVE-2024-53148, CVE-2024-47408, CVE-2024-53122, CVE-2024-56691,     CVE-2024-56763, CVE-2024-53227, CVE-2024-56369, CVE-2024-50275, CVE-2024-57892, CVE-2024-53142,     CVE-2024-56693, CVE-2024-56658, CVE-2024-57882, CVE-2024-56606, CVE-2024-46871, CVE-2024-57907,     CVE-2024-56642, CVE-2025-21631, CVE-2024-57908, CVE-2024-57890, CVE-2024-53194, CVE-2024-57913,     CVE-2024-56659, CVE-2024-56643, CVE-2024-56590, CVE-2024-56754, CVE-2025-21678, CVE-2024-56678,     CVE-2024-49974, CVE-2024-56614, CVE-2024-53124, CVE-2022-49034, CVE-2024-49996, CVE-2024-47143,     CVE-2024-50055, CVE-2024-53184, CVE-2024-56681, CVE-2025-21683, CVE-2024-57922, CVE-2024-56532,     CVE-2024-53161, CVE-2024-57791, CVE-2025-21664, CVE-2024-53206, CVE-2024-56589, CVE-2024-57902,     CVE-2024-56633, CVE-2024-53140, CVE-2024-56627, CVE-2024-57912, CVE-2024-55916, CVE-2024-56594,     CVE-2025-21690, CVE-2024-56602, CVE-2024-49998, CVE-2024-53171, CVE-2024-53174, CVE-2024-53172,     CVE-2024-56701, CVE-2024-52332, CVE-2024-57948, CVE-2024-57802, CVE-2024-53237, CVE-2024-50304,     CVE-2024-56568, CVE-2024-49571, CVE-2025-21636, CVE-2024-57906, CVE-2024-57939, CVE-2024-57931,     CVE-2024-56698, CVE-2024-56781, CVE-2024-50051, CVE-2024-57904, CVE-2024-43900, CVE-2024-53146,     CVE-2024-53217, CVE-2024-56548, CVE-2024-56616, CVE-2024-53155, CVE-2024-57889, CVE-2025-21666,     CVE-2024-53165, CVE-2024-56615, CVE-2024-56629, CVE-2024-53197, CVE-2024-47707, CVE-2024-53690,     CVE-2024-56572, CVE-2024-56748, CVE-2024-45828, CVE-2024-53156, CVE-2024-53150, CVE-2024-53181,     CVE-2024-56625, CVE-2024-57938, CVE-2024-56708, CVE-2024-57925, CVE-2024-56644, CVE-2024-50121,     CVE-2024-53125, CVE-2025-21697, CVE-2024-53180, CVE-2024-53129, CVE-2024-57910, CVE-2024-57951,     CVE-2024-46841, CVE-2024-56670, CVE-2024-56759, CVE-2024-56662, CVE-2024-56769, CVE-2024-56623,     CVE-2024-26928, CVE-2024-56777, CVE-2024-53183, CVE-2024-53135, CVE-2024-57884, CVE-2024-56778,     CVE-2024-56774, CVE-2024-53145, CVE-2024-56574, CVE-2025-21687, CVE-2024-53215, CVE-2024-57807,     CVE-2024-56704, CVE-2025-21665, CVE-2024-56637, CVE-2024-56601, CVE-2024-56650, CVE-2024-57911,     CVE-2024-57900, CVE-2024-56716, CVE-2025-21689, CVE-2024-56597, CVE-2024-56570, CVE-2024-56779,     CVE-2025-21653, CVE-2024-56747, CVE-2024-56622, CVE-2024-44938, CVE-2025-21639, CVE-2024-56578,     CVE-2024-56728, CVE-2024-53151, CVE-2024-56723, CVE-2024-53158, CVE-2024-56645, CVE-2024-56586,     CVE-2024-50242, CVE-2024-53099, CVE-2024-56726, CVE-2024-35864, CVE-2024-56739, CVE-2024-56785,     CVE-2024-46784, CVE-2024-56539, CVE-2024-57838, CVE-2024-57850, CVE-2024-56593, CVE-2024-53239,     CVE-2024-53173, CVE-2024-57901, CVE-2024-56595, CVE-2024-53138, CVE-2024-56724, CVE-2025-21699,     CVE-2025-21694, CVE-2024-49925, CVE-2024-53113, CVE-2024-56603, CVE-2024-53119, CVE-2024-53121,     CVE-2024-48881, CVE-2024-56745, CVE-2025-21637, CVE-2025-21640, CVE-2024-50283, CVE-2024-42069,     CVE-2024-53214, CVE-2024-56605, CVE-2024-53226, CVE-2024-56640, CVE-2024-57929, CVE-2024-56575,     CVE-2024-56700, CVE-2024-57903, CVE-2024-56776, CVE-2024-56679, CVE-2024-56648, CVE-2025-21692,     CVE-2024-56558, CVE-2024-53198, CVE-2024-56787, CVE-2024-56600, CVE-2024-56576, CVE-2024-53120,     CVE-2024-56531, CVE-2024-56567, CVE-2025-21680, CVE-2024-56780, CVE-2024-56631, CVE-2024-56694,     CVE-2024-43098, CVE-2024-53127, CVE-2024-56626, CVE-2024-56598, CVE-2024-47730, CVE-2024-53130,     CVE-2024-56619, CVE-2024-56569, CVE-2024-57917, CVE-2024-56767, CVE-2024-56587, CVE-2024-56690,     CVE-2024-53112, CVE-2024-57946, CVE-2025-21638, CVE-2024-56770, CVE-2024-56596, CVE-2024-56720,     CVE-2024-36476, CVE-2024-56533, CVE-2025-21648, CVE-2024-56705, CVE-2025-21646, CVE-2024-57897,     CVE-2024-57798, CVE-2024-56636, CVE-2024-53096, CVE-2024-56715, CVE-2024-58087, CVE-2024-57841,     CVE-2024-46809, CVE-2024-56634, CVE-2024-53685, CVE-2024-56756, CVE-2024-56562, CVE-2024-57874,     CVE-2024-56581, CVE-2024-56630, CVE-2025-21669, CVE-2024-57896, CVE-2024-55881, CVE-2024-53157,     CVE-2024-56688, CVE-2024-57849, CVE-2024-53131, CVE-2024-56610, CVE-2024-57940, CVE-2024-57792,     CVE-2024-36899, CVE-2024-53136, CVE-2024-42315, CVE-2024-56746, CVE-2024-49950)

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 20.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7539-1 advisory.

    Chenyuan Yang discovered that the CEC driver driver in the Linux kernel contained a use-after-free     vulnerability. A local attacker could use this to cause a denial of service (system crash) or possibly     execute arbitrary code. (CVE-2024-23848)

    Attila Szsz discovered that the HFS+ file system implementation in the Linux Kernel contained a heap     overflow vulnerability. An attacker could use a specially crafted file system image that, when mounted,     could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2025-0927)

    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;

    - PowerPC architecture;

    - S390 architecture;

    - SuperH RISC architecture;

    - User-Mode Linux (UML);

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - ACPI drivers;

    - Drivers core;

    - ATA over ethernet (AOE) driver;

    - Network block device driver;

    - Virtio block driver;

    - Character device driver;

    - TPM device driver;

    - Data acquisition framework and drivers;

    - Hardware crypto device drivers;

    - DMA engine subsystem;

    - EDAC drivers;

    - ARM SCPI message protocol;

    - GPIO subsystem;

    - GPU drivers;

    - HID subsystem;

    - Microsoft Hyper-V drivers;

    - I2C subsystem;

    - I3C subsystem;

    - IIO ADC drivers;

    - IIO subsystem;

    - InfiniBand drivers;

    - LED subsystem;

    - Mailbox framework;

    - Multiple devices driver;

    - Media drivers;

    - Multifunction device drivers;

    - MMC subsystem;

    - MTD block device drivers;

    - Network drivers;

    - Mellanox network drivers;

    - NTB driver;

    - Virtio pmem driver;

    - NVME drivers;

    - Parport drivers;

    - PCI subsystem;

    - Pin controllers subsystem;

    - x86 platform drivers;

    - PPS (Pulse Per Second) driver;

    - PTP clock framework;

    - RapidIO drivers;

    - Real Time Clock drivers;

    - SCSI subsystem;

    - SuperH / SH-Mobile drivers;

    - SLIMbus drivers;

    - QCOM SoC drivers;

    - SPI subsystem;

    - Direct Digital Synthesis drivers;

    - Trusted Execution Environment drivers;

    - USB DSL drivers;

    - USB Device Class drivers;

    - USB core drivers;

    - USB Gadget drivers;

    - USB Host Controller drivers;

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

    - Renesas USBHS Controller drivers;

    - USB Serial drivers;

    - USB Type-C support driver;

    - USB Type-C Port Controller Manager driver;

    - VFIO drivers;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ceph distributed file system;

    - Ext4 file system;

    - F2FS file system;

    - GFS2 file system;

    - JFFS2 file system;

    - JFS file system;

    - Network file system (NFS) client;

    - Network file system (NFS) server daemon;

    - NILFS2 file system;

    - Overlay file system;

    - Proc file system;

    - Diskquota system;

    - SMB network file system;

    - UBI file system;

    - Timer subsystem;

    - VLANs driver;

    - KVM subsystem;

    - L3 Master device support module;

    - LAPB network protocol;

    - Network namespace;

    - Netfilter;

    - Network traffic control;

    - Network sockets;

    - TCP network protocol;

    - Kernel init infrastructure;

    - Process Accounting mechanism;

    - BPF subsystem;

    - Kernel CPU control infrastructure;

    - Perf events;

    - printk logging mechanism;

    - Arbitrary resource management;

    - Scheduler infrastructure;

    - Tracing infrastructure;

    - Closures library;

    - Memory management;

    - 802.1Q VLAN protocol;

    - 9P file system network protocol;

    - Amateur Radio drivers;

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

    - Bluetooth subsystem;

    - Ethernet bridge;

    - CAN network layer;

    - Networking core;

    - DCCP (Datagram Congestion Control Protocol);

    - IEEE802154.4 network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - Logical Link layer;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Netlink;

    - NET/ROM layer;

    - NFC subsystem;

    - Open vSwitch;

    - Packet sockets;

    - Rose network layer;

    - SCTP protocol;

    - Sun RPC protocol;

    - TIPC protocol;

    - Wireless networking;

    - eXpress Data Path;

    - XFRM subsystem;

    - Key management;

    - SELinux security module;

    - Tomoyo security module;

    - FireWire sound drivers;

    - AudioScience HPI driver;

    - Amlogic Meson SoC drivers;

    - USB sound devices; (CVE-2025-21814, CVE-2024-57938, CVE-2024-56605, CVE-2024-47747, CVE-2024-50251,     CVE-2021-47191, CVE-2024-49973, CVE-2024-53171, CVE-2024-50167, CVE-2024-53066, CVE-2024-57980,     CVE-2024-56558, CVE-2024-57906, CVE-2025-21846, CVE-2024-56576, CVE-2024-56593, CVE-2024-57850,     CVE-2024-56594, CVE-2024-50256, CVE-2024-49948, CVE-2024-38544, CVE-2024-58071, CVE-2024-58017,     CVE-2024-50282, CVE-2024-47737, CVE-2024-47740, CVE-2024-56548, CVE-2025-21925, CVE-2025-21689,     CVE-2024-46826, CVE-2024-26982, CVE-2024-53121, CVE-2024-50171, CVE-2024-50278, CVE-2024-50290,     CVE-2024-56597, CVE-2025-21708, CVE-2024-49867, CVE-2024-57849, CVE-2024-56769, CVE-2024-58010,     CVE-2025-21848, CVE-2024-50218, CVE-2024-53063, CVE-2025-21697, CVE-2023-52664, CVE-2024-50302,     CVE-2024-58014, CVE-2024-53112, CVE-2024-50099, CVE-2024-49884, CVE-2024-53138, CVE-2024-53183,     CVE-2024-56658, CVE-2024-57884, CVE-2024-50229, CVE-2024-53174, CVE-2024-47756, CVE-2024-49851,     CVE-2024-47699, CVE-2024-58072, CVE-2024-49878, CVE-2024-50148, CVE-2024-57904, CVE-2024-50045,     CVE-2024-53157, CVE-2024-53146, CVE-2024-50287, CVE-2024-49883, CVE-2024-56724, CVE-2024-58090,     CVE-2025-21722, CVE-2024-53061, CVE-2025-21664, CVE-2024-50265, CVE-2024-50168, CVE-2024-49894,     CVE-2024-50035, CVE-2024-57913, CVE-2024-57929, CVE-2024-48881, CVE-2024-58058, CVE-2024-56633,     CVE-2024-56756, CVE-2024-49925, CVE-2024-50233, CVE-2025-21639, CVE-2024-49944, CVE-2024-53194,     CVE-2025-21904, CVE-2024-56581, CVE-2025-21877, CVE-2025-21811, CVE-2024-53156, CVE-2024-57912,     CVE-2025-21653, CVE-2024-50024, CVE-2024-57931, CVE-2024-26928, CVE-2024-49949, CVE-2024-56688,     CVE-2024-47757, CVE-2024-56601, CVE-2024-56562, CVE-2025-21749, CVE-2024-47709, CVE-2025-21934,     CVE-2024-47674, CVE-2024-49879, CVE-2024-49924, CVE-2024-46731, CVE-2024-53214, CVE-2024-56659,     CVE-2024-50236, CVE-2025-21694, CVE-2024-47707, CVE-2024-53680, CVE-2024-41066, CVE-2024-56651,     CVE-2025-21718, CVE-2024-50279, CVE-2024-50040, CVE-2024-56598, CVE-2023-52927, CVE-2025-21862,     CVE-2024-49981, CVE-2024-50273, CVE-2024-50180, CVE-2025-21753, CVE-2024-49957, CVE-2024-56615,     CVE-2024-46854, CVE-2025-21721, CVE-2024-49962, CVE-2024-49974, CVE-2024-53217, CVE-2024-35887,     CVE-2024-53172, CVE-2024-58069, CVE-2024-53124, CVE-2024-50131, CVE-2024-53158, CVE-2024-57901,     CVE-2024-46849, CVE-2025-21917, CVE-2024-57892, CVE-2024-53131, CVE-2024-56587, CVE-2024-50151,     CVE-2024-49860, CVE-2024-53184, CVE-2025-21687, CVE-2024-56690, CVE-2025-21926, CVE-2024-47723,     CVE-2024-50195, CVE-2025-21760, CVE-2024-50142, CVE-2025-21910, CVE-2024-49997, CVE-2024-58083,     CVE-2024-52332, CVE-2025-21806, CVE-2025-21640, CVE-2025-21922, CVE-2024-58051, CVE-2024-56606,     CVE-2024-47698, CVE-2024-50044, CVE-2024-56574, CVE-2025-21785, CVE-2024-56532, CVE-2024-53165,     CVE-2024-56779, CVE-2024-50269, CVE-2024-47684, CVE-2024-50006, CVE-2024-47749, CVE-2024-56595,     CVE-2025-21736, CVE-2024-53198, CVE-2024-49952, CVE-2024-53104, CVE-2025-21772, CVE-2025-21914,     CVE-2024-53127, CVE-2024-50301, CVE-2024-53239, CVE-2024-47670, CVE-2021-47119, CVE-2025-21702,     CVE-2024-50296, CVE-2024-50033, CVE-2024-49975, CVE-2024-57900, CVE-2024-56596, CVE-2024-56569,     CVE-2024-47692, CVE-2024-56567, CVE-2024-56746, CVE-2024-47672, CVE-2025-21866, CVE-2024-58001,     CVE-2024-50202, CVE-2024-49955, CVE-2024-38588, CVE-2024-47706, CVE-2025-21700, CVE-2025-21763,     CVE-2024-47696, CVE-2024-53150, CVE-2024-53237, CVE-2024-40953, CVE-2024-53197, CVE-2024-49892,     CVE-2024-40965, CVE-2024-49903, CVE-2024-42252, CVE-2024-56642, CVE-2024-56739, CVE-2024-43098,     CVE-2024-57973, CVE-2023-52741, CVE-2024-50096, CVE-2025-21835, CVE-2024-49882, CVE-2025-21765,     CVE-2024-57889, CVE-2022-49034, CVE-2024-57946, CVE-2025-21735, CVE-2024-56720, CVE-2024-57890,     CVE-2024-50267, CVE-2025-21920, CVE-2024-56634, CVE-2024-56599, CVE-2024-47701, CVE-2024-56780,     CVE-2024-49900, CVE-2024-26689, CVE-2025-21638, CVE-2024-50150, CVE-2024-47679, CVE-2025-21776,     CVE-2024-49996, CVE-2024-49896, CVE-2024-53140, CVE-2024-50127, CVE-2024-53148, CVE-2024-49963,     CVE-2024-56645, CVE-2025-21859, CVE-2024-53135, CVE-2024-56614, CVE-2024-49985, CVE-2024-57948,     CVE-2024-50230, CVE-2024-57986, CVE-2024-56767, CVE-2024-50199, CVE-2024-53181, CVE-2024-49936,     CVE-2024-58052, CVE-2024-57910, CVE-2024-47671, CVE-2024-50134, CVE-2024-55916, CVE-2024-50184,     CVE-2024-56691, CVE-2024-26915, CVE-2024-58085, CVE-2025-21909, CVE-2024-44938, CVE-2024-41016,     CVE-2025-21761, CVE-2024-35958, CVE-2024-49982, CVE-2024-57911, CVE-2025-21858, CVE-2024-57981,     CVE-2024-53059, CVE-2024-26996, CVE-2025-21916, CVE-2025-21871, CVE-2021-47219, CVE-2024-50059,     CVE-2024-58020, CVE-2025-21744, CVE-2024-47710, CVE-2025-21699, CVE-2024-49958, CVE-2024-53155,     CVE-2024-53161, CVE-2024-56572, CVE-2024-49938, CVE-2024-53142, CVE-2024-53145, CVE-2024-50205,     CVE-2024-47712, CVE-2024-56704, CVE-2024-56619, CVE-2024-56603, CVE-2024-56650, CVE-2024-50007,     CVE-2024-56586, CVE-2025-21898, CVE-2024-49877, CVE-2024-56723, CVE-2024-50237, CVE-2025-21781,     CVE-2025-21762, CVE-2024-53130, CVE-2024-57802, CVE-2024-56602, CVE-2024-53101, CVE-2024-57977,     CVE-2025-21948, CVE-2024-47685, CVE-2024-35896, CVE-2024-58002, CVE-2024-49902, CVE-2024-50116,     CVE-2024-56531, CVE-2024-56600, CVE-2025-21787, CVE-2024-56630, CVE-2024-50055, CVE-2024-47713,     CVE-2024-56570, CVE-2024-46853, CVE-2024-57807, CVE-2023-52458, CVE-2024-44931, CVE-2025-21728,     CVE-2024-43900, CVE-2024-57951, CVE-2025-21782, CVE-2024-43863, CVE-2024-56781, CVE-2025-21971,     CVE-2024-56539, CVE-2024-57979, CVE-2024-50179, CVE-2024-56643, CVE-2025-21647, CVE-2024-50262,     CVE-2024-56629, CVE-2024-50234, CVE-2024-57922, CVE-2024-58063, CVE-2024-53690, CVE-2024-50082,     CVE-2024-57908, CVE-2024-53227, CVE-2024-58009, CVE-2024-56644, CVE-2024-56681, CVE-2024-58007,     CVE-2024-56637, CVE-2024-50074, CVE-2025-21731, CVE-2024-49965, CVE-2025-21823, CVE-2024-56747,     CVE-2025-21935, CVE-2025-21905, CVE-2024-47742, CVE-2024-56670, CVE-2024-50143, CVE-2025-21715,     CVE-2024-35864, CVE-2024-50039, CVE-2024-56694, CVE-2025-21678, CVE-2024-58055, CVE-2024-50117,     CVE-2024-49868, CVE-2024-56748, CVE-2025-21764, CVE-2024-49959, CVE-2025-21704, CVE-2024-57902,     CVE-2025-21928, CVE-2024-50299, CVE-2025-21719, CVE-2025-21865, CVE-2024-50051, CVE-2024-47697,     CVE-2024-56631, CVE-2024-56770, CVE-2024-49966, CVE-2024-40911, CVE-2024-50194, CVE-2024-50008,     CVE-2024-53173, CVE-2025-21791, CVE-2024-56700)

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 AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1783791447 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot     reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED     indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but     device_register() was called In case of device_register() has been called we should call put_device() to     correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of     MDIOBUS_ALLOCATED state To avoid this behaviour we need to set bus->state to MDIOBUS_UNREGISTERED _before_     calling device_register(), because put_device() should be called even in case of device_register()     failure. (CVE-2021-47416)

  - An out-of-bounds read flaw was found in the Linux kernel's TeleTYpe subsystem. The issue occurs in how a     user triggers a race condition using ioctls TIOCSPTLCK and TIOCGPTPEER and TIOCSTI and TCXONC with leakage     of memory in the flush_to_ldisc function. This flaw allows a local user to crash the system or read     unauthorized random data from memory. (CVE-2022-1462)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in     isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached     with a compliant CAN ID address configuration. The provided address information consisted of CAN ID     0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the     SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)

  - In the Linux kernel, the following vulnerability has been resolved: tty: fix deadlock caused by calling     printk() under tty_port->lock pty_write() invokes kmalloc() which may invoke a normal printk() to print     failure message. This can cause a deadlock in the scenario reported by syz-bot below: CPU0 CPU1 CPU2 ----
    ---- ---- lock(console_owner); lock(&port_lock_key); lock(&port->lock); lock(&port_lock_key);
    lock(&port->lock); lock(console_owner); As commit dbdda842fe96 (printk: Add console owner and waiter     logic to load balance console writes) said, such deadlock can be prevented by using printk_deferred() in     kmalloc() (which is invoked in the section guarded by the port->lock). But there are too many printk() on     the kmalloc() path, and kmalloc() can be called from anywhere, so changing printk() to printk_deferred()     is too complicated and inelegant. Therefore, this patch chooses to specify __GFP_NOWARN to kmalloc(), so     that printk() will not be called, and this deadlock problem can be avoided. Syzbot reported the following     lockdep error: ====================================================== WARNING: possible circular locking     dependency detected 5.4.143-00237-g08ccc19a-dirty #10 Not tainted
    ------------------------------------------------------ syz-executor.4/29420 is trying to acquire lock:
    ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: console_trylock_spinning kernel/printk/printk.c:1752     [inline] ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: vprintk_emit+0x2ca/0x470     kernel/printk/printk.c:2023 but task is already holding lock: ffff8880119c9158 (&port->lock){-.-.}-{2:2},     at: pty_write+0xf4/0x1f0 drivers/tty/pty.c:120 which lock already depends on the new lock. the existing     dependency chain (in reverse order) is: -> #2 (&port->lock){-.-.}-{2:2}: __raw_spin_lock_irqsave     include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x35/0x50     kernel/locking/spinlock.c:159 tty_port_tty_get drivers/tty/tty_port.c:288 [inline] <-- lock(&port->lock);
    tty_port_default_wakeup+0x1d/0xb0 drivers/tty/tty_port.c:47 serial8250_tx_chars+0x530/0xa80     drivers/tty/serial/8250/8250_port.c:1767 serial8250_handle_irq.part.0+0x31f/0x3d0     drivers/tty/serial/8250/8250_port.c:1854 serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1827     [inline] <-- lock(&port_lock_key); serial8250_default_handle_irq+0xb2/0x220     drivers/tty/serial/8250/8250_port.c:1870 serial8250_interrupt+0xfd/0x200     drivers/tty/serial/8250/8250_core.c:126 __handle_irq_event_percpu+0x109/0xa50 kernel/irq/handle.c:156     [...] -> #1 (&port_lock_key){-.-.}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110     [inline] _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159     serial8250_console_write+0x184/0xa40 drivers/tty/serial/8250/8250_port.c:3198 <-- lock(&port_lock_key);
    call_console_drivers kernel/printk/printk.c:1819 [inline] console_unlock+0x8cb/0xd00     kernel/printk/printk.c:2504 vprintk_emit+0x1b5/0x470 kernel/printk/printk.c:2024 <-- lock(console_owner);
    vprintk_func+0x8d/0x250 kernel/printk/printk_safe.c:394 printk+0xba/0xed kernel/printk/printk.c:2084     register_console+0x8b3/0xc10 kernel/printk/printk.c:2829 univ8250_console_init+0x3a/0x46     drivers/tty/serial/8250/8250_core.c:681 console_init+0x49d/0x6d3 kernel/printk/printk.c:2915     start_kernel+0x5e9/0x879 init/main.c:713 secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:241 ->     #0 (console_owner){....}-{0:0}: [...] lock_acquire+0x127/0x340 kernel/locking/lockdep.c:4734     console_trylock_spinning kernel/printk/printk.c:1773 ---truncated--- (CVE-2022-49441)

  - In the Linux kernel, the following vulnerability has been resolved: list: fix a data-race around     ep->rdllist ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is     empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses to it need some protection to     avoid store/load-tearing. Note INIT_LIST_HEAD_RCU() already has the annotation for both prev and next.
    Commit bf3b9f6372c4 (epoll: Add busy poll support to epoll with socket fds.) added the first lockless     ep_events_available(), and commit c5a282e9635e (fs/epoll: reduce the scope of wq lock in epoll_wait())     made some ep_events_available() calls lockless and added single call under a lock, finally commit     e59d3c64cba6 (epoll: eliminate unnecessary lock for zero timeout) made the last ep_events_available()     lockless. BUG: KCSAN: data-race in do_epoll_wait / do_epoll_wait write to 0xffff88810480c7d8 of 8 bytes by     task 1802 on cpu 0: INIT_LIST_HEAD include/linux/list.h:38 [inline] list_splice_init     include/linux/list.h:492 [inline] ep_start_scan fs/eventpoll.c:622 [inline] ep_send_events     fs/eventpoll.c:1656 [inline] ep_poll fs/eventpoll.c:1806 [inline] do_epoll_wait+0x4eb/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff88810480c7d8 of 8 bytes     by task 1799 on cpu 1: list_empty_careful include/linux/list.h:329 [inline] ep_events_available     fs/eventpoll.c:381 [inline] ep_poll fs/eventpoll.c:1797 [inline] do_epoll_wait+0x279/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0xffff88810480c7d0 ->     0xffff888103c15098 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1799 Comm: syz-fuzzer Tainted:
    G W 5.17.0-rc7-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS     Google 01/01/2011 (CVE-2022-49443)

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

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

    - sunrpc: handle SVC_GARBAGE during svc auth processing as auth error (Jeff Layton)  [Orabug: 38137447]     {CVE-2025-38089}
    - Add Zen34 clients (Borislav Petkov (AMD))  [Orabug: 38172252]  {CVE-2024-36350} {CVE-2024-36357}
    - x86/process: Move the buffer clearing before MONITOR (Kim Phillips)  [Orabug: 38172252]     {CVE-2024-36350} {CVE-2024-36357}
    - Add normal counters (Borislav Petkov (AMD))  [Orabug: 38172252]  {CVE-2024-36350} {CVE-2024-36357}
    - KVM: SVM: Advertize TSA CPUID bits to guests (Borislav Petkov (AMD))  [Orabug: 38172252]     {CVE-2024-36350} {CVE-2024-36357}
    - x86/bugs: Add a Transient Scheduler Attacks mitigation (Borislav Petkov (AMD))  [Orabug: 38172252]     {CVE-2024-36350} {CVE-2024-36357}

Tenable has extracted the preceding description block directly from the Oracle Linux security advisory.

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

ID	Name	Product	Family	Published	Updated	Severity
233966	Ubuntu 20.04 LTS : Linux kernel (Azure) vulnerabilities (USN-7421-1)	Nessus	Ubuntu Local Security Checks	4/7/2025	6/3/2026	high
237324	RHEL 9 : kernel (RHSA-2025:6966)	Nessus	Red Hat Local Security Checks	5/27/2025	10/28/2025	critical
237432	Ubuntu 20.04 LTS : Linux kernel (Raspberry Pi) vulnerabilities (USN-7539-1)	Nessus	Ubuntu Local Security Checks	5/28/2025	1/6/2026	critical
352871	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1783791447)	Nessus	Alma Linux Local Security Checks	9/30/2026	10/22/2026	low
252244	Oracle Linux 10 / 9 : Unbreakable Enterprise kernel (ELSA-2025-20530)	Nessus	Oracle Linux Local Security Checks	8/19/2025	2/9/2026	medium

Detections

Analytics

Plugins Search

high

critical

critical

low

medium