The Rocky Linux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1786352940 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: serial: imx: fix tx statemachine     deadlock When using the serial port as RS485 port, the tx statemachine is used to control the RTS pin to     drive the RS485 transceiver TX_EN pin. When the TTY port is closed in the middle of a transmission (for     instance during userland application crash), imx_uart_shutdown disables the interface and disables the     Transmission Complete interrupt. afer that, imx_uart_stop_tx bails on an incomplete transmission, to be     retriggered by the TC interrupt. This interrupt is disabled and therefore the tx statemachine never     transitions out of SEND. The statemachine is in deadlock now, and the TX_EN remains low, making the     interface useless. imx_uart_stop_tx now checks for incomplete transmission AND whether TC interrupts are     enabled before bailing to be retriggered. This makes sure the state machine handling is reached, and is     properly set to WAIT_AFTER_SEND. (CVE-2023-52456)

  - In the Linux kernel, the following vulnerability has been resolved: ubi: Fix use-after-free when volume     resizing failed There is an use-after-free problem reported by KASAN:
    ================================================================== BUG: KASAN: use-after-free in     ubi_eba_copy_table+0x11f/0x1c0 [ubi] Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735 CPU: 2     PID: 4735 Comm: ubirsvol Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty #14 Hardware name: QEMU Standard     PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44     print_report+0x171/0x472 kasan_report+0xad/0x130 ubi_eba_copy_table+0x11f/0x1c0 [ubi]     ubi_resize_volume+0x4f9/0xbc0 [ubi] ubi_cdev_ioctl+0x701/0x1850 [ubi] __x64_sys_ioctl+0x11d/0x170     do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> When ubi_change_vtbl_record()     returns an error in ubi_resize_volume(), new_eba_tbl will be freed on error handing path, but it is     holded by vol->eba_tbl in ubi_eba_replace_table(). It means that the liftcycle of vol->eba_tbl and     vol are different, so when resizing volume in next time, it causing an use-after-free fault. Fix it by     not freeing new_eba_tbl after it replaced in ubi_eba_replace_table(), while will be freed in next volume     resizing. (CVE-2023-53800)

  - In the Linux kernel, the following vulnerability has been resolved: kdb: Fix buffer overflow during tab-     complete Currently, when the user attempts symbol completion with the Tab key, kdb will use strncpy() to     insert the completed symbol into the command buffer. Unfortunately it passes the size of the source buffer     rather than the destination to strncpy() with predictably horrible results. Most obviously if the command     buffer is already full but cp, the cursor position, is in the middle of the buffer, then we will write     past the end of the supplied buffer. Fix this by replacing the dubious strncpy() calls with     memmove()/memcpy() calls plus explicit boundary checks to make sure we have enough space before we start     moving characters around. (CVE-2024-39480)

  - In the Linux kernel, the following vulnerability has been resolved: Fix userfaultfd_api to return EINVAL     as expected Currently if we request a feature that is not set in the Kernel config we fail silently and     return all the available features. However, the man page indicates we should return an EINVAL. We need to     fix this issue since we can end up with a Kernel warning should a program request the feature     UFFD_FEATURE_WP_UNPOPULATED on a kernel with the config not set with this feature. [ 200.812896] WARNING:
    CPU: 91 PID: 13634 at mm/memory.c:1660 zap_pte_range+0x43d/0x660 [ 200.820738] Modules linked in: [     200.869387] CPU: 91 PID: 13634 Comm: userfaultfd Kdump: loaded Not tainted 6.9.0-rc5+ #8 [ 200.877477]     Hardware name: Dell Inc. PowerEdge R6525/0N7YGH, BIOS 2.7.3 03/30/2022 [ 200.885052] RIP:
    0010:zap_pte_range+0x43d/0x660 (CVE-2024-41027)

  - In the Linux kernel, the following vulnerability has been resolved: mlxsw: core_linecards: Fix double     memory deallocation in case of invalid INI file In case of invalid INI file mlxsw_linecard_types_init()     deallocates memory but doesn't reset pointer to NULL and returns 0. In case of any error occurred after     mlxsw_linecard_types_init() call, mlxsw_linecards_init() calls mlxsw_linecard_types_fini() which performs     memory deallocation again. Add pointer reset to NULL. Found by Linux Verification Center     (linuxtesting.org) with SVACE. (CVE-2024-42138)

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

  - In the Linux kernel, the following vulnerability has been resolved: serial: imx: fix tx statemachine     deadlock When using the serial port as RS485 port, the tx statemachine is used to control the RTS pin to     drive the RS485 transceiver TX_EN pin. When the TTY port is closed in the middle of a transmission (for     instance during userland application crash), imx_uart_shutdown disables the interface and disables the     Transmission Complete interrupt. afer that, imx_uart_stop_tx bails on an incomplete transmission, to be     retriggered by the TC interrupt. This interrupt is disabled and therefore the tx statemachine never     transitions out of SEND. The statemachine is in deadlock now, and the TX_EN remains low, making the     interface useless. imx_uart_stop_tx now checks for incomplete transmission AND whether TC interrupts are     enabled before bailing to be retriggered. This makes sure the state machine handling is reached, and is     properly set to WAIT_AFTER_SEND. (CVE-2023-52456)

  - In the Linux kernel, the following vulnerability has been resolved: ubi: Fix use-after-free when volume     resizing failed There is an use-after-free problem reported by KASAN:
    ================================================================== BUG: KASAN: use-after-free in     ubi_eba_copy_table+0x11f/0x1c0 [ubi] Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735 CPU: 2     PID: 4735 Comm: ubirsvol Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty #14 Hardware name: QEMU Standard     PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x34/0x44     print_report+0x171/0x472 kasan_report+0xad/0x130 ubi_eba_copy_table+0x11f/0x1c0 [ubi]     ubi_resize_volume+0x4f9/0xbc0 [ubi] ubi_cdev_ioctl+0x701/0x1850 [ubi] __x64_sys_ioctl+0x11d/0x170     do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 </TASK> When ubi_change_vtbl_record()     returns an error in ubi_resize_volume(), new_eba_tbl will be freed on error handing path, but it is     holded by vol->eba_tbl in ubi_eba_replace_table(). It means that the liftcycle of vol->eba_tbl and     vol are different, so when resizing volume in next time, it causing an use-after-free fault. Fix it by     not freeing new_eba_tbl after it replaced in ubi_eba_replace_table(), while will be freed in next volume     resizing. (CVE-2023-53800)

  - In the Linux kernel, the following vulnerability has been resolved: kdb: Fix buffer overflow during tab-     complete Currently, when the user attempts symbol completion with the Tab key, kdb will use strncpy() to     insert the completed symbol into the command buffer. Unfortunately it passes the size of the source buffer     rather than the destination to strncpy() with predictably horrible results. Most obviously if the command     buffer is already full but cp, the cursor position, is in the middle of the buffer, then we will write     past the end of the supplied buffer. Fix this by replacing the dubious strncpy() calls with     memmove()/memcpy() calls plus explicit boundary checks to make sure we have enough space before we start     moving characters around. (CVE-2024-39480)

  - In the Linux kernel, the following vulnerability has been resolved: Fix userfaultfd_api to return EINVAL     as expected Currently if we request a feature that is not set in the Kernel config we fail silently and     return all the available features. However, the man page indicates we should return an EINVAL. We need to     fix this issue since we can end up with a Kernel warning should a program request the feature     UFFD_FEATURE_WP_UNPOPULATED on a kernel with the config not set with this feature. [ 200.812896] WARNING:
    CPU: 91 PID: 13634 at mm/memory.c:1660 zap_pte_range+0x43d/0x660 [ 200.820738] Modules linked in: [     200.869387] CPU: 91 PID: 13634 Comm: userfaultfd Kdump: loaded Not tainted 6.9.0-rc5+ #8 [ 200.877477]     Hardware name: Dell Inc. PowerEdge R6525/0N7YGH, BIOS 2.7.3 03/30/2022 [ 200.885052] RIP:
    0010:zap_pte_range+0x43d/0x660 (CVE-2024-41027)

  - In the Linux kernel, the following vulnerability has been resolved: mlxsw: core_linecards: Fix double     memory deallocation in case of invalid INI file In case of invalid INI file mlxsw_linecard_types_init()     deallocates memory but doesn't reset pointer to NULL and returns 0. In case of any error occurred after     mlxsw_linecard_types_init() call, mlxsw_linecards_init() calls mlxsw_linecard_types_fini() which performs     memory deallocation again. Add pointer reset to NULL. Found by Linux Verification Center     (linuxtesting.org) with SVACE. (CVE-2024-42138)

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

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

  - drm/xe/reg_sr: Fix leak on xa_store failure Free the newly allocated entry when xa_store() fails to avoid     a memory leak on the error path. v2: use goto fail_free. (Bala) (cherry picked from commit     6bc6fec71ac45f52db609af4e62bdb96b9f5fadb) (CVE-2026-23418)

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

