In the Linux kernel, the following vulnerability has been resolved: wifi: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req() mt76_connac_mcu_alloc_sta_req() allocates an skb which is expected to be freed eventually by mt76_mcu_skb_send_msg(). However, currently if an intermediate function fails before sending, the allocated skb is leaked. Specifically, mt76_connac_mcu_sta_wed_update() and mt76_connac_mcu_sta_key_tlv() may fail, leading to an immediate memory leak in the error path. Fix this by explicitly freeing the skb in these error paths. Commit 7c0f63fe37a5 ("wifi: mt76: mt7996: fix memory leak on mt7996_mcu_sta_key_tlv error") made a similar change. Compile tested only. Issue found using a prototype static analysis tool and code review.

oracle_linux ELSA-2026-500374: ELSA-2026-500374: Unbreakable Enterprise kernel security update (IMPORTANT)

The AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1787307395 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: ftrace: Clean up hash direct_functions     on register failures We see the following GPF when register_ftrace_direct fails: [ ] general protection     fault, probably for non-canonical address \ 0x200000000000010: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC PTI     [...] [ ] RIP: 0010:ftrace_find_rec_direct+0x53/0x70 [ ] Code: 48 c1 e0 03 48 03 42 08 48 8b 10 31 c0 48     85 d2 74 [...] [ ] RSP: 0018:ffffc9000138bc10 EFLAGS: 00010206 [ ] RAX: 0000000000000000 RBX:
    ffffffff813e0df0 RCX: 000000000000003b [ ] RDX: 0200000000000000 RSI: 000000000000000c RDI:
    ffffffff813e0df0 [ ] RBP: ffffffffa00a3000 R08: ffffffff81180ce0 R09: 0000000000000001 [ ] R10:
    ffffc9000138bc18 R11: 0000000000000001 R12: ffffffff813e0df0 [ ] R13: ffffffff813e0df0 R14:
    ffff888171b56400 R15: 0000000000000000 [ ] FS: 00007fa9420c7780(0000) GS:ffff888ff6a00000(0000)     knlGS:000000000 [ ] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ ] CR2: 000000000770d000 CR3:
    0000000107d50003 CR4: 0000000000370ee0 [ ] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
    0000000000000000 [ ] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ ] Call Trace: [ ]     <TASK> [ ] register_ftrace_direct+0x54/0x290 [ ] ? render_sigset_t+0xa0/0xa0 [ ]     bpf_trampoline_update+0x3f5/0x4a0 [ ] ? 0xffffffffa00a3000 [ ] bpf_trampoline_link_prog+0xa9/0x140 [ ]     bpf_tracing_prog_attach+0x1dc/0x450 [ ] bpf_raw_tracepoint_open+0x9a/0x1e0 [ ] ? find_held_lock+0x2d/0x90     [ ] ? lock_release+0x150/0x430 [ ] __sys_bpf+0xbd6/0x2700 [ ] ? lock_is_held_type+0xd8/0x130 [ ]
    __x64_sys_bpf+0x1c/0x20 [ ] do_syscall_64+0x3a/0x80 [ ] entry_SYSCALL_64_after_hwframe+0x44/0xae [ ] RIP:
    0033:0x7fa9421defa9 [ ] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 9 f8 [...] [ ] RSP:
    002b:00007ffed743bd78 EFLAGS: 00000246 ORIG_RAX: 0000000000000141 [ ] RAX: ffffffffffffffda RBX:
    00000000069d2480 RCX: 00007fa9421defa9 [ ] RDX: 0000000000000078 RSI: 00007ffed743bd80 RDI:
    0000000000000011 [ ] RBP: 00007ffed743be00 R08: 0000000000bb7270 R09: 0000000000000000 [ ] R10:
    00000000069da210 R11: 0000000000000246 R12: 0000000000000001 [ ] R13: 00007ffed743c4b0 R14:
    00000000069d2480 R15: 0000000000000001 [ ] </TASK> [ ] Modules linked in: klp_vm(OK) [ ] ---[ end trace     0000000000000000 ]--- One way to trigger this is: 1. load a livepatch that patches kernel function xxx; 2.
    run bpftrace -e 'kfunc:xxx {}', this will fail (expected for now); 3. repeat #2 => gpf. This is because     the entry is added to direct_functions, but not removed. Fix this by remove the entry from     direct_functions when register_ftrace_direct fails. Also remove the last trailing space from ftrace.c, so     we don't have to worry about it anymore. (CVE-2022-49402)

  - In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v3: Fix refcount leak in     gic_populate_ppi_partitions of_find_node_by_phandle() returns a node pointer with refcount incremented, we     should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak.
    (CVE-2022-49715)

  - In the Linux kernel, the following vulnerability has been resolved: cpufreq: CPPC: Add u64 casts to avoid     overflowing The fields of the _CPC object are unsigned 32-bits values. To avoid overflows while using
    _CPC's values, add 'u64' casts. (CVE-2022-49750)

  - In the Linux kernel, the following vulnerability has been resolved: net: stream: purge sk_error_queue in     sk_stream_kill_queues() Changheon Lee reported TCP socket leaks, with a nice repro. It seems we leak TCP     sockets with the following sequence: 1) SOF_TIMESTAMPING_TX_ACK is enabled on the socket. Each ACK will     cook an skb put in error queue, from __skb_tstamp_tx(). __skb_tstamp_tx() is using skb_clone(), unless     SOF_TIMESTAMPING_OPT_TSONLY was also requested. 2) If the application is also using MSG_ZEROCOPY, then we     put in the error queue cloned skbs that had a struct ubuf_info attached to them. Whenever an struct     ubuf_info is allocated, sock_zerocopy_alloc() does a sock_hold(). As long as the cloned skbs are still in     sk_error_queue, socket refcount is kept elevated. 3) Application closes the socket, while error queue is     not empty. Since tcp_close() no longer purges the socket error queue, we might end up with a TCP socket     with at least one skb in error queue keeping the socket alive forever. This bug can be (ab)used to consume     all kernel memory and freeze the host. We need to purge the error queue, with proper synchronization     against concurrent writers. (CVE-2022-50838)

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Add preempt_count_{sub,add} into     btf id deny list The recursion check in __bpf_prog_enter* and __bpf_prog_exit* leave     preempt_count_{sub,add} unprotected. When attaching trampoline to them we get panic as follows, [     867.843050] BUG: TASK stack guard page was hit at 0000000009d325cf (stack is     0000000046a46a15..00000000537e7b28) [ 867.843064] stack guard page: 0000 [#1] PREEMPT SMP NOPTI [     867.843067] CPU: 8 PID: 11009 Comm: trace Kdump: loaded Not tainted 6.2.0+ #4 [ 867.843100] Call Trace: [     867.843101] <TASK> [ 867.843104] asm_exc_int3+0x3a/0x40 [ 867.843108] RIP: 0010:preempt_count_sub+0x1/0xa0     [ 867.843135] __bpf_prog_enter_recur+0x17/0x90 [ 867.843148] bpf_trampoline_6442468108_0+0x2e/0x1000 [     867.843154] ? preempt_count_sub+0x1/0xa0 [ 867.843157] preempt_count_sub+0x5/0xa0 [ 867.843159] ?     migrate_enable+0xac/0xf0 [ 867.843164] __bpf_prog_exit_recur+0x2d/0x40 [ 867.843168]     bpf_trampoline_6442468108_0+0x55/0x1000 ... [ 867.843788] preempt_count_sub+0x5/0xa0 [ 867.843793] ?     migrate_enable+0xac/0xf0 [ 867.843829] __bpf_prog_exit_recur+0x2d/0x40 [ 867.843837] BUG: IRQ stack guard     page was hit at 0000000099bd8228 (stack is 00000000b23e2bc4..000000006d95af35) [ 867.843841] BUG: IRQ     stack guard page was hit at 000000005ae07924 (stack is 00000000ffd69623..0000000014eb594c) [ 867.843843]     BUG: IRQ stack guard page was hit at 00000000028320f0 (stack is 00000000034b6438..0000000078d1bcec) [     867.843842] bpf_trampoline_6442468108_0+0x55/0x1000 ... That is because in __bpf_prog_exit_recur, the     preempt_count_{sub,add} are called after prog->active is decreased. Fixing this by adding these two     functions into btf ids deny list. (CVE-2023-54086)

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

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: 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)

  - In the Linux kernel, the following vulnerability has been resolved: x86/tdx: Fix data leak in mmio_read()     The mmio_read() function makes a TDVMCALL to retrieve MMIO data for an address from the VMM. Sean noticed     that mmio_read() unintentionally exposes the value of an initialized variable (val) on the stack to the     VMM. This variable is only needed as an output value. It did not need to be passed to the VMM in the first     place. Do not send the original value of *val to the VMM. [ dhansen: clarify what 'val' is used for. ]     (CVE-2024-46794)

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: 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)

  - In the Linux kernel, the following vulnerability has been resolved: x86/tdx: Fix data leak in mmio_read()     The mmio_read() function makes a TDVMCALL to retrieve MMIO data for an address from the VMM. Sean noticed     that mmio_read() unintentionally exposes the value of an initialized variable (val) on the stack to the     VMM. This variable is only needed as an output value. It did not need to be passed to the VMM in the first     place. Do not send the original value of *val to the VMM. [ dhansen: clarify what 'val' is used for. ]     (CVE-2024-46794)

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.

  - wifi: mt76: Fix memory leak after mt76_connac_mcu_alloc_sta_req() mt76_connac_mcu_alloc_sta_req()     allocates an skb which is expected to be freed eventually by mt76_mcu_skb_send_msg(). However, currently     if an intermediate function fails before sending, the allocated skb is leaked. Specifically,     mt76_connac_mcu_sta_wed_update() and mt76_connac_mcu_sta_key_tlv() may fail, leading to an immediate     memory leak in the error path. Fix this by explicitly freeing the skb in these error paths. Commit     7c0f63fe37a5 (wifi: mt76: mt7996: fix memory leak on mt7996_mcu_sta_key_tlv error) made a similar     change. Compile tested only. Issue found using a prototype static analysis tool and code review.
    (CVE-2026-53102)

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

