Rocky Linux 9.6 主机上存在安装的程序包，该程序包受到 TuxCare ALMALINUX9.6：CLSA-2026：1 1787305050公告中提及的多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped.
    Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet have session->tunnel set. Add a check for this case. (CVE-2024-49940)

  - 已修复 Linux 内核中的下列漏洞：mm/thp: fix deferred split unqueue naming and locking Recent changes are putting more pressure on THP deferred split queues: under load revealing long-standing races, causing list_del corruptions, Bad page states and worse (I keep BUGs in both of those, so usually don't get to see how badly they end up without). The relevant recent changes being 6.8's mTHP, 6.10's mTHP swapout, and 6.12's mTHP swapin, improved swap allocation, and underused THP splitting. Before fixing locking: rename misleading folio_undo_large_rmappable(), which does not undo large_rmappable, to folio_unqueue_deferred_split(), which is what it does. But that and its out-of-line
    __callee are mm internals of very limited usability: add comment and WARN_ON_ONCEs to check usage; and return a bool to say if a deferred split was unqueued, which can then be used in WARN_ON_ONCEs around safety checks (sparing callers the arcane conditionals in __folio_unqueue_deferred_split()). Just omit the folio_unqueue_deferred_split() from free_unref_folios(), all of whose callers now call it beforehand (and if any forget then bad_page() will tell) - except for its caller put_pages_list(), which itself no longer has any callers (and will be deleted separately). Swapout: mem_cgroup_swapout() has been resetting folio->memcg_data 0 without checking and unqueueing a THP folio from deferred split list; which is unfortunate, since the split_queue_lock depends on the memcg (when memcg is enabled); so swapout has been unqueueing such THPs later, when freeing the folio, using the pgdat's lock instead: potentially corrupting the memcg's list. __remove_mapping() has frozen refcount to 0 here, so no problem with calling folio_unqueue_deferred_split() before resetting memcg_data. That goes back to 5.4 commit 87eaceb3faa5 (mm: thp: make deferred split shrinker memcg aware): which included a check on swapcache before adding to deferred queue, but no check on deferred queue before adding THP to swapcache. That worked fine with the usual sequence of events in reclaim (though there were a couple of rare ways in which a THP on deferred queue could have been swapped out), but 6.12 commit dafff3f4c850 (mm: split underused THPs) avoids splitting underused THPs in reclaim, which makes swapcache THPs on deferred queue commonplace. Keep the check on swapcache before adding to deferred queue? Yes: it is no longer essential, but preserves the existing behaviour, and is likely to be a worthwhile optimization (vmstat showed much more traffic on the queue under swapping load if the check was removed); update its comment. Memcg-v1 move (deprecated):
    mem_cgroup_move_account() has been changing folio->memcg_data without checking and unqueueing a THP folio from the deferred list, sometimes corrupting from memcg's list, like swapout. Refcount is non-zero here, so folio_unqueue_deferred_split() can only be used in a WARN_ON_ONCE to validate the fix, which must be done earlier: mem_cgroup_move_charge_pte_range() first try to split the THP (splitting of course unqueues), or skip it if that fails. Not ideal, but moving charge has been requested, and khugepaged should repair the THP later: nobody wants new custom unqueueing code just for this deprecated case. The 87eaceb3faa5 commit did have the code to move from one deferred list to another (but was not conscious of its unsafety while refcount non-0); but that was removed by 5.6 commit fac0516b5534 (mm: thp: don't need care deferred split queue in memcg charge move path), which argued that the existence of a PMD mapping guarantees that the THP cannot be on a deferred list. As above, false in rare cases, and now commonly false. Backport to 6.11 should be straightforward. Earlier backports must take care that other
    _deferred_list fixes and dependencies are included. There is not a strong case for backports, but they can fix cornercases. (CVE-2024-53079)

  - 已修复 Linux 内核中的下列漏洞：io_uring/kbuf: reallocate buf lists on upgrade IORING_REGISTER_PBUF_RING can reuse an old struct io_buffer_list if it was created for legacy selected buffer and has been emptied. It violates the requirement that most of the field should stay stable after publish. Always reallocate it instead. (CVE-2025-21836)

  - 已修复 Linux 内核中的下列漏洞：RDMA/bnxt_re: Add sanity checks on rdev validity There is a possibility that ulp_irq_stop and ulp_irq_start callbacks will be called when the device is in detached state. This can cause a crash due to NULL pointer dereference as the rdev is already freed. (CVE-2025-21901)

  - 已修复 Linux 内核中的下列漏洞：cpufreq/amd-pstate: Add missing NULL ptr check in amd_pstate_update Check if policy is NULL before dereferencing it in amd_pstate_update.
    (CVE-2025-23137)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