ID	Name	Product	Family	Published	Updated	Severity
360569	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1786352940)	Nessus	Rocky Linux Local Security Checks	10/1/2026	10/28/2026	high
360481	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1786352940)	Nessus	Alma Linux Local Security Checks	10/1/2026	10/28/2026	high
324048	SUSE SLED15 / SLES15 : Security update for the Linux Kernel (SUSE-SU-2026:2238-1)	Nessus	SuSE Local Security Checks	7/1/2026	10/29/2026	high
318102	openSUSE 16 Security Update : kernel (openSUSE-SU-2026:20826-1)	Nessus	SuSE Local Security Checks	6/1/2026	10/20/2026	high
340680	Ubuntu 24.04 LTS / Pro Realtime 24.04 LTS : Linux kernel (Raspberry Pi) vulnerabilities (USN-8665-1)	Nessus	Ubuntu Local Security Checks	8/26/2026	11/11/2026	high
319659	SUSE SLES16 Security Update : kernel (SUSE-SU-2026:21845-1)	Nessus	SuSE Local Security Checks	6/8/2026	10/15/2026	high
304915	Linux Distros Unpatched Vulnerability : CVE-2026-23418	Nessus	Misc.	4/5/2026	11/13/2026	medium
318240	SUSE SLES16 Security Update : kernel (SUSE-SU-2026:21860-1)	Nessus	SuSE Local Security Checks	6/2/2026	10/20/2026	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

medium

high