The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2025:0437 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2024-46732:
    In the Linux kernel, the following vulnerability has been resolved:

    drm/amd/display: Assign linear_pitch_alignment even for VM

    [Description]     Assign linear_pitch_alignment so we don't cause a divide by 0     error in VM environments

    CVE-2024-46730:
    In the Linux kernel, the following vulnerability has been resolved:

    drm/amd/display: Ensure array index tg_inst won't be -1

    [WHY & HOW]     tg_inst will be a negative if timing_generator_count equals 0, which     should be checked before used.

    This fixes 2 OVERRUN issues reported by Coverity.

    CVE-2024-24861:
    A race condition was found in the Linux kernel's media/xc4000 device driver in xc4000     xc4000_get_frequency() function. This can result in return value overflow issue, possibly leading to     malfunction or denial of service issue.






    CVE-2024-38559:
    In the Linux kernel, the following vulnerability has been resolved:

    scsi: qedf: Ensure the copied buf is NUL terminated

    Currently, we allocate a count-sized kernel buffer and copy count from     userspace to that buffer. Later, we use kstrtouint on this buffer but we     don't ensure that the string is terminated inside the buffer, this can     lead to OOB read when using kstrtouint. Fix this issue by using     memdup_user_nul instead of memdup_user.

    CVE-2024-26937:
    In the Linux kernel, the following vulnerability has been resolved:

    drm/i915/gt: Reset queue_priority_hint on parking

    Originally, with strict in order execution, we could complete execution     only when the queue was empty. Preempt-to-busy allows replacement of an     active request that may complete before the preemption is processed by     HW. If that happens, the request is retired from the queue, but the     queue_priority_hint remains set, preventing direct submission until     after the next CS interrupt is processed.

    This preempt-to-busy race can be triggered by the heartbeat, which will     also act as the power-management barrier and upon completion allow us to     idle the HW. We may process the completion of the heartbeat, and begin     parking the engine before the CS event that restores the     queue_priority_hint, causing us to fail the assertion that it is MIN.

    <3>[  166.210729] __engine_park:283 GEM_BUG_ON(engine->sched_engine->queue_priority_hint != (-((int)(~0U     >> 1)) - 1))     <0>[  166.210781] Dumping ftrace buffer:
    <0>[  166.210795] ---------------------------------     ...
    <0>[  167.302811] drm_fdin-1097      2..s1. 165741070us : trace_ports: 0000:00:02.0 rcs0: promote {     ccid:20 1217:2 prio 0 }     <0>[  167.302861] drm_fdin-1097      2d.s2. 165741072us : execlists_submission_tasklet: 0000:00:02.0 rcs0:
    preempting last=1217:2, prio=0, hint=2147483646     <0>[  167.302928] drm_fdin-1097      2d.s2. 165741072us : __i915_request_unsubmit: 0000:00:02.0 rcs0:
    fence 1217:2, current 0     <0>[  167.302992] drm_fdin-1097      2d.s2. 165741073us : __i915_request_submit: 0000:00:02.0 rcs0: fence     3:4660, current 4659     <0>[  167.303044] drm_fdin-1097      2d.s1. 165741076us : execlists_submission_tasklet: 0000:00:02.0 rcs0:
    context:3 schedule-in, ccid:40     <0>[  167.303095] drm_fdin-1097      2d.s1. 165741077us : trace_ports: 0000:00:02.0 rcs0: submit { ccid:40     3:4660* prio 2147483646 }     <0>[  167.303159] kworker/-89       11..... 165741139us : i915_request_retire.part.0: 0000:00:02.0 rcs0:
    fence c90:2, current 2     <0>[  167.303208] kworker/-89       11..... 165741148us : __intel_context_do_unpin: 0000:00:02.0 rcs0:
    context:c90 unpin     <0>[  167.303272] kworker/-89       11..... 165741159us : i915_request_retire.part.0: 0000:00:02.0 rcs0:
    fence 1217:2, current 2     <0>[  167.303321] kworker/-89       11..... 165741166us : __intel_context_do_unpin: 0000:00:02.0 rcs0:
    context:1217 unpin     <0>[  167.303384] kworker/-89       11..... 165741170us : i915_request_retire.part.0: 0000:00:02.0 rcs0:
    fence 3:4660, current 4660     <0>[  167.303434] kworker/-89       11d..1. 165741172us : __intel_context_retire: 0000:00:02.0 rcs0:
    context:1216 retire runtime: { total:56028ns, avg:56028ns }     <0>[  167.303484] kworker/-89       11..... 165741198us : __engine_park: 0000:00:02.0 rcs0: parked     <0>[  167.303534]   <idle>-0         5d.H3. 165741207us : execlists_irq_handler: 0000:00:02.0 rcs0:
    semaphore yield: 00000040     <0>[  167.303583] kworker/-89       11..... 165741397us : __intel_context_retire: 0000:00:02.0 rcs0:
    context:1217 retire runtime: { total:325575ns, avg:0ns }     <0>[  167.303756] kworker/-89       11..... 165741777us : __intel_context_retire: 0000:00:02.0 rcs0:
    context:c90 retire runtime: { total:0ns, avg:0ns }     <0>[  167.303806] kworker/-89       11..... 165742017us : __engine_park: __engine_park:283     GEM_BUG_ON(engine->sched_engine->queue_priority_hint != (-((int)(~0U >> 1)) - 1))     <0>[  167.303811] ---------------------------------     <4>[  167.304722] ------------[ cut here ]------------     <2>[  167.304725] kernel BUG at drivers/gpu/drm/i915/gt/intel_engine_pm.c:283!     <4>[  167.304731] invalid opcode: 0000 [#1] PREEMPT SMP NOPTI     <4>[  167.304734] CPU: 11 PID: 89 Comm: kworker/11:1 Tainted: G        W     6.8.0-rc2-CI_DRM_14193-gc655e0fd2804+ #1     <4>[  167.304736] Hardware name: Intel Corporation Rocket Lake Client Platform/RocketLake S UDIMM 6L RVP,     BIOS RKLSFWI1.R00.3173.A03.2204210138 04/21/2022     <4>[  167.304738] Workqueue: i915-unordered retire_work_handler [i915]     <4>[  16
    ---truncated---

    CVE-2024-26935:
    In the Linux kernel, the following vulnerability has been resolved:

    scsi: core: Fix unremoved procfs host directory regression

    Commit fc663711b944 (scsi: core: Remove the /proc/scsi/${proc_name}     directory earlier) fixed a bug related to modules loading/unloading, by     adding a call to scsi_proc_hostdir_rm() on scsi_remove_host(). But that led     to a potential duplicate call to the hostdir_rm() routine, since it's also     called from scsi_host_dev_release(). That triggered a regression report,     which was then fixed by commit be03df3d4bfe (scsi: core: Fix a procfs host     directory removal regression). The fix just dropped the hostdir_rm() call     from dev_release().

    But it happens that this proc directory is created on scsi_host_alloc(),     and that function pairs with scsi_host_dev_release(), while     scsi_remove_host() pairs with scsi_add_host(). In other words, it seems the     reason for removing the proc directory on dev_release() was meant to cover     cases in which a SCSI host structure was allocated, but the call to     scsi_add_host() didn't happen. And that pattern happens to exist in some     error paths, for example.

    Syzkaller causes that by using USB raw gadget device, error'ing on     usb-storage driver, at usb_stor_probe2(). By checking that path, we can see     that the BadDevice label leads to a scsi_host_put() after a SCSI host     allocation, but there's no call to scsi_add_host() in such path. That leads     to messages like this in dmesg (and a leak of the SCSI host proc     structure):

    usb-storage 4-1:87.51: USB Mass Storage device detected     proc_dir_entry 'scsi/usb-storage' already registered     WARNING: CPU: 1 PID: 3519 at fs/proc/generic.c:377 proc_register+0x347/0x4e0 fs/proc/generic.c:376

    The proper fix seems to still call scsi_proc_hostdir_rm() on dev_release(),     but guard that with the state check for SHOST_CREATED; there is even a     comment in scsi_host_dev_release() detailing that: such conditional is     meant for cases where the SCSI host was allocated but there was no calls to     {add,remove}_host(), like the usb-storage case.

    This is what we propose here and with that, the error path of usb-storage     does not trigger the warning anymore.

    CVE-2024-26934:
    In the Linux kernel, the following vulnerability has been resolved:

    USB: core: Fix deadlock in usb_deauthorize_interface()

    Among the attribute file callback routines in     drivers/usb/core/sysfs.c, the interface_authorized_store() function is     the only one which acquires a device lock on an ancestor device: It     calls usb_deauthorize_interface(), which locks the interface's parent     USB device.

    The will lead to deadlock if another process already owns that lock     and tries to remove the interface, whether through a configuration     change or because the device has been disconnected.  As part of the     removal procedure, device_del() waits for all ongoing sysfs attribute     callbacks to complete.  But usb_deauthorize_interface() can't complete     until the device lock has been released, and the lock won't be     released until the removal has finished.

    The mechanism provided by sysfs to prevent this kind of deadlock is     to use the sysfs_break_active_protection() function, which tells sysfs     not to wait for the attribute callback.

    Reported-and-tested by: Yue Sun <samsun1006219@gmail.com>     Reported by: xingwei lee <xrivendell7@gmail.com>

    CVE-2024-26931:
    In the Linux kernel, the following vulnerability has been resolved:

    scsi: qla2xxx: Fix command flush on cable pull

    System crash due to command failed to flush back to SCSI layer.

     BUG: unable to handle kernel NULL pointer dereference at 0000000000000000      PGD 0 P4D 0      Oops: 0000 [#1] SMP NOPTI      CPU: 27 PID: 793455 Comm: kworker/u130:6 Kdump: loaded Tainted: G           OE    --------- -  -     4.18.0-372.9.1.el8.x86_64 #1      Hardware name: HPE ProLiant DL360 Gen10/ProLiant DL360 Gen10, BIOS U32 09/03/2021      Workqueue: nvme-wq nvme_fc_connect_ctrl_work [nvme_fc]      RIP: 0010:__wake_up_common+0x4c/0x190      Code: 24 10 4d 85 c9 74 0a 41 f6 01 04 0f 85 9d 00 00 00 48 8b 43 08 48 83 c3 08 4c 8d 48 e8 49 8d 41 18     48 39 c3 0f 84 f0 00 00 00 <49> 8b 41 18 89 54 24 08 31 ed 4c 8d 70 e8 45 8b 29 41 f6 c5 04 75      RSP: 0018:ffff95f3e0cb7cd0 EFLAGS: 00010086      RAX: 0000000000000000 RBX: ffff8b08d3b26328 RCX: 0000000000000000      RDX: 0000000000000001 RSI: 0000000000000003 RDI: ffff8b08d3b26320      RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffffffffffe8      R10: 0000000000000000 R11: ffff95f3e0cb7a60 R12: ffff95f3e0cb7d20      R13: 0000000000000003 R14: 0000000000000000 R15: 0000000000000000      FS:  0000000000000000(0000) GS:ffff8b2fdf6c0000(0000) knlGS:0000000000000000      CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033      CR2: 0000000000000000 CR3: 0000002f1e410002 CR4: 00000000007706e0      DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000      DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400      PKRU: 55555554      Call Trace:
    __wake_up_common_lock+0x7c/0xc0     qla_nvme_ls_req+0x355/0x4c0 [qla2xxx]      qla2xxx [0000:12:00.1]-f084:3: qlt_free_session_done: se_sess 0000000000000000 / sess ffff8ae1407ca000     from port 21:32:00:02:ac:07:ee:b8 loop_id 0x02 s_id 01:02:00 logout 1 keep 0 els_logo 0      ? __nvme_fc_send_ls_req+0x260/0x380 [nvme_fc]      qla2xxx [0000:12:00.1]-207d:3: FCPort 21:32:00:02:ac:07:ee:b8 state transitioned from ONLINE to LOST -     portid=010200.
    ? nvme_fc_send_ls_req.constprop.42+0x1a/0x45 [nvme_fc]      qla2xxx [0000:12:00.1]-2109:3: qla2x00_schedule_rport_del 21320002ac07eeb8. rport ffff8ae598122000 roles     1      ? nvme_fc_connect_ctrl_work.cold.63+0x1e3/0xa7d [nvme_fc]      qla2xxx [0000:12:00.1]-f084:3: qlt_free_session_done: se_sess 0000000000000000 / sess ffff8ae14801e000     from port 21:32:01:02:ad:f7:ee:b8 loop_id 0x04 s_id 01:02:01 logout 1 keep 0 els_logo 0     ? __switch_to+0x10c/0x450      ? process_one_work+0x1a7/0x360      qla2xxx [0000:12:00.1]-207d:3: FCPort 21:32:01:02:ad:f7:ee:b8 state transitioned from ONLINE to LOST -     portid=010201.
    ? worker_thread+0x1ce/0x390     ? create_worker+0x1a0/0x1a0      qla2xxx [0000:12:00.1]-2109:3: qla2x00_schedule_rport_del 21320102adf7eeb8. rport ffff8ae3b2312800 roles     70     ? kthread+0x10a/0x120      qla2xxx [0000:12:00.1]-2112:3: qla_nvme_unregister_remote_port: unregister remoteport on ffff8ae14801e000     21320102adf7eeb8     ? set_kthread_struct+0x40/0x40      qla2xxx [0000:12:00.1]-2110:3: remoteport_delete of ffff8ae14801e000 21320102adf7eeb8 completed.
    ? ret_from_fork+0x1f/0x40      qla2xxx [0000:12:00.1]-f086:3: qlt_free_session_done: waiting for sess ffff8ae14801e000 logout

    The system was under memory stress where driver was not able to allocate an     SRB to carry out error recovery of cable pull.  The failure to flush causes     upper layer to start modifying scsi_cmnd.  When the system frees up some     memory, the subsequent cable pull trigger another command flush. At this     point the driver access a null pointer when attempting to DMA unmap the     SGL.

    Add a check to make sure commands are flush back on session tear down to     prevent the null pointer access.

    CVE-2023-52853:
    In the Linux kernel, the following vulnerability has been resolved:

    hid: cp2112: Fix duplicate workqueue initialization

    Previously the cp2112 driver called INIT_DELAYED_WORK within     cp2112_gpio_irq_startup, resulting in duplicate initilizations of the     workqueue on subsequent IRQ startups following an initial request. This     resulted in a warning in set_work_data in workqueue.c, as well as a rare     NULL dereference within process_one_work in workqueue.c.

    Initialize the workqueue within _probe instead.

    CVE-2022-49013:
    In the Linux kernel, the following vulnerability has been resolved:

    sctp: fix memory leak in sctp_stream_outq_migrate()

    When sctp_stream_outq_migrate() is called to release stream out resources,     the memory pointed to by prio_head in stream out is not released.

    The memory leak information is as follows:
     unreferenced object 0xffff88801fe79f80 (size 64):
     comm sctp_repo, pid 7957, jiffies 4294951704 (age 36.480s)      hex dump (first 32 bytes):
       80 9f e7 1f 80 88 ff ff 80 9f e7 1f 80 88 ff ff  ................
       90 9f e7 1f 80 88 ff ff 90 9f e7 1f 80 88 ff ff  ................
     backtrace:
       [<ffffffff81b215c6>] kmalloc_trace+0x26/0x60        [<ffffffff88ae517c>] sctp_sched_prio_set+0x4cc/0x770        [<ffffffff88ad64f2>] sctp_stream_init_ext+0xd2/0x1b0        [<ffffffff88aa2604>] sctp_sendmsg_to_asoc+0x1614/0x1a30        [<ffffffff88ab7ff1>] sctp_sendmsg+0xda1/0x1ef0        [<ffffffff87f765ed>] inet_sendmsg+0x9d/0xe0        [<ffffffff8754b5b3>] sock_sendmsg+0xd3/0x120        [<ffffffff8755446a>] __sys_sendto+0x23a/0x340        [<ffffffff87554651>] __x64_sys_sendto+0xe1/0x1b0        [<ffffffff89978b49>] do_syscall_64+0x39/0xb0        [<ffffffff89a0008b>] entry_SYSCALL_64_after_hwframe+0x63/0xcd

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

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

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

    Ziming Zhang discovered that the DRM driver for VMware Virtual GPU did not properly handle certain error     conditions, leading to a NULL pointer dereference. A local attacker could possibly trigger this     vulnerability to cause a denial of service. (CVE-2022-38096)

    Zheng Wang discovered that the Broadcom FullMAC WLAN driver in the Linux kernel contained a race condition     during device removal, leading to a use- after-free vulnerability. A physically proximate attacker could     possibly use this to cause a denial of service (system crash). (CVE-2023-47233)

    It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition,     leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or     possibly execute arbitrary code. (CVE-2023-6270)

    It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data     structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial     of service. (CVE-2023-7042)

    It was discovered that the Intel Data Streaming and Intel Analytics Accelerator drivers in the Linux     kernel allowed direct access to the devices for unprivileged users and virtual machines. A local attacker     could use this to cause a denial of service. (CVE-2024-21823)

    Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition,     leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a     denial of service (system crash). (CVE-2024-23307)

    Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a     race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause     a denial of service (system crash). (CVE-2024-24861)

    Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did     not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this     to cause a denial of service (system crash). (CVE-2024-25739)

    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:

    - ARM32 architecture;

    - PowerPC architecture;

    - x86 architecture;

    - Block layer subsystem;

    - ACPI drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - CPU frequency scaling framework;

    - Cryptographic API;

    - DPLL subsystem;

    - ARM SCMI message protocol;

    - EFI core;

    - GPU drivers;

    - InfiniBand drivers;

    - IOMMU subsystem;

    - LED subsystem;

    - Multiple devices driver;

    - Media drivers;

    - MMC subsystem;

    - Network drivers;

    - NTB driver;

    - NVME drivers;

    - PCI subsystem;

    - Powercap sysfs driver;

    - SCSI drivers;

    - Freescale SoC drivers;

    - SPI subsystem;

    - Media staging drivers;

    - Thermal drivers;

    - TTY drivers;

    - USB subsystem;

    - DesignWare USB3 driver;

    - VFIO drivers;

    - Backlight driver;

    - Virtio drivers;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - debug file system;

    - Ext4 file system;

    - F2FS file system;

    - FAT file system;

    - Network file system client;

    - NILFS2 file system;

    - Overlay file system;

    - Pstore file system;

    - Diskquota system;

    - SMB network file system;

    - UBI file system;

    - io_uring subsystem;

    - BPF subsystem;

    - Core kernel;

    - PCI iomap interfaces;

    - Memory management;

    - Bluetooth subsystem;

    - Networking core;

    - HSR network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - IEEE 802.15.4 subsystem;

    - Netfilter;

    - Packet sockets;

    - Network traffic control;

    - Sun RPC protocol;

    - ALSA SH drivers;

    - SOF drivers;

    - USB sound devices;

    - KVM core; (CVE-2024-27032, CVE-2024-26868, CVE-2024-26879, CVE-2024-27033, CVE-2024-26943,     CVE-2024-27040, CVE-2024-26950, CVE-2023-52650, CVE-2023-52649, CVE-2023-52644, CVE-2024-26899,     CVE-2024-27432, CVE-2024-35806, CVE-2024-26871, CVE-2024-35845, CVE-2024-35799, CVE-2024-26945,     CVE-2024-35805, CVE-2024-27041, CVE-2024-26860, CVE-2024-26930, CVE-2024-26941, CVE-2024-26960,     CVE-2024-27034, CVE-2024-26891, CVE-2024-35793, CVE-2024-26963, CVE-2024-27029, CVE-2024-26890,     CVE-2024-27074, CVE-2024-27079, CVE-2024-27053, CVE-2024-27070, CVE-2024-35821, CVE-2024-27067,     CVE-2024-27051, CVE-2024-27026, CVE-2024-26961, CVE-2024-27050, CVE-2024-26939, CVE-2024-26897,     CVE-2024-26878, CVE-2024-27433, CVE-2024-26885, CVE-2024-35810, CVE-2024-35829, CVE-2024-26965,     CVE-2024-26875, CVE-2024-26966, CVE-2024-27078, CVE-2024-35874, CVE-2023-52661, CVE-2024-35794,     CVE-2024-35787, CVE-2024-26874, CVE-2024-27054, CVE-2024-26940, CVE-2024-26859, CVE-2024-27044,     CVE-2024-26948, CVE-2024-26882, CVE-2023-52653, CVE-2024-27071, CVE-2024-27065, CVE-2024-26877,     CVE-2024-26929, CVE-2024-27064, CVE-2024-35803, CVE-2024-27066, CVE-2024-27028, CVE-2024-27072,     CVE-2024-26876, CVE-2024-27039, CVE-2024-27435, CVE-2024-27434, CVE-2024-26812, CVE-2024-27030,     CVE-2024-26816, CVE-2024-26873, CVE-2024-35808, CVE-2024-27389, CVE-2024-27075, CVE-2024-27038,     CVE-2024-35828, CVE-2024-26946, CVE-2024-26655, CVE-2023-52662, CVE-2024-27077, CVE-2024-27076,     CVE-2024-35795, CVE-2024-26933, CVE-2024-35789, CVE-2024-26972, CVE-2023-52663, CVE-2024-27031,     CVE-2024-27069, CVE-2024-26813, CVE-2023-52659, CVE-2024-26862, CVE-2024-26962, CVE-2024-26654,     CVE-2024-26815, CVE-2024-26978, CVE-2024-26976, CVE-2024-26893, CVE-2024-35809, CVE-2024-27027,     CVE-2024-26864, CVE-2024-27048, CVE-2024-27046, CVE-2024-26869, CVE-2024-35827, CVE-2024-26951,     CVE-2024-26942, CVE-2024-26870, CVE-2024-27437, CVE-2024-26931, CVE-2024-27036, CVE-2022-48669,     CVE-2024-26898, CVE-2024-26970, CVE-2024-26886, CVE-2024-26944, CVE-2024-26865, CVE-2024-26896,     CVE-2024-26895, CVE-2024-26947, CVE-2024-26880, CVE-2024-35811, CVE-2024-26975, CVE-2024-27391,     CVE-2024-35796, CVE-2024-27043, CVE-2024-26949, CVE-2024-26653, CVE-2024-35814, CVE-2024-26964,     CVE-2023-52652, CVE-2024-27047, CVE-2024-35830, CVE-2024-26900, CVE-2024-26810, CVE-2024-26956,     CVE-2024-35817, CVE-2024-26887, CVE-2024-26809, CVE-2024-27045, CVE-2024-26656, CVE-2024-26971,     CVE-2024-26866, CVE-2024-26861, CVE-2024-26968, CVE-2024-26881, CVE-2024-27063, CVE-2024-35807,     CVE-2024-35797, CVE-2024-35822, CVE-2024-35813, CVE-2024-27073, CVE-2024-26954, CVE-2024-26888,     CVE-2024-26955, CVE-2024-26894, CVE-2024-35844, CVE-2024-26958, CVE-2024-26952, CVE-2024-35798,     CVE-2024-26969, CVE-2024-26967, CVE-2024-35800, CVE-2024-35819, CVE-2024-26937, CVE-2024-26927,     CVE-2024-26883, CVE-2024-26934, CVE-2024-27392, CVE-2024-27068, CVE-2024-26889, CVE-2024-26892,     CVE-2024-27390, CVE-2024-26657, CVE-2024-27388, CVE-2024-27049, CVE-2024-26935, CVE-2024-35831,     CVE-2024-26884, CVE-2024-26938, CVE-2024-27037, CVE-2024-26977, CVE-2024-26953, CVE-2024-26973,     CVE-2024-26932, CVE-2024-26901, CVE-2024-35843, CVE-2024-26872, CVE-2024-26959, CVE-2024-27035,     CVE-2024-35826, CVE-2024-27436, CVE-2024-26651, CVE-2024-26957, CVE-2024-26863, CVE-2024-27042,     CVE-2024-26814, CVE-2023-52647, CVE-2024-27080, CVE-2024-27052, CVE-2024-27058, CVE-2024-35801,     CVE-2023-52648)

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

    It was discovered that the ATA over Ethernet (AoE) driver in the Linux kernel contained a race condition,     leading to a use-after-free vulnerability. An attacker could use this to cause a denial of service or     possibly execute arbitrary code. (CVE-2023-6270)

    It was discovered that the Atheros 802.11ac wireless driver did not properly validate certain data     structures, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial     of service. (CVE-2023-7042)

    Yuxuan Hu discovered that the Bluetooth RFCOMM protocol driver in the Linux Kernel contained a race     condition, leading to a NULL pointer dereference. An attacker could possibly use this to cause a denial of     service (system crash). (CVE-2024-22099)

    Gui-Dong Han discovered that the software RAID driver in the Linux kernel contained a race condition,     leading to an integer overflow vulnerability. A privileged attacker could possibly use this to cause a     denial of service (system crash). (CVE-2024-23307)

    It was discovered that a race condition existed in the Bluetooth subsystem in the Linux kernel when     modifying certain settings values through debugfs. A privileged local attacker could use this to cause a     denial of service. (CVE-2024-24857, CVE-2024-24858, CVE-2024-24859)

    Bai Jiaju discovered that the Xceive XC4000 silicon tuner device driver in the Linux kernel contained a     race condition, leading to an integer overflow vulnerability. An attacker could possibly use this to cause     a denial of service (system crash). (CVE-2024-24861)

    Chenyuan Yang discovered that the Unsorted Block Images (UBI) flash device volume management subsystem did     not properly validate logical eraseblock sizes in certain situations. An attacker could possibly use this     to cause a denial of service (system crash). (CVE-2024-25739)

    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;

    - Block layer subsystem;

    - Accessibility subsystem;

    - ACPI drivers;

    - Android drivers;

    - Bluetooth drivers;

    - Clock framework and drivers;

    - Data acquisition framework and drivers;

    - Cryptographic API;

    - GPU drivers;

    - HID subsystem;

    - I2C subsystem;

    - IRQ chip drivers;

    - Multiple devices driver;

    - Media drivers;

    - VMware VMCI Driver;

    - MMC subsystem;

    - Network drivers;

    - PCI subsystem;

    - SCSI drivers;

    - Freescale SoC drivers;

    - SPI subsystem;

    - Media staging drivers;

    - TTY drivers;

    - USB subsystem;

    - VFIO drivers;

    - Framebuffer layer;

    - Xen hypervisor drivers;

    - File systems infrastructure;

    - BTRFS file system;

    - Ext4 file system;

    - FAT file system;

    - NILFS2 file system;

    - Diskquota system;

    - SMB network file system;

    - UBI file system;

    - io_uring subsystem;

    - BPF subsystem;

    - Core kernel;

    - Memory management;

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

    - Bluetooth subsystem;

    - Networking core;

    - HSR network protocol;

    - IPv4 networking;

    - IPv6 networking;

    - MAC80211 subsystem;

    - Netfilter;

    - NET/ROM layer;

    - NFC subsystem;

    - Open vSwitch;

    - Packet sockets;

    - RDS protocol;

    - Network traffic control;

    - Sun RPC protocol;

    - Unix domain sockets;

    - ALSA SH drivers;

    - USB sound devices;

    - KVM core; (CVE-2024-35969, CVE-2024-35819, CVE-2024-26851, CVE-2024-26816, CVE-2024-26643,     CVE-2023-52656, CVE-2024-27020, CVE-2024-35821, CVE-2024-35930, CVE-2024-35936, CVE-2024-27075,     CVE-2024-26817, CVE-2024-26984, CVE-2024-35895, CVE-2024-35853, CVE-2024-27043, CVE-2024-35978,     CVE-2024-35960, CVE-2024-26882, CVE-2024-35806, CVE-2024-35830, CVE-2024-26852, CVE-2024-35915,     CVE-2024-36006, CVE-2024-35935, CVE-2024-26926, CVE-2024-35877, CVE-2024-27396, CVE-2024-26654,     CVE-2024-27077, CVE-2024-27078, CVE-2024-27000, CVE-2024-35888, CVE-2024-27437, CVE-2024-26994,     CVE-2024-26973, CVE-2024-26687, CVE-2024-26955, CVE-2024-26898, CVE-2024-26859, CVE-2023-52620,     CVE-2024-35893, CVE-2024-26903, CVE-2024-26862, CVE-2024-35950, CVE-2023-52644, CVE-2024-26969,     CVE-2024-27028, CVE-2024-35984, CVE-2024-36007, CVE-2024-35925, CVE-2024-36020, CVE-2024-26956,     CVE-2024-35789, CVE-2024-26878, CVE-2024-35855, CVE-2024-35822, CVE-2023-52699, CVE-2024-27044,     CVE-2024-27030, CVE-2024-27065, CVE-2024-26993, CVE-2024-27395, CVE-2024-27013, CVE-2024-35922,     CVE-2024-26586, CVE-2024-36004, CVE-2024-35897, CVE-2024-35807, CVE-2024-26901, CVE-2024-27076,     CVE-2023-52880, CVE-2022-48627, CVE-2024-26894, CVE-2023-52650, CVE-2024-27001, CVE-2024-26863,     CVE-2024-26651, CVE-2024-35886, CVE-2024-35982, CVE-2024-26883, CVE-2024-26935, CVE-2024-27074,     CVE-2024-35849, CVE-2024-35955, CVE-2024-26965, CVE-2024-35898, CVE-2024-26855, CVE-2024-35933,     CVE-2024-35823, CVE-2024-35815, CVE-2024-26880, CVE-2024-26874, CVE-2024-26642, CVE-2024-26937,     CVE-2024-35854, CVE-2024-35997, CVE-2024-27059, CVE-2024-26812, CVE-2024-26999, CVE-2024-26923,     CVE-2024-26934, CVE-2024-27024, CVE-2024-27419, CVE-2024-35847, CVE-2024-26974, CVE-2024-26875,     CVE-2024-35805, CVE-2024-27008, CVE-2024-26889, CVE-2024-27053, CVE-2024-27388, CVE-2024-26981,     CVE-2024-26976, CVE-2024-35973, CVE-2024-35852, CVE-2024-35809, CVE-2024-27004, CVE-2024-26884,     CVE-2024-35899, CVE-2024-26931, CVE-2024-35813, CVE-2024-26922, CVE-2024-26957, CVE-2024-35944,     CVE-2024-27038, CVE-2024-35910, CVE-2024-26925, CVE-2024-26820, CVE-2024-26857, CVE-2024-26828,     CVE-2024-35825, CVE-2024-26813, CVE-2024-27046, CVE-2024-26810, CVE-2024-27436, CVE-2024-27073,     CVE-2024-35828, CVE-2024-35900, CVE-2024-26966)

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 RockyLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2025:1067 advisory.

    * kernel: scsi: core: Fix unremoved procfs host directory regression (CVE-2024-26935)

    * kernel: arm64/sve: Discard stale CPU state when handling SVE traps (CVE-2024-50275)

Tenable has extracted the preceding description block directly from the RockyLinux 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 Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-5681 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-5681-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     May 06, 2024                          https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2023-6270 CVE-2023-7042 CVE-2023-28746 CVE-2023-47233                      CVE-2023-52429 CVE-2023-52434 CVE-2023-52435 CVE-2023-52447                      CVE-2023-52458 CVE-2023-52482 CVE-2023-52486 CVE-2023-52488                      CVE-2023-52489 CVE-2023-52491 CVE-2023-52492 CVE-2023-52493                      CVE-2023-52497 CVE-2023-52498 CVE-2023-52583 CVE-2023-52587                      CVE-2023-52594 CVE-2023-52595 CVE-2023-52597 CVE-2023-52598                      CVE-2023-52599 CVE-2023-52600 CVE-2023-52601 CVE-2023-52602                      CVE-2023-52603 CVE-2023-52604 CVE-2023-52606 CVE-2023-52607                      CVE-2023-52614 CVE-2023-52615 CVE-2023-52616 CVE-2023-52617                      CVE-2023-52618 CVE-2023-52619 CVE-2023-52620 CVE-2023-52622                      CVE-2023-52623 CVE-2023-52627 CVE-2023-52635 CVE-2023-52637                      CVE-2023-52642 CVE-2023-52644 CVE-2023-52650 CVE-2024-0340                      CVE-2024-0565 CVE-2024-0607 CVE-2024-0841 CVE-2024-1151                      CVE-2024-22099 CVE-2024-23849 CVE-2024-23850 CVE-2024-23851                      CVE-2024-24857 CVE-2024-24858 CVE-2024-24861 CVE-2024-26581                      CVE-2024-26593 CVE-2024-26600 CVE-2024-26601 CVE-2024-26602                      CVE-2024-26606 CVE-2024-26610 CVE-2024-26614 CVE-2024-26615                      CVE-2024-26622 CVE-2024-26625 CVE-2024-26627 CVE-2024-26635                      CVE-2024-26636 CVE-2024-26640 CVE-2024-26641 CVE-2024-26642                      CVE-2024-26643 CVE-2024-26644 CVE-2024-26645 CVE-2024-26651                      CVE-2024-26654 CVE-2024-26659 CVE-2024-26663 CVE-2024-26664                      CVE-2024-26665 CVE-2024-26671 CVE-2024-26673 CVE-2024-26675                      CVE-2024-26679 CVE-2024-26684 CVE-2024-26685 CVE-2024-26687                      CVE-2024-26688 CVE-2024-26689 CVE-2024-26695 CVE-2024-26696                      CVE-2024-26697 CVE-2024-26698 CVE-2024-26702 CVE-2024-26704                      CVE-2024-26707 CVE-2024-26712 CVE-2024-26720 CVE-2024-26722                      CVE-2024-26727 CVE-2024-26733 CVE-2024-26735 CVE-2024-26736                      CVE-2024-26743 CVE-2024-26744 CVE-2024-26747 CVE-2024-26748                      CVE-2024-26749 CVE-2024-26751 CVE-2024-26752 CVE-2024-26753                      CVE-2024-26754 CVE-2024-26763 CVE-2024-26764 CVE-2024-26766                      CVE-2024-26771 CVE-2024-26772 CVE-2024-26773 CVE-2024-26776                      CVE-2024-26777 CVE-2024-26778 CVE-2024-26779 CVE-2024-26781                      CVE-2024-26782 CVE-2024-26787 CVE-2024-26788 CVE-2024-26790                      CVE-2024-26791 CVE-2024-26793 CVE-2024-26795 CVE-2024-26801                      CVE-2024-26804 CVE-2024-26805 CVE-2024-26808 CVE-2024-26809                      CVE-2024-26810 CVE-2024-26812 CVE-2024-26813 CVE-2024-26814                      CVE-2024-26816 CVE-2024-26817 CVE-2024-26820 CVE-2024-26825                      CVE-2024-26833 CVE-2024-26835 CVE-2024-26839 CVE-2024-26840                      CVE-2024-26843 CVE-2024-26845 CVE-2024-26846 CVE-2024-26848                      CVE-2024-26851 CVE-2024-26852 CVE-2024-26855 CVE-2024-26857                      CVE-2024-26859 CVE-2024-26861 CVE-2024-26862 CVE-2024-26863                      CVE-2024-26870 CVE-2024-26872 CVE-2024-26874 CVE-2024-26875                      CVE-2024-26877 CVE-2024-26878 CVE-2024-26880 CVE-2024-26882                      CVE-2024-26883 CVE-2024-26884 CVE-2024-26885 CVE-2024-26889                      CVE-2024-26891 CVE-2024-26894 CVE-2024-26895 CVE-2024-26897                      CVE-2024-26898 CVE-2024-26901 CVE-2024-26903 CVE-2024-26906                      CVE-2024-26907 CVE-2024-26910 CVE-2024-26917 CVE-2024-26920                      CVE-2024-26922 CVE-2024-26923 CVE-2024-26924 CVE-2024-26925                      CVE-2024-26926 CVE-2024-26931 CVE-2024-26934 CVE-2024-26935                      CVE-2024-26937 CVE-2024-26950 CVE-2024-26951 CVE-2024-26955                      CVE-2024-26956 CVE-2024-26957 CVE-2024-26958 CVE-2024-26960                      CVE-2024-26961 CVE-2024-26965 CVE-2024-26966 CVE-2024-26969                      CVE-2024-26970 CVE-2024-26973 CVE-2024-26974 CVE-2024-26976                      CVE-2024-26978 CVE-2024-26979 CVE-2024-26981 CVE-2024-26984                      CVE-2024-26988 CVE-2024-26993 CVE-2024-26994 CVE-2024-26997                      CVE-2024-26999 CVE-2024-27000 CVE-2024-27001 CVE-2024-27004                      CVE-2024-27008 CVE-2024-27013 CVE-2024-27020 CVE-2024-27024                      CVE-2024-27025 CVE-2024-27028 CVE-2024-27030 CVE-2024-27038                      CVE-2024-27043 CVE-2024-27044 CVE-2024-27045 CVE-2024-27046                      CVE-2024-27047 CVE-2024-27051 CVE-2024-27052 CVE-2024-27053                      CVE-2024-27059 CVE-2024-27065 CVE-2024-27073 CVE-2024-27074                      CVE-2024-27075 CVE-2024-27076 CVE-2024-27077 CVE-2024-27078                      CVE-2024-27388 CVE-2024-27437

    Several vulnerabilities have been discovered in the Linux kernel that     may lead to a privilege escalation, denial of service or information     leaks.

    For the oldstable distribution (bullseye), these problems have been     fixed in version 5.10.216-1.

    We recommend that you upgrade your linux packages.

    For the detailed security status of linux please refer to its security     tracker page at:
    https://security-tracker.debian.org/tracker/linux

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian 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 Debian 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-3842 advisory.

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-3842-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     June 25, 2024                                 https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux-5.10     Version        : 5.10.216-1~deb10u1     CVE ID         : CVE-2022-38096 CVE-2023-6270 CVE-2023-7042 CVE-2023-28746                      CVE-2023-47233 CVE-2023-52429 CVE-2023-52434 CVE-2023-52435                      CVE-2023-52447 CVE-2023-52458 CVE-2023-52482 CVE-2023-52486                      CVE-2023-52488 CVE-2023-52489 CVE-2023-52491 CVE-2023-52492                      CVE-2023-52493 CVE-2023-52497 CVE-2023-52498 CVE-2023-52583                      CVE-2023-52587 CVE-2023-52594 CVE-2023-52595 CVE-2023-52597                      CVE-2023-52598 CVE-2023-52599 CVE-2023-52600 CVE-2023-52601                      CVE-2023-52602 CVE-2023-52603 CVE-2023-52604 CVE-2023-52606                      CVE-2023-52607 CVE-2023-52614 CVE-2023-52615 CVE-2023-52616                      CVE-2023-52617 CVE-2023-52618 CVE-2023-52619 CVE-2023-52620                      CVE-2023-52622 CVE-2023-52623 CVE-2023-52627 CVE-2023-52635                      CVE-2023-52637 CVE-2023-52642 CVE-2023-52644 CVE-2023-52650                      CVE-2023-52656 CVE-2023-52669 CVE-2023-52670 CVE-2023-52672                      CVE-2023-52699 CVE-2023-52880 CVE-2024-0340 CVE-2024-0565                      CVE-2024-0607 CVE-2024-0841 CVE-2024-1151 CVE-2024-22099                      CVE-2024-23849 CVE-2024-23850 CVE-2024-23851 CVE-2024-24857                      CVE-2024-24858 CVE-2024-24861 CVE-2024-25739 CVE-2024-26581                      CVE-2024-26593 CVE-2024-26600 CVE-2024-26601 CVE-2024-26602                      CVE-2024-26606 CVE-2024-26610 CVE-2024-26614 CVE-2024-26615                      CVE-2024-26622 CVE-2024-26625 CVE-2024-26627 CVE-2024-26635                      CVE-2024-26636 CVE-2024-26640 CVE-2024-26641 CVE-2024-26642                      CVE-2024-26643 CVE-2024-26644 CVE-2024-26645 CVE-2024-26651                      CVE-2024-26654 CVE-2024-26659 CVE-2024-26663 CVE-2024-26664                      CVE-2024-26665 CVE-2024-26671 CVE-2024-26673 CVE-2024-26675                      CVE-2024-26679 CVE-2024-26684 CVE-2024-26685 CVE-2024-26687                      CVE-2024-26688 CVE-2024-26689 CVE-2024-26695 CVE-2024-26696                      CVE-2024-26697 CVE-2024-26698 CVE-2024-26702 CVE-2024-26704                      CVE-2024-26707 CVE-2024-26712 CVE-2024-26720 CVE-2024-26722                      CVE-2024-26727 CVE-2024-26733 CVE-2024-26735 CVE-2024-26736                      CVE-2024-26743 CVE-2024-26744 CVE-2024-26747 CVE-2024-26748                      CVE-2024-26749 CVE-2024-26751 CVE-2024-26752 CVE-2024-26753                      CVE-2024-26754 CVE-2024-26763 CVE-2024-26764 CVE-2024-26766                      CVE-2024-26771 CVE-2024-26772 CVE-2024-26773 CVE-2024-26776                      CVE-2024-26777 CVE-2024-26778 CVE-2024-26779 CVE-2024-26781                      CVE-2024-26782 CVE-2024-26787 CVE-2024-26788 CVE-2024-26790                      CVE-2024-26791 CVE-2024-26793 CVE-2024-26795 CVE-2024-26801                      CVE-2024-26804 CVE-2024-26805 CVE-2024-26808 CVE-2024-26809                      CVE-2024-26810 CVE-2024-26812 CVE-2024-26813 CVE-2024-26814                      CVE-2024-26816 CVE-2024-26817 CVE-2024-26820 CVE-2024-26825                      CVE-2024-26833 CVE-2024-26835 CVE-2024-26839 CVE-2024-26840                      CVE-2024-26843 CVE-2024-26845 CVE-2024-26846 CVE-2024-26848                      CVE-2024-26851 CVE-2024-26852 CVE-2024-26855 CVE-2024-26857                      CVE-2024-26859 CVE-2024-26861 CVE-2024-26862 CVE-2024-26863                      CVE-2024-26870 CVE-2024-26872 CVE-2024-26874 CVE-2024-26875                      CVE-2024-26877 CVE-2024-26878 CVE-2024-26880 CVE-2024-26882                      CVE-2024-26883 CVE-2024-26884 CVE-2024-26885 CVE-2024-26889                      CVE-2024-26891 CVE-2024-26894 CVE-2024-26895 CVE-2024-26897                      CVE-2024-26898 CVE-2024-26901 CVE-2024-26903 CVE-2024-26906                      CVE-2024-26907 CVE-2024-26910 CVE-2024-26917 CVE-2024-26922                      CVE-2024-26923 CVE-2024-26924 CVE-2024-26925 CVE-2024-26926                      CVE-2024-26931 CVE-2024-26934 CVE-2024-26935 CVE-2024-26937                      CVE-2024-26950 CVE-2024-26951 CVE-2024-26955 CVE-2024-26956                      CVE-2024-26957 CVE-2024-26958 CVE-2024-26960 CVE-2024-26961                      CVE-2024-26965 CVE-2024-26966 CVE-2024-26969 CVE-2024-26970                      CVE-2024-26973 CVE-2024-26974 CVE-2024-26976 CVE-2024-26978                      CVE-2024-26981 CVE-2024-26984 CVE-2024-26988 CVE-2024-26993                      CVE-2024-26994 CVE-2024-26997 CVE-2024-26999 CVE-2024-27000                      CVE-2024-27001 CVE-2024-27004 CVE-2024-27008 CVE-2024-27013                      CVE-2024-27020 CVE-2024-27024 CVE-2024-27025 CVE-2024-27028                      CVE-2024-27030 CVE-2024-27038 CVE-2024-27043 CVE-2024-27044                      CVE-2024-27045 CVE-2024-27046 CVE-2024-27047 CVE-2024-27051                      CVE-2024-27052 CVE-2024-27053 CVE-2024-27059 CVE-2024-27065                      CVE-2024-27073 CVE-2024-27074 CVE-2024-27075 CVE-2024-27076                      CVE-2024-27077 CVE-2024-27078 CVE-2024-27388 CVE-2024-27395                      CVE-2024-27396 CVE-2024-27405 CVE-2024-27410 CVE-2024-27412                      CVE-2024-27413 CVE-2024-27414 CVE-2024-27416 CVE-2024-27417                      CVE-2024-27419 CVE-2024-27431 CVE-2024-27436 CVE-2024-27437                      CVE-2024-35785 CVE-2024-35789 CVE-2024-35791 CVE-2024-35796                      CVE-2024-35805 CVE-2024-35806 CVE-2024-35807 CVE-2024-35809                      CVE-2024-35811 CVE-2024-35813 CVE-2024-35815 CVE-2024-35819                      CVE-2024-35821 CVE-2024-35822 CVE-2024-35823 CVE-2024-35825                      CVE-2024-35828 CVE-2024-35829 CVE-2024-35830 CVE-2024-35833                      CVE-2024-35835 CVE-2024-35837 CVE-2024-35845 CVE-2024-35847                      CVE-2024-35849 CVE-2024-35852 CVE-2024-35853 CVE-2024-35854                      CVE-2024-35855 CVE-2024-35871 CVE-2024-35877 CVE-2024-35879                      CVE-2024-35884 CVE-2024-35886 CVE-2024-35888 CVE-2024-35893                      CVE-2024-35895 CVE-2024-35896 CVE-2024-35897 CVE-2024-35898                      CVE-2024-35899 CVE-2024-35900 CVE-2024-35902 CVE-2024-35905                      CVE-2024-35910 CVE-2024-35915 CVE-2024-35922 CVE-2024-35925                      CVE-2024-35930 CVE-2024-35933 CVE-2024-35934 CVE-2024-35935                      CVE-2024-35936 CVE-2024-35940 CVE-2024-35944 CVE-2024-35950                      CVE-2024-35955 CVE-2024-35958 CVE-2024-35960 CVE-2024-35962                      CVE-2024-35967 CVE-2024-35969 CVE-2024-35973 CVE-2024-35976                      CVE-2024-35978 CVE-2024-35982 CVE-2024-35983 CVE-2024-35984                      CVE-2024-35988 CVE-2024-35990 CVE-2024-35996 CVE-2024-35997                      CVE-2024-36004 CVE-2024-36005 CVE-2024-36006 CVE-2024-36007                      CVE-2024-36008 CVE-2024-36020     Debian Bug     : 1064035

    Several vulnerabilities were discovered in the Linux kernel that may     lead to a privilege escalation, denial of service or information     leaks.

    For Debian 10 buster, these problems were fixed earlier in version     5.10.216-1~deb10u1.  This update also fixed a regression in kernel     documentation generation, and included many more bug fixes from stable     updates 5.10.210-5.10.216 inclusive.

    For the detailed security status of linux-5.10 please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/linux-5.10

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS     Attachment:
    signature.asc     Description: PGP signature

Tenable has extracted the preceding description block directly from the Debian 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
276192	TencentOS Server 4: kernel (TSSA-2025:0437)	Nessus	Tencent Local Security Checks	11/20/2025	11/20/2025	high
201889	Ubuntu 24.04 LTS : Linux kernel (Oracle) vulnerabilities (USN-6878-1)	Nessus	Ubuntu Local Security Checks	7/4/2024	3/24/2026	high
202292	Ubuntu 18.04 LTS / 20.04 LTS : Linux kernel vulnerabilities (USN-6896-1)	Nessus	Ubuntu Local Security Checks	7/12/2024	12/24/2025	high
216295	RockyLinux 8 : kernel-rt (RLSA-2025:1067)	Nessus	Rocky Linux Local Security Checks	2/14/2025	2/14/2025	high
239342	TencentOS Server 4: kernel (TSSA-2024:0981)	Nessus	Tencent Local Security Checks	6/16/2025	12/4/2025	high
195025	Debian dsa-5681 : affs-modules-5.10.0-29-4kc-malta-di - security update	Nessus	Debian Local Security Checks	5/6/2024	10/30/2025	high
201105	Debian dla-3842 : linux-config-5.10 - security update	Nessus	Debian Local Security Checks	6/27/2024	10/30/2025	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high