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

  - In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot     reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED     indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiobus_register() fails, but     device_register() was called In case of device_register() has been called we should call put_device() to     correctly free the memory allocated for this device, but mdiobus_free() calls just kfree(dev) in case of     MDIOBUS_ALLOCATED state To avoid this behaviour we need to set bus->state to MDIOBUS_UNREGISTERED _before_     calling device_register(), because put_device() should be called even in case of device_register()     failure. (CVE-2021-47416)

  - An out-of-bounds read flaw was found in the Linux kernel's TeleTYpe subsystem. The issue occurs in how a     user triggers a race condition using ioctls TIOCSPTLCK and TIOCGPTPEER and TIOCSTI and TCXONC with leakage     of memory in the flush_to_ldisc function. This flaw allows a local user to crash the system or read     unauthorized random data from memory. (CVE-2022-1462)

  - In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in     isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached     with a compliant CAN ID address configuration. The provided address information consisted of CAN ID     0x6000001 and 0xC28001 which both boil down to 11 bit CAN IDs 0x001 in sending and receiving. Sanitize the     SFF/EFF CAN ID values before performing the address checks. (CVE-2022-49269)

  - In the Linux kernel, the following vulnerability has been resolved: tty: fix deadlock caused by calling     printk() under tty_port->lock pty_write() invokes kmalloc() which may invoke a normal printk() to print     failure message. This can cause a deadlock in the scenario reported by syz-bot below: CPU0 CPU1 CPU2 ----
    ---- ---- lock(console_owner); lock(&port_lock_key); lock(&port->lock); lock(&port_lock_key);
    lock(&port->lock); lock(console_owner); As commit dbdda842fe96 (printk: Add console owner and waiter     logic to load balance console writes) said, such deadlock can be prevented by using printk_deferred() in     kmalloc() (which is invoked in the section guarded by the port->lock). But there are too many printk() on     the kmalloc() path, and kmalloc() can be called from anywhere, so changing printk() to printk_deferred()     is too complicated and inelegant. Therefore, this patch chooses to specify __GFP_NOWARN to kmalloc(), so     that printk() will not be called, and this deadlock problem can be avoided. Syzbot reported the following     lockdep error: ====================================================== WARNING: possible circular locking     dependency detected 5.4.143-00237-g08ccc19a-dirty #10 Not tainted
    ------------------------------------------------------ syz-executor.4/29420 is trying to acquire lock:
    ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: console_trylock_spinning kernel/printk/printk.c:1752     [inline] ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: vprintk_emit+0x2ca/0x470     kernel/printk/printk.c:2023 but task is already holding lock: ffff8880119c9158 (&port->lock){-.-.}-{2:2},     at: pty_write+0xf4/0x1f0 drivers/tty/pty.c:120 which lock already depends on the new lock. the existing     dependency chain (in reverse order) is: -> #2 (&port->lock){-.-.}-{2:2}: __raw_spin_lock_irqsave     include/linux/spinlock_api_smp.h:110 [inline] _raw_spin_lock_irqsave+0x35/0x50     kernel/locking/spinlock.c:159 tty_port_tty_get drivers/tty/tty_port.c:288 [inline] <-- lock(&port->lock);
    tty_port_default_wakeup+0x1d/0xb0 drivers/tty/tty_port.c:47 serial8250_tx_chars+0x530/0xa80     drivers/tty/serial/8250/8250_port.c:1767 serial8250_handle_irq.part.0+0x31f/0x3d0     drivers/tty/serial/8250/8250_port.c:1854 serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1827     [inline] <-- lock(&port_lock_key); serial8250_default_handle_irq+0xb2/0x220     drivers/tty/serial/8250/8250_port.c:1870 serial8250_interrupt+0xfd/0x200     drivers/tty/serial/8250/8250_core.c:126 __handle_irq_event_percpu+0x109/0xa50 kernel/irq/handle.c:156     [...] -> #1 (&port_lock_key){-.-.}-{2:2}: __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110     [inline] _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159     serial8250_console_write+0x184/0xa40 drivers/tty/serial/8250/8250_port.c:3198 <-- lock(&port_lock_key);
    call_console_drivers kernel/printk/printk.c:1819 [inline] console_unlock+0x8cb/0xd00     kernel/printk/printk.c:2504 vprintk_emit+0x1b5/0x470 kernel/printk/printk.c:2024 <-- lock(console_owner);
    vprintk_func+0x8d/0x250 kernel/printk/printk_safe.c:394 printk+0xba/0xed kernel/printk/printk.c:2084     register_console+0x8b3/0xc10 kernel/printk/printk.c:2829 univ8250_console_init+0x3a/0x46     drivers/tty/serial/8250/8250_core.c:681 console_init+0x49d/0x6d3 kernel/printk/printk.c:2915     start_kernel+0x5e9/0x879 init/main.c:713 secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:241 ->     #0 (console_owner){....}-{0:0}: [...] lock_acquire+0x127/0x340 kernel/locking/lockdep.c:4734     console_trylock_spinning kernel/printk/printk.c:1773 ---truncated--- (CVE-2022-49441)

  - In the Linux kernel, the following vulnerability has been resolved: list: fix a data-race around     ep->rdllist ep_poll() first calls ep_events_available() with no lock held and checks if ep->rdllist is     empty by list_empty_careful(), which reads rdllist->prev. Thus all accesses to it need some protection to     avoid store/load-tearing. Note INIT_LIST_HEAD_RCU() already has the annotation for both prev and next.
    Commit bf3b9f6372c4 (epoll: Add busy poll support to epoll with socket fds.) added the first lockless     ep_events_available(), and commit c5a282e9635e (fs/epoll: reduce the scope of wq lock in epoll_wait())     made some ep_events_available() calls lockless and added single call under a lock, finally commit     e59d3c64cba6 (epoll: eliminate unnecessary lock for zero timeout) made the last ep_events_available()     lockless. BUG: KCSAN: data-race in do_epoll_wait / do_epoll_wait write to 0xffff88810480c7d8 of 8 bytes by     task 1802 on cpu 0: INIT_LIST_HEAD include/linux/list.h:38 [inline] list_splice_init     include/linux/list.h:492 [inline] ep_start_scan fs/eventpoll.c:622 [inline] ep_send_events     fs/eventpoll.c:1656 [inline] ep_poll fs/eventpoll.c:1806 [inline] do_epoll_wait+0x4eb/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae read to 0xffff88810480c7d8 of 8 bytes     by task 1799 on cpu 1: list_empty_careful include/linux/list.h:329 [inline] ep_events_available     fs/eventpoll.c:381 [inline] ep_poll fs/eventpoll.c:1797 [inline] do_epoll_wait+0x279/0xf40     fs/eventpoll.c:2234 do_epoll_pwait fs/eventpoll.c:2268 [inline] __do_sys_epoll_pwait fs/eventpoll.c:2281     [inline] __se_sys_epoll_pwait+0x12b/0x240 fs/eventpoll.c:2275 __x64_sys_epoll_pwait+0x74/0x80     fs/eventpoll.c:2275 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x44/0xd0     arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x44/0xae value changed: 0xffff88810480c7d0 ->     0xffff888103c15098 Reported by Kernel Concurrency Sanitizer on: CPU: 1 PID: 1799 Comm: syz-fuzzer Tainted:
    G W 5.17.0-rc7-syzkaller-dirty #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS     Google 01/01/2011 (CVE-2022-49443)

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 dla-4671 advisory.

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4671-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     July 05, 2026                                 https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux-6.1     Version        : 6.1.176-1~deb11u1     CVE ID         : CVE-2023-53292 CVE-2023-53989 CVE-2023-54125 CVE-2023-54271                      CVE-2023-54322 CVE-2024-27012 CVE-2024-36922 CVE-2024-53221                      CVE-2024-56657 CVE-2025-10263 CVE-2025-21739 CVE-2025-21863                      CVE-2025-22105 CVE-2025-37864 CVE-2025-38584 CVE-2025-38627                      CVE-2025-38710 CVE-2025-39997 CVE-2025-40347 CVE-2025-68201                      CVE-2025-68315 CVE-2025-68823 CVE-2026-23066 CVE-2026-23255                      CVE-2026-23310 CVE-2026-23389 CVE-2026-23399 CVE-2026-23442                      CVE-2026-23444 CVE-2026-23468 CVE-2026-31407 CVE-2026-31449                      CVE-2026-31488 CVE-2026-31489 CVE-2026-31500 CVE-2026-31532                      CVE-2026-31576 CVE-2026-31577 CVE-2026-31578 CVE-2026-31580                      CVE-2026-31581 CVE-2026-31583 CVE-2026-31585 CVE-2026-31586                      CVE-2026-31587 CVE-2026-31588 CVE-2026-31590 CVE-2026-31594                      CVE-2026-31595 CVE-2026-31596 CVE-2026-31597 CVE-2026-31598                      CVE-2026-31599 CVE-2026-31602 CVE-2026-31603 CVE-2026-31605                      CVE-2026-31607 CVE-2026-31611 CVE-2026-31612 CVE-2026-31613                      CVE-2026-31615 CVE-2026-31616 CVE-2026-31617 CVE-2026-31618                      CVE-2026-31619 CVE-2026-31622 CVE-2026-31623 CVE-2026-31624                      CVE-2026-31625 CVE-2026-31626 CVE-2026-31627 CVE-2026-31629                      CVE-2026-31630 CVE-2026-31637 CVE-2026-31642 CVE-2026-31673                      CVE-2026-31676 CVE-2026-31681 CVE-2026-31684 CVE-2026-31685                      CVE-2026-31686 CVE-2026-31696 CVE-2026-31697 CVE-2026-31698                      CVE-2026-31699 CVE-2026-31700 CVE-2026-31701 CVE-2026-31702                      CVE-2026-31704 CVE-2026-31705 CVE-2026-31708 CVE-2026-31709                      CVE-2026-31711 CVE-2026-31712 CVE-2026-31715 CVE-2026-31716                      CVE-2026-43052 CVE-2026-43058 CVE-2026-43064 CVE-2026-43071                      CVE-2026-43072 CVE-2026-43075 CVE-2026-43076 CVE-2026-43079                      CVE-2026-43080 CVE-2026-43085 CVE-2026-43089 CVE-2026-43093                      CVE-2026-43094 CVE-2026-43098 CVE-2026-43099 CVE-2026-43103                      CVE-2026-43104 CVE-2026-43105 CVE-2026-43110 CVE-2026-43111                      CVE-2026-43112 CVE-2026-43113 CVE-2026-43114 CVE-2026-43116                      CVE-2026-43117 CVE-2026-43219 CVE-2026-43303 CVE-2026-43350                      CVE-2026-43421 CVE-2026-43492 CVE-2026-43493 CVE-2026-43494                      CVE-2026-43495 CVE-2026-43496 CVE-2026-43497 CVE-2026-43499                      CVE-2026-43501 CVE-2026-43502 CVE-2026-45834 CVE-2026-45835                      CVE-2026-45836 CVE-2026-45838 CVE-2026-45839 CVE-2026-45840                      CVE-2026-45841 CVE-2026-45842 CVE-2026-45843 CVE-2026-45844                      CVE-2026-45846 CVE-2026-45850 CVE-2026-45930 CVE-2026-45986                      CVE-2026-45987 CVE-2026-45991 CVE-2026-45994 CVE-2026-45996                      CVE-2026-45997 CVE-2026-45999 CVE-2026-46002 CVE-2026-46003                      CVE-2026-46004 CVE-2026-46005 CVE-2026-46006 CVE-2026-46009                      CVE-2026-46015 CVE-2026-46018 CVE-2026-46019 CVE-2026-46021                      CVE-2026-46022 CVE-2026-46023 CVE-2026-46024 CVE-2026-46026                      CVE-2026-46027 CVE-2026-46031 CVE-2026-46033 CVE-2026-46037                      CVE-2026-46038 CVE-2026-46040 CVE-2026-46043 CVE-2026-46044                      CVE-2026-46046 CVE-2026-46047 CVE-2026-46049 CVE-2026-46050                      CVE-2026-46051 CVE-2026-46052 CVE-2026-46053 CVE-2026-46056                      CVE-2026-46058 CVE-2026-46062 CVE-2026-46064 CVE-2026-46065                      CVE-2026-46069 CVE-2026-46070 CVE-2026-46072 CVE-2026-46075                      CVE-2026-46077 CVE-2026-46078 CVE-2026-46079 CVE-2026-46080                      CVE-2026-46082 CVE-2026-46083 CVE-2026-46086 CVE-2026-46088                      CVE-2026-46091 CVE-2026-46098 CVE-2026-46099 CVE-2026-46101                      CVE-2026-46102 CVE-2026-46103 CVE-2026-46107 CVE-2026-46108                      CVE-2026-46109 CVE-2026-46110 CVE-2026-46112 CVE-2026-46113                      CVE-2026-46116 CVE-2026-46119 CVE-2026-46120 CVE-2026-46122                      CVE-2026-46123 CVE-2026-46124 CVE-2026-46125 CVE-2026-46127                      CVE-2026-46128 CVE-2026-46129 CVE-2026-46132 CVE-2026-46133                      CVE-2026-46136 CVE-2026-46137 CVE-2026-46143 CVE-2026-46146                      CVE-2026-46149 CVE-2026-46150 CVE-2026-46151 CVE-2026-46159                      CVE-2026-46160 CVE-2026-46161 CVE-2026-46163 CVE-2026-46164                      CVE-2026-46165 CVE-2026-46167 CVE-2026-46168 CVE-2026-46169                      CVE-2026-46172 CVE-2026-46173 CVE-2026-46177 CVE-2026-46178                      CVE-2026-46179 CVE-2026-46180 CVE-2026-46184 CVE-2026-46185                      CVE-2026-46186 CVE-2026-46187 CVE-2026-46189 CVE-2026-46190                      CVE-2026-46191 CVE-2026-46193 CVE-2026-46195 CVE-2026-46196                      CVE-2026-46197 CVE-2026-46198 CVE-2026-46199 CVE-2026-46205                      CVE-2026-46206 CVE-2026-46208 CVE-2026-46209 CVE-2026-46212                      CVE-2026-46214 CVE-2026-46218 CVE-2026-46220 CVE-2026-46227                      CVE-2026-46230 CVE-2026-46231 CVE-2026-46233 CVE-2026-46234                      CVE-2026-46235 CVE-2026-46236 CVE-2026-46238 CVE-2026-46273                      CVE-2026-46275 CVE-2026-46276 CVE-2026-46280 CVE-2026-46285                      CVE-2026-46291 CVE-2026-46292 CVE-2026-46294 CVE-2026-46296                      CVE-2026-46299 CVE-2026-46301 CVE-2026-46303 CVE-2026-46304                      CVE-2026-46306 CVE-2026-46307 CVE-2026-46314 CVE-2026-46319                      CVE-2026-46320 CVE-2026-46321 CVE-2026-46322 CVE-2026-46323                      CVE-2026-46331 CVE-2026-52909 CVE-2026-52910 CVE-2026-52911                      CVE-2026-52912 CVE-2026-52913 CVE-2026-52914 CVE-2026-52915                      CVE-2026-52916 CVE-2026-52917 CVE-2026-52918 CVE-2026-52919                      CVE-2026-52920 CVE-2026-52921 CVE-2026-52922 CVE-2026-52923                      CVE-2026-52924 CVE-2026-52925 CVE-2026-52926 CVE-2026-52927                      CVE-2026-52929 CVE-2026-52930 CVE-2026-52931 CVE-2026-52933                      CVE-2026-52934 CVE-2026-52935 CVE-2026-52939 CVE-2026-52941                      CVE-2026-52942 CVE-2026-52943 CVE-2026-52946 CVE-2026-52947                      CVE-2026-52948 CVE-2026-52954 CVE-2026-52955 CVE-2026-52957                      CVE-2026-52958 CVE-2026-52962 CVE-2026-52963 CVE-2026-52967                      CVE-2026-52968 CVE-2026-52969 CVE-2026-52970 CVE-2026-52972                      CVE-2026-52974 CVE-2026-52975 CVE-2026-52977 CVE-2026-52981                      CVE-2026-52982 CVE-2026-52984 CVE-2026-52985 CVE-2026-52986                      CVE-2026-52989 CVE-2026-52992 CVE-2026-52993 CVE-2026-52995                      CVE-2026-52998 CVE-2026-52999 CVE-2026-53001 CVE-2026-53002                      CVE-2026-53003 CVE-2026-53004 CVE-2026-53006 CVE-2026-53011                      CVE-2026-53012 CVE-2026-53016 CVE-2026-53021 CVE-2026-53022                      CVE-2026-53023 CVE-2026-53033 CVE-2026-53034 CVE-2026-53035                      CVE-2026-53036 CVE-2026-53037 CVE-2026-53039 CVE-2026-53040                      CVE-2026-53041 CVE-2026-53043 CVE-2026-53045 CVE-2026-53046                      CVE-2026-53047 CVE-2026-53048 CVE-2026-53049 CVE-2026-53050                      CVE-2026-53052 CVE-2026-53056 CVE-2026-53059 CVE-2026-53060                      CVE-2026-53061 CVE-2026-53062 CVE-2026-53063 CVE-2026-53064                      CVE-2026-53065 CVE-2026-53066 CVE-2026-53068 CVE-2026-53069                      CVE-2026-53071 CVE-2026-53072 CVE-2026-53073 CVE-2026-53074                      CVE-2026-53075 CVE-2026-53077 CVE-2026-53080 CVE-2026-53082                      CVE-2026-53086 CVE-2026-53088 CVE-2026-53093 CVE-2026-53096                      CVE-2026-53111 CVE-2026-53112 CVE-2026-53128 CVE-2026-53130                      CVE-2026-53131 CVE-2026-53133 CVE-2026-53134 CVE-2026-53135                      CVE-2026-53136 CVE-2026-53137 CVE-2026-53146 CVE-2026-53147                      CVE-2026-53148 CVE-2026-53149 CVE-2026-53150 CVE-2026-53159                      CVE-2026-53160 CVE-2026-53161 CVE-2026-53168 CVE-2026-53176                      CVE-2026-53177 CVE-2026-53181 CVE-2026-53182 CVE-2026-53183                      CVE-2026-53184 CVE-2026-53186 CVE-2026-53189 CVE-2026-53194                      CVE-2026-53195 CVE-2026-53196 CVE-2026-53198 CVE-2026-53199                      CVE-2026-53207 CVE-2026-53208 CVE-2026-53209 CVE-2026-53212                      CVE-2026-53213 CVE-2026-53215 CVE-2026-53216 CVE-2026-53217                      CVE-2026-53218 CVE-2026-53219 CVE-2026-53221 CVE-2026-53223                      CVE-2026-53225 CVE-2026-53227 CVE-2026-53228 CVE-2026-53236                      CVE-2026-53238 CVE-2026-53239 CVE-2026-53242 CVE-2026-53245                      CVE-2026-53249 CVE-2026-53252 CVE-2026-53253 CVE-2026-53254                      CVE-2026-53255 CVE-2026-53256 CVE-2026-53263 CVE-2026-53264                      CVE-2026-53266 CVE-2026-53268 CVE-2026-53269 CVE-2026-53270                      CVE-2026-53273 CVE-2026-53274 CVE-2026-53275 CVE-2026-53279                      CVE-2026-53287 CVE-2026-53289 CVE-2026-53291 CVE-2026-53294                      CVE-2026-53295 CVE-2026-53296 CVE-2026-53303 CVE-2026-53304                      CVE-2026-53306 CVE-2026-53309 CVE-2026-53314 CVE-2026-53320                      CVE-2026-53329 CVE-2026-53331 CVE-2026-53337 CVE-2026-53339                      CVE-2026-53343 CVE-2026-53349 CVE-2026-53350 CVE-2026-53352                      CVE-2026-53354 CVE-2026-53355 CVE-2026-53356 CVE-2026-53357     Debian Bug     : 1130365 1119093

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

    For Debian 11 bullseye, these problems have been fixed in version     6.1.176-1~deb11u1.  This version additionally includes many more bug     fixes from stable updates 6.1.175 and 6.1.176.

    We recommend that you upgrade your linux-6.1 packages.

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

    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.

The remote Debian 13 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-6253 advisory.

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

    Package        : linux     CVE ID         : CVE-2025-38584 CVE-2026-23468 CVE-2026-31419 CVE-2026-31709                      CVE-2026-31715 CVE-2026-43284 CVE-2026-43500

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

    For the stable distribution (trixie), these problems have been fixed in     version 6.12.86-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.

ID	名前	製品	ファミリー	公開日	更新日	深刻度
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/15	high
352871	AlmaLinux 9.2 [TuxCare] Security Update: bpftool / kernel / kernel-abi-stablelists / kernel-core / etc Multiple Vulnerabilities (ALMALINUX9.2:CLSA-2026:1783791447)	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/10/1	medium
325283	Debian dla-4671 : linux-config-6.1 - security update	Nessus	Debian Local Security Checks	2026/7/6	2026/9/23	high
313288	Debian dsa-6253 : ata-modules-6.12.74+deb13+1-armmp-di - security update	Nessus	Debian Local Security Checks	2026/5/8	2026/5/27	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

検出

プラグインの検索

high

medium

high

high

high