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

    - S390 architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - ATM drivers;

    - Device frequency scaling framework;

    - GPU drivers;

    - Hardware monitoring drivers;

    - VMware VMCI Driver;

    - Network drivers;

    - Device tree and open firmware driver;

    - SCSI drivers;

    - Greybus lights staging drivers;

    - BTRFS file system;

    - File systems infrastructure;

    - F2FS file system;

    - JFS file system;

    - NILFS2 file system;

    - Netfilter;

    - Memory management;

    - Ethernet bridge;

    - IPv6 networking;

    - IUCV driver;

    - Logical Link layer;

    - MAC80211 subsystem;

    - NFC subsystem;

    - Network traffic control;

    - Unix domain sockets; (CVE-2023-52614, CVE-2024-26633, CVE-2024-46758, CVE-2024-46723, CVE-2023-52502,     CVE-2024-41059, CVE-2024-44987, CVE-2024-36020, CVE-2023-52599, CVE-2023-52639, CVE-2024-26668,     CVE-2024-42094, CVE-2022-48938, CVE-2022-48733, CVE-2024-27397, CVE-2023-52578, CVE-2024-38560,     CVE-2024-38538, CVE-2024-42310, CVE-2024-46722, CVE-2024-46800, CVE-2024-41095, CVE-2024-42104,     CVE-2024-35877, CVE-2022-48943, CVE-2024-46743, CVE-2023-52531, CVE-2024-46757, CVE-2024-36953,     CVE-2024-46756, CVE-2024-38596, CVE-2023-52612, CVE-2024-38637, CVE-2024-41071, CVE-2024-46759,     CVE-2024-43882, CVE-2024-26675, CVE-2024-43854, CVE-2024-44942, CVE-2024-44998, CVE-2024-42240,     CVE-2024-41089, CVE-2024-26636, CVE-2024-46738, CVE-2024-42309)

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

    Lyu Tao discovered that the NFS implementation in the Linux kernel did not properly handle requests to     open a directory on a regular file. A local attacker could use this to expose sensitive information     (kernel memory).

    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:

    - x86 architecture;

    - ATM drivers;

    - Device frequency scaling framework;

    - GPU drivers;

    - Hardware monitoring drivers;

    - VMware VMCI Driver;

    - MTD block device drivers;

    - Network drivers;

    - Device tree and open firmware driver;

    - SCSI subsystem;

    - USB Serial drivers;

    - BTRFS file system;

    - File systems infrastructure;

    - F2FS file system;

    - JFS file system;

    - NILFS2 file system;

    - Netfilter;

    - Memory management;

    - Ethernet bridge;

    - IPv6 networking;

    - Logical Link layer;

    - MAC80211 subsystem;

    - NFC subsystem;

    - Network traffic control; (CVE-2021-47055, CVE-2024-26675, CVE-2024-42244, CVE-2024-46743,     CVE-2024-41095, CVE-2024-46756, CVE-2024-46723, CVE-2024-46759, CVE-2024-35877, CVE-2024-38538,     CVE-2024-26668, CVE-2024-44998, CVE-2024-42309, CVE-2024-46758, CVE-2024-46800, CVE-2022-48733,     CVE-2023-52531, CVE-2023-52599, CVE-2024-46722, CVE-2024-42240, CVE-2024-44987, CVE-2023-52502,     CVE-2023-52578, CVE-2024-41059, CVE-2024-41071, CVE-2024-44942, CVE-2024-46738, CVE-2022-48943,     CVE-2023-52614, CVE-2024-27397, CVE-2024-38560, CVE-2024-43882, CVE-2024-42104, CVE-2024-46757,     CVE-2024-26636, CVE-2024-26633, CVE-2024-41089, CVE-2024-42310, CVE-2022-48938)

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-7003-4 advisory.

    It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing     xattr debug information. A local attacker could use this to cause a denial of service (system crash).
    (CVE-2024-40902)

    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:

    - MIPS architecture;

    - PowerPC architecture;

    - x86 architecture;

    - ACPI drivers;

    - Serial ATA and Parallel ATA drivers;

    - Drivers core;

    - GPIO subsystem;

    - GPU drivers;

    - Greybus drivers;

    - HID subsystem;

    - I2C subsystem;

    - IIO subsystem;

    - InfiniBand drivers;

    - Media drivers;

    - VMware VMCI Driver;

    - Network drivers;

    - Pin controllers subsystem;

    - S/390 drivers;

    - SCSI drivers;

    - USB subsystem;

    - JFFS2 file system;

    - JFS file system;

    - File systems infrastructure;

    - NILFS2 file system;

    - IOMMU subsystem;

    - Sun RPC protocol;

    - Netfilter;

    - Memory management;

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

    - CAN network layer;

    - Ceph Core library;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - IUCV driver;

    - MAC80211 subsystem;

    - NET/ROM layer;

    - Network traffic control;

    - SoC Audio for Freescale CPUs drivers; (CVE-2024-41034, CVE-2024-40984, CVE-2024-40987, CVE-2024-42119,     CVE-2024-42224, CVE-2024-42101, CVE-2024-42096, CVE-2024-41095, CVE-2024-42087, CVE-2024-42104,     CVE-2024-42148, CVE-2024-39495, CVE-2024-40980, CVE-2024-42223, CVE-2024-40961, CVE-2024-40988,     CVE-2024-42127, CVE-2024-42090, CVE-2024-42236, CVE-2024-40995, CVE-2024-41007, CVE-2024-40968,     CVE-2024-40901, CVE-2024-42097, CVE-2024-41041, CVE-2024-36974, CVE-2024-42115, CVE-2024-40978,     CVE-2024-38619, CVE-2024-41049, CVE-2024-41035, CVE-2024-41044, CVE-2024-42154, CVE-2024-39499,     CVE-2024-42070, CVE-2024-40959, CVE-2024-39487, CVE-2024-42157, CVE-2024-40916, CVE-2024-42076,     CVE-2024-41087, CVE-2024-42094, CVE-2024-42124, CVE-2024-40905, CVE-2024-42145, CVE-2024-40963,     CVE-2024-36894, CVE-2024-40942, CVE-2024-42092, CVE-2024-42153, CVE-2024-41089, CVE-2024-40912,     CVE-2023-52887, CVE-2024-40934, CVE-2024-41006, CVE-2024-39501, CVE-2024-42084, CVE-2024-39506,     CVE-2024-39509, CVE-2024-40943, CVE-2024-42106, CVE-2024-42093, CVE-2024-40902, CVE-2024-42086,     CVE-2024-40958, CVE-2024-39502, CVE-2024-42232, CVE-2024-42089, CVE-2024-37078, CVE-2024-39469,     CVE-2024-41046, CVE-2024-42102, CVE-2024-40974, CVE-2024-39505, CVE-2024-40960, CVE-2024-42105,     CVE-2024-40932, CVE-2024-40904, CVE-2024-40981, CVE-2024-39503, CVE-2024-41097, CVE-2024-40941,     CVE-2024-36978, CVE-2023-52803, CVE-2024-40945)

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 NewStart CGSL host, running version MAIN 7.02, has kernel packages installed that are affected by multiple vulnerabilities:

  - In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix racy issue from session     lookup and expire Increment the session reference count within the lock for lookup to avoid racy issue     with session expire. (CVE-2024-58087)

  - In the Linux kernel, the following vulnerability has been resolved: nouveau: fix instmem race condition     around ptr stores Running a lot of VK CTS in parallel against nouveau, once every few hours you might see     something like this crash. BUG: kernel NULL pointer dereference, address: 0000000000000008 PGD     8000000114e6e067 P4D 8000000114e6e067 PUD 109046067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI CPU: 7 PID:
    53891 Comm: deqp-vk Not tainted 6.8.0-rc6+ #27 Hardware name: Gigabyte Technology Co., Ltd. Z390 I AORUS     PRO WIFI/Z390 I AORUS PRO WIFI-CF, BIOS F8 11/05/2021 RIP: 0010:gp100_vmm_pgt_mem+0xe3/0x180 [nouveau]     Code: c7 48 01 c8 49 89 45 58 85 d2 0f 84 95 00 00 00 41 0f b7 46 12 49 8b 7e 08 89 da 42 8d 2c f8 48 8b     47 08 41 83 c7 01 48 89 ee <48> 8b 40 08 ff d0 0f 1f 00 49 8b 7e 08 48 89 d9 48 8d 75 04 48 c1 RSP:
    0000:ffffac20c5857838 EFLAGS: 00010202 RAX: 0000000000000000 RBX: 00000000004d8001 RCX: 0000000000000001     RDX: 00000000004d8001 RSI: 00000000000006d8 RDI: ffffa07afe332180 RBP: 00000000000006d8 R08:
    ffffac20c5857ad0 R09: 0000000000ffff10 R10: 0000000000000001 R11: ffffa07af27e2de0 R12: 000000000000001c     R13: ffffac20c5857ad0 R14: ffffa07a96fe9040 R15: 000000000000001c FS: 00007fe395eed7c0(0000)     GS:ffffa07e2c980000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2:
    0000000000000008 CR3: 000000011febe001 CR4: 00000000003706f0 DR0: 0000000000000000 DR1: 0000000000000000     DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: ... ?     gp100_vmm_pgt_mem+0xe3/0x180 [nouveau] ? gp100_vmm_pgt_mem+0x37/0x180 [nouveau] nvkm_vmm_iter+0x351/0xa20     [nouveau] ? __pfx_nvkm_vmm_ref_ptes+0x10/0x10 [nouveau] ? __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] ?
    __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] ? __lock_acquire+0x3ed/0x2170 ?
    __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau] nvkm_vmm_ptes_get_map+0xc2/0x100 [nouveau] ?
    __pfx_nvkm_vmm_ref_ptes+0x10/0x10 [nouveau] ? __pfx_gp100_vmm_pgt_mem+0x10/0x10 [nouveau]     nvkm_vmm_map_locked+0x224/0x3a0 [nouveau] Adding any sort of useful debug usually makes it go away, so I     hand wrote the function in a line, and debugged the asm. Every so often pt->memory->ptrs is NULL. This     ptrs ptr is set in the nv50_instobj_acquire called from nvkm_kmap. If Thread A and Thread B both get to     nv50_instobj_acquire around the same time, and Thread A hits the refcount_set line, and in lockstep thread     B succeeds at refcount_inc_not_zero, there is a chance the ptrs value won't have been stored since     refcount_set is unordered. Force a memory barrier here, I picked smp_mb, since we want it on all CPUs and     it's write followed by a read. v2: use paired smp_rmb/smp_wmb. (CVE-2024-26984)

  - In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix use-after-free bugs     caused by sco_sock_timeout When the sco connection is established and then, the sco socket is releasing,     timeout_work will be scheduled to judge whether the sco disconnection is timeout. The sock will be     deallocated later, but it is dereferenced again in sco_sock_timeout. As a result, the use-after-free bugs     will happen. The root cause is shown below: Cleanup Thread | Worker Thread sco_sock_release |     sco_sock_close | __sco_sock_close | sco_sock_set_timer | schedule_delayed_work | sco_sock_kill | (wait a     time) sock_put(sk) //FREE | sco_sock_timeout | sock_hold(sk) //USE The KASAN report triggered by POC is     shown below: [ 95.890016] ================================================================== [ 95.890496]     BUG: KASAN: slab-use-after-free in sco_sock_timeout+0x5e/0x1c0 [ 95.890755] Write of size 4 at addr     ffff88800c388080 by task kworker/0:0/7 ... [ 95.890755] Workqueue: events sco_sock_timeout [ 95.890755]     Call Trace: [ 95.890755] <TASK> [ 95.890755] dump_stack_lvl+0x45/0x110 [ 95.890755]     print_address_description+0x78/0x390 [ 95.890755] print_report+0x11b/0x250 [ 95.890755] ?
    __virt_addr_valid+0xbe/0xf0 [ 95.890755] ? sco_sock_timeout+0x5e/0x1c0 [ 95.890755]     kasan_report+0x139/0x170 [ 95.890755] ? update_load_avg+0xe5/0x9f0 [ 95.890755] ?     sco_sock_timeout+0x5e/0x1c0 [ 95.890755] kasan_check_range+0x2c3/0x2e0 [ 95.890755]     sco_sock_timeout+0x5e/0x1c0 [ 95.890755] process_one_work+0x561/0xc50 [ 95.890755]     worker_thread+0xab2/0x13c0 [ 95.890755] ? pr_cont_work+0x490/0x490 [ 95.890755] kthread+0x279/0x300 [     95.890755] ? pr_cont_work+0x490/0x490 [ 95.890755] ? kthread_blkcg+0xa0/0xa0 [ 95.890755]     ret_from_fork+0x34/0x60 [ 95.890755] ? kthread_blkcg+0xa0/0xa0 [ 95.890755] ret_from_fork_asm+0x11/0x20 [     95.890755] </TASK> [ 95.890755] [ 95.890755] Allocated by task 506: [ 95.890755]     kasan_save_track+0x3f/0x70 [ 95.890755] __kasan_kmalloc+0x86/0x90 [ 95.890755] __kmalloc+0x17f/0x360 [     95.890755] sk_prot_alloc+0xe1/0x1a0 [ 95.890755] sk_alloc+0x31/0x4e0 [ 95.890755] bt_sock_alloc+0x2b/0x2a0     [ 95.890755] sco_sock_create+0xad/0x320 [ 95.890755] bt_sock_create+0x145/0x320 [ 95.890755]
    __sock_create+0x2e1/0x650 [ 95.890755] __sys_socket+0xd0/0x280 [ 95.890755] __x64_sys_socket+0x75/0x80 [     95.890755] do_syscall_64+0xc4/0x1b0 [ 95.890755] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 95.890755] [     95.890755] Freed by task 506: [ 95.890755] kasan_save_track+0x3f/0x70 [ 95.890755]     kasan_save_free_info+0x40/0x50 [ 95.890755] poison_slab_object+0x118/0x180 [ 95.890755]
    __kasan_slab_free+0x12/0x30 [ 95.890755] kfree+0xb2/0x240 [ 95.890755] __sk_destruct+0x317/0x410 [     95.890755] sco_sock_release+0x232/0x280 [ 95.890755] sock_close+0xb2/0x210 [ 95.890755] __fput+0x37f/0x770     [ 95.890755] task_work_run+0x1ae/0x210 [ 95.890755] get_signal+0xe17/0xf70 [ 95.890755]     arch_do_signal_or_restart+0x3f/0x520 [ 95.890755] syscall_exit_to_user_mode+0x55/0x120 [ 95.890755]     do_syscall_64+0xd1/0x1b0 [ 95.890755] entry_SYSCALL_64_after_hwframe+0x67/0x6f [ 95.890755] [ 95.890755]     The buggy address belongs to the object at ffff88800c388000 [ 95.890755] which belongs to the cache     kmalloc-1k of size 1024 [ 95.890755] The buggy address is located 128 bytes inside of [ 95.890755] freed     1024-byte region [ffff88800c388000, ffff88800c388400) [ 95.890755] [ 95.890755] The buggy address belongs     to the physical page: [ 95.890755] page: refcount:1 mapcount:0 mapping:0000000000000000     index:0xffff88800c38a800 pfn:0xc388 [ 95.890755] head: order:3 entire_mapcount:0 nr_pages_mapped:0     pincount:0 [ 95.890755] ano ---truncated--- (CVE-2024-27398)

  - In the Linux kernel, the following vulnerability has been resolved: firewire: nosy: ensure user_length is     taken into account when fetching packet contents Ensure that packet_buffer_get respects the user_length     provided. If the length of the head packet exceeds the user_length, packet_buffer_get will now return 0 to     signify to the user that no data were read and a larger buffer size is required. Helps prevent user space     overflows. (CVE-2024-27401)

  - In the Linux kernel, the following vulnerability has been resolved: riscv: process: Fix kernel gp leakage     childregs represents the registers which are active for the new thread in user context. For a kernel     thread, childregs->gp is never used since the kernel gp is not touched by switch_to. For a user mode     helper, the gp value can be observed in user space after execve or possibly by other means. [From the     email thread] The /* Kernel thread */ comment is somewhat inaccurate in that it is also used for     user_mode_helper threads, which exec a user process, e.g. /sbin/init or when /proc/sys/kernel/core_pattern     is a pipe. Such threads do not have PF_KTHREAD set and are valid targets for ptrace etc. even before they     exec. childregs is the *user* context during syscall execution and it is observable from userspace in at     least five ways: 1. kernel_execve does not currently clear integer registers, so the starting register     state for PID 1 and other user processes started by the kernel has sp = user stack, gp = kernel
    __global_pointer$, all other integer registers zeroed by the memset in the patch comment. This is a bug in     its own right, but I'm unwilling to bet that it is the only way to exploit the issue addressed by this     patch. 2. ptrace(PTRACE_GETREGSET): you can PTRACE_ATTACH to a user_mode_helper thread before it execs,     but ptrace requires SIGSTOP to be delivered which can only happen at user/kernel boundaries. 3.
    /proc/*/task/*/syscall: this is perfectly happy to read pt_regs for user_mode_helpers before the exec     completes, but gp is not one of the registers it returns. 4. PERF_SAMPLE_REGS_USER: LOCKDOWN_PERF normally     prevents access to kernel addresses via PERF_SAMPLE_REGS_INTR, but due to this bug kernel addresses are     also exposed via PERF_SAMPLE_REGS_USER which is permitted under LOCKDOWN_PERF. I have not attempted to     write exploit code. 5. Much of the tracing infrastructure allows access to user registers. I have not     attempted to determine which forms of tracing allow access to user registers without already allowing     access to kernel registers. (CVE-2024-35871)

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 / 22.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-7007-3 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)

    Chenyuan Yang discovered that the USB Gadget subsystem in the Linux kernel did not properly check for the     device to be enabled before writing. A local attacker could possibly use this to cause a denial of     service. (CVE-2024-25741)

    It was discovered that the JFS file system contained an out-of-bounds read vulnerability when printing     xattr debug information. A local attacker could use this to cause a denial of service (system crash).
    (CVE-2024-40902)

    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;

    - M68K architecture;

    - MIPS architecture;

    - PowerPC architecture;

    - RISC-V architecture;

    - x86 architecture;

    - Block layer subsystem;

    - Cryptographic API;

    - Accessibility subsystem;

    - ACPI drivers;

    - Serial ATA and Parallel ATA drivers;

    - Drivers core;

    - Bluetooth drivers;

    - Character device driver;

    - CPU frequency scaling framework;

    - Hardware crypto device drivers;

    - Buffer Sharing and Synchronization framework;

    - DMA engine subsystem;

    - FPGA Framework;

    - GPIO subsystem;

    - GPU drivers;

    - Greybus drivers;

    - HID subsystem;

    - HW tracing;

    - I2C subsystem;

    - IIO subsystem;

    - InfiniBand drivers;

    - Input Device (Mouse) drivers;

    - Macintosh device drivers;

    - Multiple devices driver;

    - Media drivers;

    - VMware VMCI Driver;

    - Network drivers;

    - Near Field Communication (NFC) drivers;

    - NVME drivers;

    - Pin controllers subsystem;

    - PTP clock framework;

    - S/390 drivers;

    - SCSI drivers;

    - SoundWire subsystem;

    - Greybus lights staging drivers;

    - Media staging drivers;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - DesignWare USB3 driver;

    - Framebuffer layer;

    - ACRN Hypervisor Service Module driver;

    - eCrypt file system;

    - File systems infrastructure;

    - Ext4 file system;

    - F2FS file system;

    - JFFS2 file system;

    - JFS file system;

    - NILFS2 file system;

    - NTFS3 file system;

    - SMB network file system;

    - IOMMU subsystem;

    - Memory management;

    - Netfilter;

    - BPF subsystem;

    - Kernel debugger infrastructure;

    - DMA mapping infrastructure;

    - IRQ subsystem;

    - Tracing infrastructure;

    - 9P file system network protocol;

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

    - CAN network layer;

    - Ceph Core library;

    - Networking core;

    - IPv4 networking;

    - IPv6 networking;

    - IUCV driver;

    - MAC80211 subsystem;

    - Multipath TCP;

    - NET/ROM layer;

    - NFC subsystem;

    - Open vSwitch;

    - Network traffic control;

    - TIPC protocol;

    - TLS protocol;

    - Unix domain sockets;

    - Wireless networking;

    - XFRM subsystem;

    - ALSA framework;

    - SoC Audio for Freescale CPUs drivers;

    - Kirkwood ASoC drivers; (CVE-2024-42105, CVE-2024-41002, CVE-2024-38558, CVE-2023-52887, CVE-2024-39487,     CVE-2024-39276, CVE-2024-42077, CVE-2024-39493, CVE-2024-40934, CVE-2024-39277, CVE-2024-42087,     CVE-2024-38598, CVE-2024-38618, CVE-2024-40981, CVE-2024-42127, CVE-2024-38607, CVE-2024-38586,     CVE-2024-40901, CVE-2024-40916, CVE-2024-42247, CVE-2024-42093, CVE-2024-36489, CVE-2024-38615,     CVE-2024-42120, CVE-2024-38567, CVE-2024-40957, CVE-2024-39501, CVE-2024-42140, CVE-2024-33621,     CVE-2024-38573, CVE-2023-52884, CVE-2024-39468, CVE-2024-41092, CVE-2024-40931, CVE-2024-42145,     CVE-2024-39490, CVE-2024-38555, CVE-2024-42086, CVE-2024-38597, CVE-2024-40956, CVE-2024-42223,     CVE-2024-36894, CVE-2024-40961, CVE-2024-42076, CVE-2024-40994, CVE-2024-38619, CVE-2024-39467,     CVE-2024-39466, CVE-2022-48772, CVE-2024-39507, CVE-2024-40914, CVE-2024-41046, CVE-2024-42094,     CVE-2024-38591, CVE-2024-42098, CVE-2024-41027, CVE-2024-41040, CVE-2024-41089, CVE-2024-40945,     CVE-2024-39503, CVE-2024-37356, CVE-2024-36286, CVE-2024-39495, CVE-2024-42101, CVE-2024-40941,     CVE-2024-42137, CVE-2024-38381, CVE-2024-38627, CVE-2024-31076, CVE-2024-42092, CVE-2024-40932,     CVE-2024-40995, CVE-2024-40937, CVE-2024-39489, CVE-2024-42084, CVE-2024-40929, CVE-2024-36978,     CVE-2024-36015, CVE-2024-36014, CVE-2024-42124, CVE-2024-40976, CVE-2024-39502, CVE-2024-38599,     CVE-2024-38661, CVE-2024-42104, CVE-2024-42096, CVE-2024-40904, CVE-2024-40990, CVE-2024-38579,     CVE-2024-40974, CVE-2024-41055, CVE-2024-38633, CVE-2024-38659, CVE-2024-41093, CVE-2024-42154,     CVE-2024-38624, CVE-2024-41049, CVE-2024-38552, CVE-2024-38578, CVE-2024-38605, CVE-2024-40970,     CVE-2024-38601, CVE-2024-38550, CVE-2024-38559, CVE-2024-38571, CVE-2024-40971, CVE-2024-41097,     CVE-2024-40967, CVE-2024-38612, CVE-2024-38587, CVE-2024-41004, CVE-2024-33847, CVE-2024-38580,     CVE-2024-39506, CVE-2024-42102, CVE-2024-36032, CVE-2024-38548, CVE-2024-39499, CVE-2024-38610,     CVE-2024-42152, CVE-2024-40943, CVE-2024-40959, CVE-2024-39488, CVE-2024-36972, CVE-2024-38637,     CVE-2024-40942, CVE-2024-42106, CVE-2024-38546, CVE-2024-38634, CVE-2024-39471, CVE-2024-39482,     CVE-2024-41095, CVE-2024-42229, CVE-2024-42131, CVE-2024-41007, CVE-2024-42095, CVE-2024-42097,     CVE-2024-39480, CVE-2024-35927, CVE-2024-42153, CVE-2024-42080, CVE-2024-42089, CVE-2024-41087,     CVE-2024-39475, CVE-2024-42119, CVE-2024-41041, CVE-2024-38623, CVE-2024-39469, CVE-2024-34777,     CVE-2024-42157, CVE-2024-42085, CVE-2024-36270, CVE-2024-34027, CVE-2024-35247, CVE-2024-38549,     CVE-2024-40954, CVE-2024-41034, CVE-2024-41044, CVE-2024-39509, CVE-2024-40987, CVE-2024-42161,     CVE-2024-40911, CVE-2024-42070, CVE-2024-42109, CVE-2024-37078, CVE-2024-40912, CVE-2024-40988,     CVE-2024-40978, CVE-2024-41048, CVE-2024-41005, CVE-2024-40905, CVE-2024-41047, CVE-2024-41006,     CVE-2024-38560, CVE-2024-42225, CVE-2024-42148, CVE-2024-38596, CVE-2024-38588, CVE-2024-39301,     CVE-2024-38613, CVE-2024-38635, CVE-2024-40960, CVE-2024-39505, CVE-2024-42244, CVE-2024-40963,     CVE-2024-39500, CVE-2024-42082, CVE-2024-36971, CVE-2024-42068, CVE-2024-40984, CVE-2024-41035,     CVE-2024-38583, CVE-2024-42121, CVE-2024-40968, CVE-2024-40958, CVE-2024-40927, CVE-2024-40980,     CVE-2024-40908, CVE-2024-38780, CVE-2024-38590, CVE-2024-42115, CVE-2024-42224, CVE-2024-42232,     CVE-2024-42240, CVE-2024-42236, CVE-2024-38547, CVE-2024-38565, CVE-2024-40902, CVE-2024-38662,     CVE-2024-42090, CVE-2024-36974, CVE-2024-38621, CVE-2024-41000, CVE-2024-40983, CVE-2024-42130,     CVE-2024-38582, CVE-2024-38589)

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

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

ID	Name	Product	Family	Published	Updated	Severity
211824	Ubuntu 16.04 LTS : Linux kernel (Oracle) vulnerabilities (USN-7121-3)	Nessus	Ubuntu Local Security Checks	11/25/2024	9/24/2025	high
212266	Ubuntu 14.04 LTS / 16.04 LTS : Linux kernel vulnerabilities (USN-7148-1)	Nessus	Ubuntu Local Security Checks	12/10/2024	9/24/2025	high
207802	Ubuntu 20.04 LTS : Linux kernel vulnerabilities (USN-7003-4)	Nessus	Ubuntu Local Security Checks	9/26/2024	9/24/2025	high
238008	NewStart CGSL MAIN 7.02 : kernel Multiple Vulnerabilities (NS-SA-2025-0084)	Nessus	NewStart CGSL Local Security Checks	6/9/2025	6/18/2025	high
207597	Ubuntu 20.04 LTS / 22.04 LTS : Linux kernel vulnerabilities (USN-7007-3)	Nessus	Ubuntu Local Security Checks	9/23/2024	2/3/2026	high

Detections

Analytics

Plugins Search

high

high

high

high

high