ID	Name	Product	Family	Type	Severity
362907	Debian dla-4817 : ata-modules-6.12.107+deb12-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
361223	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1787307395)	Nessus	Alma Linux Local Security Checks	Local	medium
360569	Rocky Linux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1786352940)	Nessus	Rocky Linux Local Security Checks	Local	high
360481	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1786352940)	Nessus	Alma Linux Local Security Checks	Local	high
351155	Debian dsa-6528 : ata-modules-6.12.111+deb13-armmp-di - security update	Nessus	Debian Local Security Checks	Local	high
343532	Ubuntu 24.04 LTS / Pro Realtime 24.04 LTS : Linux kernel (GCP) vulnerabilities (USN-8728-1)	Nessus	Ubuntu Local Security Checks	Local	high
340681	Ubuntu 24.04 LTS / 26.04 LTS / Pro Realtime 24.04 LTS : Linux kernel (NVIDIA) vulnerabilities (USN-8663-1)	Nessus	Ubuntu Local Security Checks	Local	high
340045	Ubuntu 26.04 LTS : Linux kernel (NVIDIA BaseOS) vulnerabilities (USN-8664-1)	Nessus	Ubuntu Local Security Checks	Local	high
335080	openSUSE 16: cluster-md-kmp-64kb / cluster-md-kmp-azure / cluster-md-kmp-default / etc (openSUSE-SU-2026:21555-1)	Nessus	SuSE Local Security Checks	Local	high
322720	Linux Distros Unpatched Vulnerability : CVE-2026-53102	Nessus	Misc.	Local	medium

Detections

Analytics

CVE-2026-53102

medium

Tenable Plugins

Coming Soon

high

medium

high

high

high

high

high

high

high

medium