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

  - In the Linux kernel, the following vulnerability has been resolved: i2c: designware: use casting of u64 in     clock multiplication to avoid overflow In functions i2c_dw_scl_lcnt() and i2c_dw_scl_hcnt() may have     overflow by depending on the values of the given parameters including the ic_clk. For example in our use     case where ic_clk is larger than one million, multiplication of ic_clk * 4700 will result in 32 bit     overflow. Add cast of u64 to the calculation to avoid multiplication overflow, and use the corresponding     define for divide. (CVE-2022-49749)

  - In the Linux kernel, the following vulnerability has been resolved: kernel/irq/irqdomain.c: fix memory     leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it,     otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove()     instead which handles all of the logic at once. (CVE-2023-52936)

  - In the Linux kernel, the following vulnerability has been resolved: tracing: Fix null pointer dereference     in tracing_err_log_open() Fix an issue in function 'tracing_err_log_open'. The function doesn't call     'seq_open' if the file is opened only with write permissions, which results in 'file->private_data' being     left as null. If we then use 'lseek' on that opened file, 'seq_lseek' dereferences 'file->private_data' in     'mutex_lock(&m->lock)', resulting in a kernel panic. Writing to this node requires root privileges,     therefore this bug has very little security impact. Tracefs node: /sys/kernel/tracing/error_log Example     Kernel panic: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000038 Call     trace: mutex_lock+0x30/0x110 seq_lseek+0x34/0xb8 __arm64_sys_lseek+0x6c/0xb8 invoke_syscall+0x58/0x13c     el0_svc_common+0xc4/0x10c do_el0_svc+0x24/0x98 el0_svc+0x24/0x88 el0t_64_sync_handler+0x84/0xe4     el0t_64_sync+0x1b4/0x1b8 Code: d503201f aa0803e0 aa1f03e1 aa0103e9 (c8e97d02) ---[ end trace     561d1b49c12cf8a5 ]--- Kernel panic - not syncing: Oops: Fatal exception (CVE-2023-53167)

  - In the Linux kernel, the following vulnerability has been resolved: irqchip: Fix refcount leak in     platform_irqchip_probe of_irq_find_parent() returns a node pointer with refcount incremented, We should     use of_node_put() on it when not needed anymore. Add missing of_node_put() to avoid refcount leak.
    (CVE-2023-53610)

  - In the Linux kernel, the following vulnerability has been resolved: uio_hv_generic: Fix kernel NULL     pointer dereference in hv_uio_rescind For primary VM Bus channels, primary_channel pointer is always NULL.
    This pointer is valid only for the secondary channels. Also, rescind callback is meant for primary     channels only. Fix NULL pointer dereference by retrieving the device_obj from the parent for the primary     channel. (CVE-2024-46739)

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 12 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6243 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-6243-1                   security@debian.org     https://www.debian.org/security/                     Salvatore Bonaccorso     May 01, 2026                          https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : linux     CVE ID         : CVE-2023-53228 CVE-2023-53510 CVE-2023-53545 CVE-2024-47736                      CVE-2024-47809 CVE-2024-49998 CVE-2024-50298 CVE-2024-56719                      CVE-2025-21676 CVE-2025-21682 CVE-2025-37945 CVE-2025-37980                      CVE-2025-38105 CVE-2025-38162 CVE-2025-38192 CVE-2025-38250                      CVE-2025-38303 CVE-2025-38436 CVE-2025-38626 CVE-2025-38659                      CVE-2025-38704 CVE-2025-39748 CVE-2025-39764 CVE-2025-39863                      CVE-2025-40005 CVE-2025-40016 CVE-2025-40135 CVE-2025-40219                      CVE-2025-40242 CVE-2025-40261 CVE-2025-40358 CVE-2025-68206                      CVE-2025-68239 CVE-2025-68265 CVE-2025-71067 CVE-2025-71161                      CVE-2025-71221 CVE-2025-71265 CVE-2025-71266 CVE-2025-71267                      CVE-2025-71269 CVE-2026-23100 CVE-2026-23113 CVE-2026-23141                      CVE-2026-23154 CVE-2026-23157 CVE-2026-23204 CVE-2026-23227                      CVE-2026-23231 CVE-2026-23242 CVE-2026-23243 CVE-2026-23245                      CVE-2026-23253 CVE-2026-23270 CVE-2026-23271 CVE-2026-23273                      CVE-2026-23274 CVE-2026-23277 CVE-2026-23279 CVE-2026-23281                      CVE-2026-23284 CVE-2026-23286 CVE-2026-23287 CVE-2026-23289                      CVE-2026-23290 CVE-2026-23291 CVE-2026-23292 CVE-2026-23293                      CVE-2026-23296 CVE-2026-23298 CVE-2026-23300 CVE-2026-23303                      CVE-2026-23304 CVE-2026-23306 CVE-2026-23307 CVE-2026-23312                      CVE-2026-23315 CVE-2026-23317 CVE-2026-23318 CVE-2026-23319                      CVE-2026-23321 CVE-2026-23324 CVE-2026-23335 CVE-2026-23336                      CVE-2026-23339 CVE-2026-23340 CVE-2026-23343 CVE-2026-23351                      CVE-2026-23352 CVE-2026-23356 CVE-2026-23357 CVE-2026-23359                      CVE-2026-23362 CVE-2026-23364 CVE-2026-23365 CVE-2026-23367                      CVE-2026-23368 CVE-2026-23370 CVE-2026-23372 CVE-2026-23378                      CVE-2026-23379 CVE-2026-23381 CVE-2026-23382 CVE-2026-23388                      CVE-2026-23391 CVE-2026-23392 CVE-2026-23395 CVE-2026-23396                      CVE-2026-23397 CVE-2026-23398 CVE-2026-23401 CVE-2026-23414                      CVE-2026-23420 CVE-2026-23422 CVE-2026-23426 CVE-2026-23428                      CVE-2026-23434 CVE-2026-23438 CVE-2026-23439 CVE-2026-23446                      CVE-2026-23449 CVE-2026-23450 CVE-2026-23452 CVE-2026-23454                      CVE-2026-23455 CVE-2026-23456 CVE-2026-23457 CVE-2026-23458                      CVE-2026-23460 CVE-2026-23462 CVE-2026-23463 CVE-2026-23474                      CVE-2026-23475 CVE-2026-31389 CVE-2026-31391 CVE-2026-31392                      CVE-2026-31393 CVE-2026-31396 CVE-2026-31399 CVE-2026-31400                      CVE-2026-31402 CVE-2026-31403 CVE-2026-31405 CVE-2026-31408                      CVE-2026-31409 CVE-2026-31411 CVE-2026-31412 CVE-2026-31414                      CVE-2026-31415 CVE-2026-31416 CVE-2026-31417 CVE-2026-31418                      CVE-2026-31421 CVE-2026-31422 CVE-2026-31423 CVE-2026-31424                      CVE-2026-31425 CVE-2026-31426 CVE-2026-31427 CVE-2026-31428                      CVE-2026-31431 CVE-2026-31433 CVE-2026-31434 CVE-2026-31441                      CVE-2026-31446 CVE-2026-31447 CVE-2026-31448 CVE-2026-31450                      CVE-2026-31452 CVE-2026-31453 CVE-2026-31454 CVE-2026-31455                      CVE-2026-31464 CVE-2026-31466 CVE-2026-31467 CVE-2026-31469                      CVE-2026-31473 CVE-2026-31476 CVE-2026-31477 CVE-2026-31478                      CVE-2026-31480 CVE-2026-31483 CVE-2026-31485 CVE-2026-31492                      CVE-2026-31494 CVE-2026-31495 CVE-2026-31496 CVE-2026-31497                      CVE-2026-31498 CVE-2026-31503 CVE-2026-31504 CVE-2026-31507                      CVE-2026-31508 CVE-2026-31509 CVE-2026-31510 CVE-2026-31512                      CVE-2026-31515 CVE-2026-31518 CVE-2026-31519 CVE-2026-31520                      CVE-2026-31521 CVE-2026-31522 CVE-2026-31523 CVE-2026-31524                      CVE-2026-31533 CVE-2026-31540 CVE-2026-31545 CVE-2026-31546                      CVE-2026-31548 CVE-2026-31549 CVE-2026-31550 CVE-2026-31551                      CVE-2026-31552 CVE-2026-31555 CVE-2026-31563 CVE-2026-31565                      CVE-2026-31566 CVE-2026-31570 CVE-2026-31628 CVE-2026-31634                      CVE-2026-31649 CVE-2026-31651 CVE-2026-31656 CVE-2026-31657                      CVE-2026-31658 CVE-2026-31659 CVE-2026-31660 CVE-2026-31661                      CVE-2026-31662 CVE-2026-31664 CVE-2026-31665 CVE-2026-31667                      CVE-2026-31668 CVE-2026-31669 CVE-2026-31670 CVE-2026-31671                      CVE-2026-31672 CVE-2026-31674 CVE-2026-31678 CVE-2026-31679                      CVE-2026-31680 CVE-2026-31682 CVE-2026-31683 CVE-2026-31689                      CVE-2026-31695 CVE-2026-31720 CVE-2026-31721 CVE-2026-31726                      CVE-2026-31728 CVE-2026-31737 CVE-2026-31738 CVE-2026-31747                      CVE-2026-31748 CVE-2026-31749 CVE-2026-31751 CVE-2026-31752                      CVE-2026-31754 CVE-2026-31755 CVE-2026-31756 CVE-2026-31758                      CVE-2026-31759 CVE-2026-31761 CVE-2026-31762 CVE-2026-31763                      CVE-2026-31768 CVE-2026-31770 CVE-2026-31773 CVE-2026-31776                      CVE-2026-31778 CVE-2026-31779 CVE-2026-31780 CVE-2026-31781                      CVE-2026-31786 CVE-2026-31787 CVE-2026-31788 CVE-2026-43011                      CVE-2026-43013 CVE-2026-43014 CVE-2026-43015 CVE-2026-43017                      CVE-2026-43018 CVE-2026-43020 CVE-2026-43023 CVE-2026-43024                      CVE-2026-43025 CVE-2026-43026 CVE-2026-43027 CVE-2026-43028                      CVE-2026-43030 CVE-2026-43032 CVE-2026-43033 CVE-2026-43035                      CVE-2026-43037 CVE-2026-43038 CVE-2026-43040 CVE-2026-43041                      CVE-2026-43043 CVE-2026-43046 CVE-2026-43047 CVE-2026-43050                      CVE-2026-43051 CVE-2026-43054 CVE-2026-43057

    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 (bookworm), these problems have been fixed     in version 6.1.170-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 AlmaLinux 9.2 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.2:CLSA-2026:1778266904 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: samples/landlock: Fix path_list memory     leak Clang static analysis reports this error sandboxer.c:134:8: warning: Potential leak of memory pointed     to by 'path_list' ret = 0; ^ path_list is allocated in parse_path() but never freed. (CVE-2021-47654)

  - In the Linux kernel, the following vulnerability has been resolved: tty: synclink_gt: Fix null-pointer-     dereference in slgt_clean() When the driver fails at alloc_hdlcdev(), and then we remove the driver     module, we will get the following splat: [ 25.065966] general protection fault, probably for non-canonical     address 0xdffffc0000000182: 0000 [#1] PREEMPT SMP KASAN PTI [ 25.066914] KASAN: null-ptr-deref in range     [0x0000000000000c10-0x0000000000000c17] [ 25.069262] RIP: 0010:detach_hdlc_protocol+0x2a/0x3e0 [     25.077709] Call Trace: [ 25.077924] <TASK> [ 25.078108] unregister_hdlc_device+0x16/0x30 [ 25.078481]     slgt_cleanup+0x157/0x9f0 [synclink_gt] Fix this by checking whether the 'info->netdev' is a null pointer     first. (CVE-2022-49307)

  - In the Linux kernel, the following vulnerability has been resolved: ima: Fix potential memory leak in     ima_init_crypto() On failure to allocate the SHA1 tfm, IMA fails to initialize and exits without freeing     the ima_algo_array. Add the missing kfree() for ima_algo_array to avoid the potential memory leak.
    (CVE-2022-49627)

  - In the Linux kernel, the following vulnerability has been resolved: tracing/histograms: Fix memory leak     problem This reverts commit 46bbe5c671e06f070428b9be142cc4ee5cedebac. As commit 46bbe5c671e0 (tracing:
    fix double free) said, the double free problem reported by clang static analyzer is: > In     parse_var_defs() if there is a problem allocating > var_defs.expr, the earlier var_defs.name is freed. >     This free is duplicated by free_var_defs() which frees > the rest of the list. However, if there is a     problem allocating N-th var_defs.expr: + in parse_var_defs(), the freed 'earlier var_defs.name' is     actually the N-th var_defs.name; + then in free_var_defs(), the names from 0th to (N-1)-th are freed; IF     ALLOCATING PROBLEM HAPPENED HERE!!! -+ \ | 0th 1th (N-1)-th N-th V     +-------------+-------------+-----+-------------+----------- var_defs: | name | expr | name | expr | ... |     name | expr | name | /// +-------------+-------------+-----+-------------+----------- These two frees     don't act on same name, so there was no double free problem before. Conversely, after that commit, we     get a memory leak problem because the above N-th var_defs.name is not freed. If enable     CONFIG_DEBUG_KMEMLEAK and inject a fault at where the N-th var_defs.expr allocated, then execute on shell     like: $ echo 'hist:key=call_site:val=$v1,$v2:v1=bytes_req,v2=bytes_alloc' > \     /sys/kernel/debug/tracing/events/kmem/kmalloc/trigger Then kmemleak reports: unreferenced object     0xffff8fb100ef3518 (size 8): comm bash, pid 196, jiffies 4295681690 (age 28.538s) hex dump (first 8     bytes): 76 31 00 00 b1 8f ff ff v1...... backtrace: [<0000000038fe4895>] kstrdup+0x2d/0x60     [<00000000c99c049a>] event_hist_trigger_parse+0x206f/0x20e0 [<00000000ae70d2cc>]     trigger_process_regex+0xc0/0x110 [<0000000066737a4c>] event_trigger_write+0x75/0xd0 [<000000007341e40c>]     vfs_write+0xbb/0x2a0 [<0000000087fde4c2>] ksys_write+0x59/0xd0 [<00000000581e9cdf>]     do_syscall_64+0x3a/0x80 [<00000000cf3b065c>] entry_SYSCALL_64_after_hwframe+0x46/0xb0 (CVE-2022-49648)

  - In the Linux kernel, the following vulnerability has been resolved: linux/dim: Fix divide by 0 in RDMA DIM     Fix a divide 0 error in rdma_dim_stats_compare() when prev->cpe_ratio == 0. CallTrace: Hardware name: H3C     R4900 G3/RS33M2C9S, BIOS 2.00.37P21 03/12/2020 task: ffff880194b78000 task.stack: ffffc90006714000 RIP:
    0010:backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: 0018:ffff880c10e83ec0 EFLAGS: 00010202 RAX:
    0000000000002710 RBX: ffff88096cd7f780 RCX: 0000000000000064 RDX: 0000000000000000 RSI: 0000000000000002     RDI: 0000000000000001 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10:
    0000000000000000 R11: 0000000000000000 R12: 000000001d7c6c09 R13: ffff88096cd7f780 R14: ffff880b174fe800     R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff880c10e80000(0000) knlGS:0000000000000000 CS: 0010     DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000a0965b00 CR3: 000000000200a003 CR4: 00000000007606e0     DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6:
    00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <IRQ> ib_poll_handler+0x43/0x80     [ib_core] irq_poll_softirq+0xae/0x110 __do_softirq+0xd1/0x28c irq_exit+0xde/0xf0 do_IRQ+0x54/0xe0     common_interrupt+0x8f/0x8f </IRQ> ? cpuidle_enter_state+0xd9/0x2a0 ? cpuidle_enter_state+0xc7/0x2a0 ?     do_idle+0x170/0x1d0 ? cpu_startup_entry+0x6f/0x80 ? start_secondary+0x1b9/0x210 ?     secondary_startup_64+0xa5/0xb0 Code: 0f 87 e1 00 00 00 8b 4c 24 14 44 8b 43 14 89 c8 4d 63 c8 44 29 c0 99     31 d0 29 d0 31 d2 48 98 48 8d 04 80 48 8d 04 80 48 c1 e0 02 <49> f7 f1 48 83 f8 0a 0f 86 c1 00 00 00 44 39     c1 7f 10 48 89 df RIP: backport_rdma_dim+0x10e/0x240 [mlx_compat] RSP: ffff880c10e83ec0 (CVE-2022-49670)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
340680	Ubuntu 24.04 LTS / Pro Realtime 24.04 LTS : Linux kernel (Raspberry Pi) vulnerabilities (USN-8665-1)	Nessus	Ubuntu Local Security Checks	2026/8/26	2026/8/27	high
360739	AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1781344094)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	high
324048	SUSE SLED15 / SLES15 : Security update for the Linux Kernel (SUSE-SU-2026:2238-1)	Nessus	SuSE Local Security Checks	2026/7/1	2026/9/29	high
311547	Debian dsa-6243 : affs-modules-6.1.0-44-4kc-malta-di - security update	Nessus	Debian Local Security Checks	2026/5/2	2026/5/8	high
361258	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1778266904)	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/2	high

检测

插件搜索

high

high

high

high

high