AlmaLinux 9.2 主机上存在安装的程序包，该程序包受到 TuxCare ALMALINUX9.2：CLSA-2026：1789898700公告中提及的多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：ceph: fix possible deadlock when holding Fwb to get inline_data 1, mount with wsync. 2, create a file with O_RDWR, and the request was sent to mds.0: ceph_atomic_open()--> ceph_mdsc_do_request(openc) finish_open(file, dentry, ceph_open)--> ceph_open()--> ceph_init_file()--> ceph_init_file_info()--> ceph_uninline_data()--> { ... if (inline_version == 1 || /* initial version, no data */ inline_version == CEPH_INLINE_NONE) goto out_unlock; ... } The inline_version will be 1, which is the initial version for the new create file. And here the ci->i_inline_version will keep with 1, it's buggy. 3, buffer write to the file immediately:
    ceph_write_iter()--> ceph_get_caps(file, need=Fw, want=Fb, ...); generic_perform_write()--> a_ops->write_begin()--> ceph_write_begin()--> netfs_write_begin()--> netfs_begin_read()--> netfs_rreq_submit_slice()--> netfs_read_from_server()--> rreq->netfs_ops->issue_read()--> ceph_netfs_issue_read()--> { ... if (ci->i_inline_version != CEPH_INLINE_NONE && ceph_netfs_issue_op_inline(subreq)) return; ... } ceph_put_cap_refs(ci, Fwb); The ceph_netfs_issue_op_inline() will send a getattr(Fsr) request to mds.1. 4, then the mds.1 will request the rd lock for CInode::filelock from the auth mds.0, the mds.0 will do the CInode::filelock state transation from excl --> sync, but it need to revoke the Fxwb caps back from the clients. While the kernel client has aleady held the Fwb caps and waiting for the getattr(Fsr). It's deadlock! URL:
    https://tracker.ceph.com/issues/55377 (CVE-2022-49296)

  - 已修复 Linux 内核中的下列漏洞：tracing: Fix reading strings from synthetic events The follow commands caused a crash: # cd /sys/kernel/tracing # echo 's:open char file[]' > dynamic_events # echo 'hist:keys=common_pid:file=filename:onchange($file).trace(open,$file)' > events/syscalls/sys_enter_openat/trigger' # echo 1 > events/synthetic/open/enable BOOM! The problem is that the synthetic event field char file[] will read the value given to it as a string without any memory checks to make sure the address is valid. The above example will pass in the user space address and the sythetic event code will happily call strlen() on it and then strscpy() where either one will cause an oops when accessing user space addresses. Use the helper functions from trace_kprobe and trace_eprobe that can read strings safely (and actually succeed when the address is from user space and the memory is mapped in). Now the above can show: packagekitd-1721 [000] ...2. 104.597170: open:
    file=/usr/lib/rpm/fileattrs/cmake.attr in:imjournal-978 [006] ...2. 104.599642: open:
    file=/var/lib/rsyslog/imjournal.state.tmp packagekitd-1721 [000] ...2. 104.626308: open:
    file=/usr/lib/rpm/fileattrs/debuginfo.attr (CVE-2022-50255)

  - 已修复 Linux 内核中的下列漏洞：hwrng: core - Fix page fault dead lock on mmap-ed hwrng There is a dead-lock in the hwrng device read path. This triggers when the user reads from /dev/hwrng into memory also mmap-ed from /dev/hwrng. The resulting page fault triggers a recursive read which then dead-locks. Fix this by using a stack buffer when calling copy_to_user. (CVE-2023-52615)

  - 已修复 Linux 内核中的下列漏洞：fscache: Use wait_on_bit() to wait for the freeing of relinquished volume The freeing of relinquished volume will wake up the pending volume acquisition by using wake_up_bit(), however it is mismatched with wait_var_event() used in fscache_wait_on_volume_collision() and it will never wake up the waiter in the wait-queue because these two functions operate on different wait-queues. According to the implementation in fscache_wait_on_volume_collision(), if the wake-up of pending acquisition is delayed longer than 20 seconds (e.g., due to the delay of on-demand fd closing), the first wait_var_event_timeout() will timeout and the following wait_var_event() will hang forever as shown below: FS-Cache: Potential volume collision new=00000024 old=00000022 ...... INFO: task mount:1148 blocked for more than 122 seconds. Not tainted 6.1.0-rc6+ #1 task:mount state:D stack:0 pid:1148 ppid:1 Call Trace: <TASK> __schedule+0x2f6/0xb80 schedule+0x67/0xe0 fscache_wait_on_volume_collision.cold+0x80/0x82 __fscache_acquire_volume+0x40d/0x4e0 erofs_fscache_register_volume+0x51/0xe0 [erofs] erofs_fscache_register_fs+0x19c/0x240 [erofs] erofs_fc_fill_super+0x746/0xaf0 [erofs] vfs_get_super+0x7d/0x100 get_tree_nodev+0x16/0x20 erofs_fc_get_tree+0x20/0x30 [erofs] vfs_get_tree+0x24/0xb0 path_mount+0x2fa/0xa90 do_mount+0x7c/0xa0
    __x64_sys_mount+0x8b/0xe0 do_syscall_64+0x30/0x60 entry_SYSCALL_64_after_hwframe+0x46/0xb0 Considering that wake_up_bit() is more selective, so fix it by using wait_on_bit() instead of wait_var_event() to wait for the freeing of relinquished volume. In addition because waitqueue_active() is used in wake_up_bit() and clear_bit() doesn't imply any memory barrier, use clear_and_wake_up_bit() to add the missing memory barrier between cursor->flags and waitqueue_active(). (CVE-2023-52982)

  - 已修复 Linux 内核中的下列漏洞：Bluetooth: ISO: fix iso_conn related locking and validity issues sk->sk_state indicates whether iso_pi(sk)->conn is valid. Operations that check/update sk_state and access conn should hold lock_sock, otherwise they can race. The order of taking locks is hci_dev_lock > lock_sock > iso_conn_lock, which is how it is in connect/disconnect_cfm -> iso_conn_del -> iso_chan_del. Fix locking in iso_connect_cis/bis and sendmsg/recvmsg to take lock_sock around updating sk_state and conn. iso_conn_del must not occur during iso_connect_cis/bis, as it frees the iso_conn. Hold hdev->lock longer to prevent that. This should not reintroduce the issue fixed in commit 241f51931c35 (Bluetooth: ISO: Avoid circular locking dependency), since the we acquire locks in order.
    We retain the fix in iso_sock_connect to release lock_sock before iso_connect_* acquires hdev->lock.
    Similarly for commit 6a5ad251b7cd (Bluetooth: ISO: Fix possible circular locking dependency). We retain the fix in iso_conn_ready to not acquire iso_conn_lock before lock_sock. iso_conn_add shall return iso_conn with valid hcon. Make it so also when reusing an old CIS connection waiting for disconnect timeout (see __iso_sock_close where conn->hcon is set to NULL). Trace with iso_conn_del after iso_chan_add in iso_connect_cis: =============================================================== iso_sock_create:771:
    sock 00000000be9b69b7 iso_sock_init:693: sk 000000004dff667e iso_sock_bind:827: sk 000000004dff667e 70:1a:b8:98:ff:a2 type 1 iso_sock_setsockopt:1289: sk 000000004dff667e iso_sock_setsockopt:1289: sk 000000004dff667e iso_sock_setsockopt:1289: sk 000000004dff667e iso_sock_connect:875: sk 000000004dff667e iso_connect_cis:353: 70:1a:b8:98:ff:a2 -> 28:3d:c2:4a:7e:da hci_get_route:1199: 70:1a:b8:98:ff:a2 -> 28:3d:c2:4a:7e:da hci_conn_add:1005: hci0 dst 28:3d:c2:4a:7e:da iso_conn_add:140: hcon 000000007b65d182 conn 00000000daf8625e __iso_chan_add:214: conn 00000000daf8625e iso_connect_cfm:1700: hcon 000000007b65d182 bdaddr 28:3d:c2:4a:7e:da status 12 iso_conn_del:187: hcon 000000007b65d182 conn 00000000daf8625e, err 16 iso_sock_clear_timer:117: sock 000000004dff667e state 3 <Note: sk_state is BT_BOUND (3), so iso_connect_cis is still running at this point> iso_chan_del:153: sk 000000004dff667e, conn 00000000daf8625e, err 16 hci_conn_del:1151: hci0 hcon 000000007b65d182 handle 65535 hci_conn_unlink:1102: hci0: hcon 000000007b65d182 hci_chan_list_flush:2780: hcon 000000007b65d182 iso_sock_getsockopt:1376: sk 000000004dff667e iso_sock_getname:1070: sock 00000000be9b69b7, sk 000000004dff667e iso_sock_getname:1070: sock 00000000be9b69b7, sk 000000004dff667e iso_sock_getsockopt:1376: sk 000000004dff667e iso_sock_getname:1070: sock 00000000be9b69b7, sk 000000004dff667e iso_sock_getname:1070: sock 00000000be9b69b7, sk 000000004dff667e iso_sock_shutdown:1434:
    sock 00000000be9b69b7, sk 000000004dff667e, how 1 __iso_sock_close:632: sk 000000004dff667e state 5 socket 00000000be9b69b7 <Note: sk_state is BT_CONNECT (5), even though iso_chan_del sets BT_CLOSED (6). Only iso_connect_cis sets it to BT_CONNECT, so it must be that iso_chan_del occurred between iso_chan_add and end of iso_connect_cis.> BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 8000000006467067 P4D 8000000006467067 PUD 3f5f067 PMD 0 Oops: 0000 [#1] PREEMPT SMP PTI Hardware name:
    QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.2-1.fc38 04/01/2014 RIP: 0010:__iso_sock_close (net/bluetooth/iso.c:664) bluetooth =============================================================== Trace with iso_conn_del before iso_chan_add in iso_connect_cis:
    =============================================================== iso_connect_cis:356: 70:1a:b8:98:ff:a2 -> 28:3d:c2:4a:7e:da ... iso_conn_add:140: hcon 0000000093bc551f conn 00000000768ae504 hci_dev_put:1487: hci0 orig refcnt 21 hci_event_packet:7607: hci0: e ---truncated--- (CVE-2023-54164)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

Linux/Unix 主机中安装的一个或多个程序包受到一个漏洞影响，而供应商没有提供补丁程序。

  - drm/amdgpu/sdma6.0：将 BUG_ON（） 替换为 WARN_ON（） 这些情况下无需造成内核崩溃。
    （从提交 c17a508a7d652da3728f8bbc481bfffe96d65a87 中精选出的内容）（CVE-2026-68251）

请注意，Nessus 依赖供应商报告的程序包是否存在进行判断。

远程 Debian 12 主机上存在安装的程序包，该程序包受到 DLA-4745 公告中提及的多个漏洞的影响。

    ------------------------------------------------------------------------- Debian LTS 公告 DLA-4745-1 debian-lts@lists.debian.org https://www.debian.org/lts/security/Ben Hutchings 2026 年 8 月 18 日 https://wiki.debian.org/LTS-------------------------------------------------------------------------

    程序包：linux-6.12 版本：6.12.101-1~deb12u1 CVE ID： CVE-2025-40098 CVE-2026-45897 CVE-2026-45901 CVE-2026-53078 CVE-2026-53090 CVE-2026-64205 CVE-2026-64280 CVE-2026-64290 CVE-2026-64561 CVE-2026-64562 CVE-2026-64563 CVE-2026-64564 CVE-2026-64565 CVE-2026-64567 CVE-2026-64568 CVE-2026-64569 CVE-2026-64570 CVE-2026-64571 CVE-2026-64572 CVE-2026-64573 CVE-2026-64574 CVE-2026-64576 CVE-2026-64577 CVE-2026-64578 CVE-2026-64579 CVE-2026-64580 CVE-2026-64583 CVE-2026-64584 CVE-2026-68093 CVE-2026-68096 CVE-2026-68097 CVE-2026-68098 CVE-2026-68099 CVE-2026-68100 CVE-2026-68102 CVE-2026-68104 CVE-2026-68106 CVE-2026-68107 CVE-2026-68108 CVE-2026-68110 CVE-2026-68111 CVE-2026-68112 CVE-2026-68113 CVE-2026-68115 CVE-2026-68116 CVE-2026-68117 CVE-2026-68119 CVE-2026-68120 CVE-2026-68121 CVE-2026-68123 CVE-2026-68124 CVE-2026-68125 CVE-2026-68126 CVE-2026-68127 CVE-2026-68128 CVE-2026-68129 CVE-2026-68130 CVE-2026-68131 CVE-2026-68133 CVE-2026-68135 CVE-2026-68136 CVE-2026-68137 CVE-2026-68139 CVE-2026-68140 CVE-2026-68141 CVE-2026-68142 CVE-2026-68143 CVE-2026-68144 CVE-2026-68145 CVE-2026-68146 CVE-2026-68147 CVE-2026-68148 CVE-2026-68149 CVE-2026-68151 CVE-2026-68152 CVE-2026-68153 CVE-2026-68154 CVE-2026-68155 CVE-2026-68156 CVE-2026-68157 CVE-2026-68158 CVE-2026-68160 CVE-2026-68161 CVE-2026-68162 CVE-2026-68164 CVE-2026-68165 CVE-2026-68175 CVE-2026-68176 CVE-2026-68178 CVE-2026-68179 CVE-2026-68180 CVE-2026-68181 CVE-2026-68182 CVE-2026-68183 CVE-2026-68184 CVE-2026-68185 CVE-2026-68186 CVE-2026-68187 CVE-2026-68188 CVE-2026-68189 CVE-2026-68190 CVE-2026-68192 CVE-2026-68193 CVE-2026-68194 CVE-2026-68195 CVE-2026-68196 CVE-2026-68197 CVE-2026-68199 CVE-2026-68200 CVE-2026-68201 CVE-2026-68202 CVE-2026-68203 CVE-2026-68204 CVE-2026-68205 CVE-2026-68206 CVE-2026-68207 CVE-2026-68209 CVE-2026-68210 CVE-2026-68212 CVE-2026-68213 CVE-2026-68214 CVE-2026-68215 CVE-2026-68216 CVE-2026-68217 CVE-2026-68218 CVE-2026-68219 CVE-2026-68220 CVE-2026-68221 CVE-2026-68222 CVE-2026-68223 CVE-2026-68225 CVE-2026-68226 CVE-2026-68227 CVE-2026-68228 CVE-2026-68229 CVE-2026-68231 CVE-2026-68234 CVE-2026-68235 CVE-2026-68236 CVE-2026-68243 CVE-2026-68244 CVE-2026-68245 CVE-2026-68246 CVE-2026-68247 CVE-2026-68248 CVE-2026-68249 CVE-2026-68250 CVE-2026-68251 CVE-2026-68252 CVE-2026-68255 CVE-2026-68256 CVE-2026-68257 CVE-2026-68259 CVE-2026-68260 CVE-2026-68261 CVE-2026-68262 CVE-2026-68263 CVE-2026-68269 CVE-2026-68271 CVE-2026-68272 CVE-2026-68277 CVE-2026-68278 CVE-2026-68279 CVE-2026-68280 CVE-2026-68281 CVE-2026-68284 CVE-2026-68290 CVE-2026-68293 CVE-2026-68294 CVE-2026-68296 CVE-2026-68297 CVE-2026-68299 CVE-2026-68300 CVE-2026-68301 CVE-2026-68302 CVE-2026-68304 CVE-2026-68306 CVE-2026-68307 CVE-2026-68308 CVE-2026-68309 CVE-2026-68310 CVE-2026-68311 CVE-2026-68313 CVE-2026-68314 CVE-2026-68315 CVE-2026-68317 CVE-2026-68318 CVE-2026-68319 CVE-2026-68320 CVE-2026-68321 CVE-2026-68324 CVE-2026-68325 CVE-2026-68326 CVE-2026-68327 CVE-2026-68328 CVE-2026-68329 CVE-2026-68331 CVE-2026-68333 CVE-2026-68335 CVE-2026-68336 CVE-2026-68338 CVE-2026-68339 CVE-2026-68340 CVE-2026-68343 CVE-2026-68344 CVE-2026-68346 CVE-2026-68348 CVE-2026-68349 CVE-2026-68350 CVE-2026-68351 CVE-2026-68352 CVE-2026-68353 CVE-2026-68354 CVE-2026-68355 CVE-2026-68357 CVE-2026-68358 CVE-2026-68359 CVE-2026-68360 CVE-2026-68361 CVE-2026-68362 CVE-2026-68363 CVE-2026-68365 CVE-2026-68366 CVE-2026-68368 CVE-2026-68369 CVE-2026-68370 CVE-2026-68371 CVE-2026-68372 CVE-2026-68373 CVE-2026-68374 CVE-2026-68376 CVE-2026-68377 CVE-2026-68381 CVE-2026-68385 CVE-2026-68386 CVE-2026-68388 CVE-2026-68389 CVE-2026-68391 CVE-2026-68392 CVE-2026-68394 CVE-2026-68395 CVE-2026-68396 CVE-2026-68397 CVE-2026-68398 CVE-2026-68402 CVE-2026-68403 CVE-2026-68405 CVE-2026-68406 CVE-2026-68407 CVE-2026-68408 CVE-2026-68410 CVE-2026-68411 CVE-2026-68413 CVE-2026-68414 CVE-2026-68416 CVE-2026-68417 CVE-2026-68419 CVE-2026-68422 CVE-2026-68425 CVE-2026-68427 CVE-2026-68428 CVE-2026-68429 CVE-2026-68430 CVE-2026-68432 CVE-2026-68433 CVE-2026-68434 CVE-2026-68437 CVE-2026-68439 CVE-2026-68442 CVE-2026-68443 CVE-2026-68444 CVE-2026-68445 CVE-2026-68446 CVE-2026-68449 CVE-2026-68450 CVE-2026-72015 CVE-2026-72017 CVE-2026-72023 CVE-2026-72030 CVE-2026-72032 CVE-2026-72040 CVE-2026-72045 CVE-2026-72046 CVE-2026-72051 CVE-2026-72062 CVE-2026-72065 CVE-2026-72069 CVE-2026-72070 CVE-2026-72101 CVE-2026-72103 CVE-2026-72113 CVE-2026-72114 CVE-2026-72115 CVE-2026-72116 CVE-2026-72117 CVE-2026-72118 CVE-2026-72119 CVE-2026-72121 CVE-2026-72124 CVE-2026-72125 CVE-2026-72130 CVE-2026-72137 CVE-2026-72142 CVE-2026-72146 CVE-2026-72147 CVE-2026-72168 CVE-2026-72175 CVE-2026-72183 CVE-2026-72213 CVE-2026-72244 CVE-2026-72253 CVE-2026-72254 CVE-2026-72260 CVE-2026-72299 CVE-2026-72305 CVE-2026-72372 CVE-2026-74436 Debian 缺陷：1143721

    在 Linux 内核中发现多个可能导致权限升级、拒绝服务或信息泄漏的漏洞。此更新还包括来自稳定更新 6.12.101的更多缺陷补丁。

    对于 Debian 12 bookworm，这些问题已在 6.12.101-1~deb12u1 版本中修复。

    我们建议您升级 linux-6.12 程序包。

    有关 linux-6.12 的详细安全状态，请参阅其安全跟踪页面：
    https://security-tracker.debian.org/tracker/linux-6.12

    有关 Debian LTS 安全公告、如何将这些更新应用到系统以及常见问题解答的更多信息，请访问以下网址：https://wiki.debian.org/LTSAttachment:signature.ascDescription: PGP signature

Tenable 已直接从 Debian 安全公告中提取上述描述块。

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

AlmaLinux 9.6 主机上存在安装的程序包，该程序包受到 TuxCare ALMALINUX9.6：CLSA-2026：2026：1787305050公告中提及的多个漏洞的影响。

  - 已修复 Linux 内核中的下列漏洞：l2tp: prevent possible tunnel refcount underflow When a session is created, it sets a backpointer to its tunnel. When the session refcount drops to 0, l2tp_session_free drops the tunnel refcount if session->tunnel is non-NULL. However, session->tunnel is set in l2tp_session_create, before the tunnel refcount is incremented by l2tp_session_register, which leaves a small window where session->tunnel is non-NULL when the tunnel refcount hasn't been bumped.
    Moving the assignment to l2tp_session_register is trivial but l2tp_session_create calls l2tp_session_set_header_len which uses session->tunnel to get the tunnel's encap. Add an encap arg to l2tp_session_set_header_len to avoid using session->tunnel. If l2tpv3 sessions have colliding IDs, it is possible for l2tp_v3_session_get to race with l2tp_session_register and fetch a session which doesn't yet have session->tunnel set. Add a check for this case. (CVE-2024-49940)

  - 已修复 Linux 内核中的下列漏洞：mm/thp: fix deferred split unqueue naming and locking Recent changes are putting more pressure on THP deferred split queues: under load revealing long-standing races, causing list_del corruptions, Bad page states and worse (I keep BUGs in both of those, so usually don't get to see how badly they end up without). The relevant recent changes being 6.8's mTHP, 6.10's mTHP swapout, and 6.12's mTHP swapin, improved swap allocation, and underused THP splitting. Before fixing locking: rename misleading folio_undo_large_rmappable(), which does not undo large_rmappable, to folio_unqueue_deferred_split(), which is what it does. But that and its out-of-line
    __callee are mm internals of very limited usability: add comment and WARN_ON_ONCEs to check usage; and return a bool to say if a deferred split was unqueued, which can then be used in WARN_ON_ONCEs around safety checks (sparing callers the arcane conditionals in __folio_unqueue_deferred_split()). Just omit the folio_unqueue_deferred_split() from free_unref_folios(), all of whose callers now call it beforehand (and if any forget then bad_page() will tell) - except for its caller put_pages_list(), which itself no longer has any callers (and will be deleted separately). Swapout: mem_cgroup_swapout() has been resetting folio->memcg_data 0 without checking and unqueueing a THP folio from deferred split list; which is unfortunate, since the split_queue_lock depends on the memcg (when memcg is enabled); so swapout has been unqueueing such THPs later, when freeing the folio, using the pgdat's lock instead: potentially corrupting the memcg's list. __remove_mapping() has frozen refcount to 0 here, so no problem with calling folio_unqueue_deferred_split() before resetting memcg_data. That goes back to 5.4 commit 87eaceb3faa5 (mm: thp: make deferred split shrinker memcg aware): which included a check on swapcache before adding to deferred queue, but no check on deferred queue before adding THP to swapcache. That worked fine with the usual sequence of events in reclaim (though there were a couple of rare ways in which a THP on deferred queue could have been swapped out), but 6.12 commit dafff3f4c850 (mm: split underused THPs) avoids splitting underused THPs in reclaim, which makes swapcache THPs on deferred queue commonplace. Keep the check on swapcache before adding to deferred queue? Yes: it is no longer essential, but preserves the existing behaviour, and is likely to be a worthwhile optimization (vmstat showed much more traffic on the queue under swapping load if the check was removed); update its comment. Memcg-v1 move (deprecated):
    mem_cgroup_move_account() has been changing folio->memcg_data without checking and unqueueing a THP folio from the deferred list, sometimes corrupting from memcg's list, like swapout. Refcount is non-zero here, so folio_unqueue_deferred_split() can only be used in a WARN_ON_ONCE to validate the fix, which must be done earlier: mem_cgroup_move_charge_pte_range() first try to split the THP (splitting of course unqueues), or skip it if that fails. Not ideal, but moving charge has been requested, and khugepaged should repair the THP later: nobody wants new custom unqueueing code just for this deprecated case. The 87eaceb3faa5 commit did have the code to move from one deferred list to another (but was not conscious of its unsafety while refcount non-0); but that was removed by 5.6 commit fac0516b5534 (mm: thp: don't need care deferred split queue in memcg charge move path), which argued that the existence of a PMD mapping guarantees that the THP cannot be on a deferred list. As above, false in rare cases, and now commonly false. Backport to 6.11 should be straightforward. Earlier backports must take care that other
    _deferred_list fixes and dependencies are included. There is not a strong case for backports, but they can fix cornercases. (CVE-2024-53079)

  - 已修复 Linux 内核中的下列漏洞：io_uring/kbuf: reallocate buf lists on upgrade IORING_REGISTER_PBUF_RING can reuse an old struct io_buffer_list if it was created for legacy selected buffer and has been emptied. It violates the requirement that most of the field should stay stable after publish. Always reallocate it instead. (CVE-2025-21836)

  - 已修复 Linux 内核中的下列漏洞：RDMA/bnxt_re: Add sanity checks on rdev validity There is a possibility that ulp_irq_stop and ulp_irq_start callbacks will be called when the device is in detached state. This can cause a crash due to NULL pointer dereference as the rdev is already freed. (CVE-2025-21901)

  - 已修复 Linux 内核中的下列漏洞：cpufreq/amd-pstate: Add missing NULL ptr check in amd_pstate_update Check if policy is NULL before dereferencing it in amd_pstate_update.
    (CVE-2025-23137)

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

远程 Debian 12 主机上存在安装的程序包，该程序包受到 dla-4777 公告中提及的多个漏洞的影响。

    - ------------------------------------------------------------------------- Debian LTS 公告 DLA-4777-1 debian-lts@lists.debian.org https://www.debian.org/lts/security/Salvatore Bonaccorso 2026 年 9 月 8 日 https://wiki.debian.org/LTS
    - -------------------------------------------------------------------------

    程序包： linux 版本： 6.1.187-1 CVE ID： CVE-2023-53706 CVE-2023-54141 CVE-2023-54263 CVE-2024-38620 CVE-2024-46754 CVE-2024-58094 CVE-2024-58095 CVE-2025-22104 CVE-2025-38117 CVE-2025-38203 CVE-2025-38206 CVE-2025-38237 CVE-2025-38616 CVE-2025-39833 CVE-2025-39901 CVE-2025-39925 CVE-2025-40054 CVE-2025-40064 CVE-2025-40102 CVE-2025-40139 CVE-2025-40168 CVE-2025-40206 CVE-2025-40307 CVE-2025-68794 CVE-2026-23394 CVE-2026-31419 CVE-2026-43491 CVE-2026-45963 CVE-2026-46111 CVE-2026-46158 CVE-2026-46170 CVE-2026-46266 CVE-2026-53089 CVE-2026-53090 CVE-2026-53361 CVE-2026-64082 CVE-2026-64139 CVE-2026-64192 CVE-2026-64270 CVE-2026-64272 CVE-2026-64280 CVE-2026-64294 CVE-2026-64434 CVE-2026-64507 CVE-2026-64508 CVE-2026-64542 CVE-2026-64543 CVE-2026-64561 CVE-2026-64562 CVE-2026-64563 CVE-2026-64564 CVE-2026-64565 CVE-2026-64567 CVE-2026-64569 CVE-2026-64571 CVE-2026-64572 CVE-2026-64573 CVE-2026-64576 CVE-2026-64577 CVE-2026-64578 CVE-2026-64579 CVE-2026-64580 CVE-2026-64581 CVE-2026-64582 CVE-2026-64583 CVE-2026-64584 CVE-2026-64586 CVE-2026-64590 CVE-2026-68082 CVE-2026-68093 CVE-2026-68096 CVE-2026-68099 CVE-2026-68100 CVE-2026-68104 CVE-2026-68106 CVE-2026-68108 CVE-2026-68111 CVE-2026-68115 CVE-2026-68117 CVE-2026-68121 CVE-2026-68123 CVE-2026-68124 CVE-2026-68125 CVE-2026-68127 CVE-2026-68129 CVE-2026-68130 CVE-2026-68131 CVE-2026-68132 CVE-2026-68135 CVE-2026-68136 CVE-2026-68137 CVE-2026-68138 CVE-2026-68140 CVE-2026-68141 CVE-2026-68142 CVE-2026-68143 CVE-2026-68144 CVE-2026-68146 CVE-2026-68147 CVE-2026-68148 CVE-2026-68151 CVE-2026-68153 CVE-2026-68154 CVE-2026-68155 CVE-2026-68156 CVE-2026-68157 CVE-2026-68158 CVE-2026-68159 CVE-2026-68160 CVE-2026-68162 CVE-2026-68164 CVE-2026-68165 CVE-2026-68169 CVE-2026-68175 CVE-2026-68176 CVE-2026-68180 CVE-2026-68181 CVE-2026-68182 CVE-2026-68183 CVE-2026-68184 CVE-2026-68186 CVE-2026-68187 CVE-2026-68188 CVE-2026-68189 CVE-2026-68190 CVE-2026-68192 CVE-2026-68194 CVE-2026-68195 CVE-2026-68196 CVE-2026-68197 CVE-2026-68198 CVE-2026-68199 CVE-2026-68202 CVE-2026-68204 CVE-2026-68206 CVE-2026-68207 CVE-2026-68209 CVE-2026-68210 CVE-2026-68212 CVE-2026-68213 CVE-2026-68214 CVE-2026-68215 CVE-2026-68216 CVE-2026-68217 CVE-2026-68218 CVE-2026-68222 CVE-2026-68223 CVE-2026-68226 CVE-2026-68227 CVE-2026-68229 CVE-2026-68231 CVE-2026-68234 CVE-2026-68243 CVE-2026-68244 CVE-2026-68246 CVE-2026-68248 CVE-2026-68249 CVE-2026-68250 CVE-2026-68251 CVE-2026-68253 CVE-2026-68254 CVE-2026-68255 CVE-2026-68259 CVE-2026-68269 CVE-2026-68277 CVE-2026-68278 CVE-2026-68279 CVE-2026-68280 CVE-2026-68284 CVE-2026-68294 CVE-2026-68297 CVE-2026-68299 CVE-2026-68300 CVE-2026-68301 CVE-2026-68302 CVE-2026-68304 CVE-2026-68309 CVE-2026-68310 CVE-2026-68313 CVE-2026-68315 CVE-2026-68320 CVE-2026-68322 CVE-2026-68324 CVE-2026-68325 CVE-2026-68326 CVE-2026-68327 CVE-2026-68328 CVE-2026-68331 CVE-2026-68333 CVE-2026-68335 CVE-2026-68336 CVE-2026-68338 CVE-2026-68340 CVE-2026-68343 CVE-2026-68344 CVE-2026-68349 CVE-2026-68350 CVE-2026-68351 CVE-2026-68352 CVE-2026-68353 CVE-2026-68354 CVE-2026-68355 CVE-2026-68357 CVE-2026-68359 CVE-2026-68360 CVE-2026-68361 CVE-2026-68362 CVE-2026-68363 CVE-2026-68365 CVE-2026-68366 CVE-2026-68367 CVE-2026-68368 CVE-2026-68369 CVE-2026-68370 CVE-2026-68371 CVE-2026-68373 CVE-2026-68376 CVE-2026-68377 CVE-2026-68386 CVE-2026-68388 CVE-2026-68395 CVE-2026-68397 CVE-2026-68398 CVE-2026-68402 CVE-2026-68403 CVE-2026-68405 CVE-2026-68406 CVE-2026-68407 CVE-2026-68410 CVE-2026-68411 CVE-2026-68413 CVE-2026-68414 CVE-2026-68417 CVE-2026-68422 CVE-2026-68425 CVE-2026-68427 CVE-2026-68428 CVE-2026-68430 CVE-2026-68431 CVE-2026-68432 CVE-2026-68433 CVE-2026-68434 CVE-2026-68444 CVE-2026-68446 CVE-2026-68450 CVE-2026-68451 CVE-2026-68452 CVE-2026-68476 CVE-2026-68480 CVE-2026-72012 CVE-2026-72015 CVE-2026-72017 CVE-2026-72023 CVE-2026-72030 CVE-2026-72035 CVE-2026-72040 CVE-2026-72041 CVE-2026-72045 CVE-2026-72051 CVE-2026-72057 CVE-2026-72062 CVE-2026-72063 CVE-2026-72065 CVE-2026-72069 CVE-2026-72070 CVE-2026-72077 CVE-2026-72096 CVE-2026-72099 CVE-2026-72110 CVE-2026-72113 CVE-2026-72114 CVE-2026-72115 CVE-2026-72116 CVE-2026-72117 CVE-2026-72118 CVE-2026-72119 CVE-2026-72121 CVE-2026-72124 CVE-2026-72125 CVE-2026-72142 CVE-2026-72146 CVE-2026-72157 CVE-2026-72170 CVE-2026-72172 CVE-2026-72191 CVE-2026-72216 CVE-2026-72236 CVE-2026-72237 CVE-2026-72242 CVE-2026-72252 CVE-2026-72253 CVE-2026-72260 CVE-2026-72262 CVE-2026-72299 CVE-2026-72305 CVE-2026-72308 CVE-2026-72323 CVE-2026-72392 CVE-2026-74436 CVE-2026-74441 CVE-2026-74443 CVE-2026-74444 CVE-2026-74446 CVE-2026-74450 CVE-2026-74453 CVE-2026-74454 CVE-2026-74455 CVE-2026-74456 CVE-2026-74457 CVE-2026-74458 CVE-2026-74459 CVE-2026-74460 CVE-2026-74461 CVE-2026-74463 CVE-2026-74464 CVE-2026-74465 CVE-2026-74467 CVE-2026-74468 CVE-2026-74469 CVE-2026-74470 CVE-2026-74471 CVE-2026-74472 CVE-2026-74473 CVE-2026-74475 CVE-2026-74476 CVE-2026-74478 CVE-2026-74479 CVE-2026-74480 CVE-2026-74481 CVE-2026-74482 CVE-2026-74485 CVE-2026-74487 CVE-2026-74488 CVE-2026-74490 CVE-2026-74492 CVE-2026-74493 CVE-2026-74494 CVE-2026-74495 CVE-2026-74497 CVE-2026-74498 CVE-2026-74499 CVE-2026-74505 CVE-2026-74507 CVE-2026-74508 CVE-2026-74509 CVE-2026-74510 CVE-2026-74512 CVE-2026-74514 CVE-2026-74515 CVE-2026-74516 CVE-2026-74518 CVE-2026-74519 CVE-2026-74522 CVE-2026-74523 CVE-2026-74525 CVE-2026-74540 CVE-2026-74546 CVE-2026-74547 CVE-2026-74548 CVE-2026-74549 CVE-2026-74550 CVE-2026-74551 CVE-2026-74552 CVE-2026-74553 CVE-2026-74555 CVE-2026-74556 CVE-2026-74557 CVE-2026-74563 CVE-2026-74564 CVE-2026-74566 CVE-2026-74567 CVE-2026-74569 CVE-2026-74575 CVE-2026-74577 CVE-2026-74579 CVE-2026-74580 CVE-2026-74581 CVE-2026-74582 CVE-2026-74583 CVE-2026-74585 CVE-2026-74586 CVE-2026-74587 CVE-2026-74588 CVE-2026-74589 CVE-2026-74594 CVE-2026-74595 CVE-2026-74597 CVE-2026-74598 CVE-2026-74601 CVE-2026-74603 CVE-2026-74604 CVE-2026-74607 CVE-2026-74608 CVE-2026-74609 CVE-2026-74612 CVE-2026-74613 CVE-2026-74614 CVE-2026-74615 CVE-2026-74616 CVE-2026-74620 CVE-2026-74621 CVE-2026-74622 CVE-2026-74623 CVE-2026-74624 CVE-2026-74625 CVE-2026-74626 CVE-2026-74628 CVE-2026-74630 CVE-2026-74631 CVE-2026-74632 CVE-2026-74635 CVE-2026-74636 CVE-2026-74637 CVE-2026-74641 CVE-2026-74647 CVE-2026-74648 CVE-2026-74649 CVE-2026-74650 CVE-2026-74651 CVE-2026-74654 CVE-2026-74656 CVE-2026-74657 CVE-2026-74658 CVE-2026-74659 CVE-2026-74660 CVE-2026-74662 CVE-2026-74663 CVE-2026-74664 CVE-2026-74666 CVE-2026-74667 CVE-2026-74668 CVE-2026-74669 CVE-2026-74671 CVE-2026-74672 CVE-2026-74673 CVE-2026-74675 CVE-2026-74676 CVE-2026-74678 CVE-2026-74679 CVE-2026-74680 CVE-2026-74682 CVE-2026-74683 CVE-2026-74688 CVE-2026-74689 CVE-2026-74691 CVE-2026-74692 CVE-2026-74693 CVE-2026-74694 CVE-2026-74696 CVE-2026-74697 CVE-2026-74701 CVE-2026-74704 CVE-2026-74705 CVE-2026-74714 CVE-2026-74717 CVE-2026-74719 CVE-2026-74720 CVE-2026-74722 CVE-2026-74724 CVE-2026-74726 CVE-2026-74730 CVE-2026-74737 CVE-2026-74739 CVE-2026-74743 CVE-2026-74744 CVE-2026-74746 CVE-2026-74748 CVE-2026-80527 CVE-2026-80528 CVE-2026-80529 CVE-2026-80534 CVE-2026-80536 CVE-2026-80539 CVE-2026-80540 CVE-2026-80541 CVE-2026-80547 CVE-2026-80548 CVE-2026-80549 CVE-2026-80550 CVE-2026-80552 CVE-2026-80553 CVE-2026-80555 CVE-2026-80557 CVE-2026-80558 CVE-2026-80559 CVE-2026-80560 CVE-2026-80561 CVE-2026-80562 CVE-2026-80565 CVE-2026-80567 CVE-2026-80568 CVE-2026-80569 CVE-2026-80570 CVE-2026-80572 CVE-2026-80573 CVE-2026-80574 CVE-2026-80583 CVE-2026-80584 CVE-2026-80586 CVE-2026-80589 CVE-2026-80590 CVE-2026-80678 CVE-2026-80679 CVE-2026-80680 CVE-2026-80681 CVE-2026-80684 CVE-2026-80686 CVE-2026-80706 CVE-2026-80707 CVE-2026-80708 CVE-2026-80709 CVE-2026-80714 CVE-2026-80715 CVE-2026-80716 CVE-2026-80717 CVE-2026-80718 CVE-2026-80722 CVE-2026-80725 CVE-2026-80726 CVE-2026-80730 CVE-2026-80731 CVE-2026-80732 CVE-2026-80733 CVE-2026-80737 CVE-2026-80742 CVE-2026-80743 CVE-2026-80744 CVE-2026-80752 CVE-2026-80754 CVE-2026-80756 CVE-2026-80757 CVE-2026-80762 CVE-2026-80763 CVE-2026-80764 CVE-2026-80765 CVE-2026-80766 CVE-2026-80767 CVE-2026-80768 CVE-2026-80770 CVE-2026-80772 CVE-2026-80781 CVE-2026-80782 CVE-2026-80783 CVE-2026-80784 CVE-2026-80788 CVE-2026-80789 CVE-2026-80790 CVE-2026-80791 CVE-2026-80792 CVE-2026-80793 CVE-2026-80794 CVE-2026-80795 CVE-2026-80796 CVE-2026-80797 CVE-2026-80798 CVE-2026-80799 CVE-2026-80800 CVE-2026-80801 CVE-2026-80802 CVE-2026-80803 CVE-2026-80805 CVE-2026-80806 CVE-2026-80807 CVE-2026-80808 CVE-2026-80809 CVE-2026-80812 CVE-2026-80814 CVE-2026-80819 CVE-2026-80823 CVE-2026-80824 CVE-2026-80826 CVE-2026-80827 CVE-2026-80828 CVE-2026-80829 CVE-2026-80830 CVE-2026-80831 CVE-2026-80832 CVE-2026-80840 CVE-2026-80842 CVE-2026-80843 CVE-2026-80844 CVE-2026-80846 CVE-2026-80848 CVE-2026-80852 CVE-2026-80854 CVE-2026-80855 CVE-2026-80856 CVE-2026-80863 CVE-2026-80888 CVE-2026-80890 CVE-2026-80891 CVE-2026-80892 CVE-2026-80893 CVE-2026-80901 CVE-2026-80902 CVE-2026-80904 CVE-2026-80906 CVE-2026-80908 CVE-2026-80909 CVE-2026-80910 CVE-2026-80913

    在 Linux 内核中发现多个可能导致权限升级、拒绝服务或信息泄漏的漏洞。

    对于 Debian 12 bookworm，这些问题已在版本 6.1.187-1中修复。

    建议您升级 linux 程序包。

    如需了解 linux 的详细安全状态，请参阅其安全跟踪页面：
    https://security-tracker.debian.org/tracker/linux

    有关 Debian LTS 安全公告、如何将这些更新应用到系统以及常见问题解答的更多信息，请访问以下网址：https://wiki.debian.org/LTS

Tenable 已直接从 Debian 安全公告中提取上述描述块。

请注意，Nessus 尚未测试这些问题，而是只依据应用程序自我报告的版本号进行判断。

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
364137	Oracle Linux 10 / 9：Unbreakable Enterprise 内核 (ELSA-2026-500374)	Nessus	Oracle Linux Local Security Checks	2026/10/8	2026/10/8	high
343049	Oracle Linux 10 / 9：Unbreakable Enterprise 内核 (ELSA-2026-500248)	Nessus	Oracle Linux Local Security Checks	2026/9/4	2026/9/23	high
352240	Rocky Linux 9.6 [TuxCare] 安全更新：kernel / kernel-abi-stablelists / kernel-core / 等多个漏洞（ALMALINUX9.6：CLSA-2026：1787305050）	Nessus	Rocky Linux Local Security Checks	2026/9/30	2026/9/30	high
365463	Ubuntu 26.04 LTS：Linux 内核 (OEM) 漏洞 (USN-8889-1)	Nessus	Ubuntu Local Security Checks	2026/10/13	2026/10/13	medium
360912	AlmaLinux 9.2 [TuxCare] 安全更新：bpftool / kernel / kernel-abi-stablelists / kernel-core / 等多个漏洞（ALMALINUX9.2：CLSA-2026：1789898700）	Nessus	Alma Linux Local Security Checks	2026/10/1	2026/10/1	high
365768	Ubuntu 26.04 LTS：Linux kernel (Azure) 漏洞 (USN-8888-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
334336	Linux Distros 未修补的漏洞：CVE-2026-68251	Nessus	Misc.	2026/8/10	2026/10/30	medium
337079	Debian dla-4745：ata-modules-6.12.100+deb12-armmp-di - 安全更新	Nessus	Debian Local Security Checks	2026/8/18	2026/8/18	medium
352220	AlmaLinux 9.6 [TuxCare] 安全更新：kernel / kernel-abi-stablelists / kernel-core / 等多个漏洞（ALMALINUX9.6：CLSA-2026：1787305050）	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/9/30	high
365522	Ubuntu 24.04 LTS：Linux 内核漏洞 (USN-8917-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
365525	Ubuntu 24.04 LTS：Linux kernel (Azure) 漏洞 (USN-8918-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium
343851	Debian dla-4777：ata-modules-6.1.0-52-armmp-di - 安全更新	Nessus	Debian Local Security Checks	2026/9/8	2026/9/8	high
365767	Ubuntu 26.04 LTS：Linux 内核漏洞 (USN-8887-1)	Nessus	Ubuntu Local Security Checks	2026/10/14	2026/10/14	medium

检测

插件搜索

high

high

high

medium

high

medium

medium

medium

high

medium

medium

high

medium