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

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

    程序包：linux 版本：6.1.176-1 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 缺陷：1130365 1119093

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

    对于 Debian 12 bookworm，这些问题已在版本 6.1.176-1中修复。此版本还包括来自稳定更新6.1.1756.1.176和 的更多缺陷补丁。

    建议您升级 linux 程序包。

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

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

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

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

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

  - blk-cgroup修复由于在 init blk-iocost 之前安装 blkg_policy_data 而造成的空取消引用有时会造成以下崩溃缺陷内核空指针取消引用地址00000000000000e0 ... RIP
    0010:_raw_spin_lock+0x17/0x30 代码 be 01 02 00 00 e8 79 38 39 ff 31 d2 89 d0 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 65 ff 05 48 d0 34 701 001 001 34 701 301 001 34 7e b9 <f0> c0  0f b1 0f 75 02 5d c3 89 c6 e8 ea 04 00 00 5d c3 0f 1f 84 00 00 RSP: 0018:ffffc900023b3d40 EFLAGS: 00010046 RAX: 0000000000000000 RBX: 00000000000000e0 RCX: 0000000000000001 RDX: ffffc900023b3d20 RSI: ffffc900023b3cf0 RDI: 00000000000000e0 RBP
     R08ffffc900023b3d40  : ffffc900023b3c10 R09: 0000000000000003 R10: 0000000000000064 R11: 000000000000000a R12: ffff888102337000 R13: fffffffffffffff2 R14: ffff88810af408c8 R15: ffff8881070c3600 FS:
    00007faaaf364fc0(0000) GS:ffff88842fdc0000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0:
    0000000080050033 CR2: 00000000000000e0 CR3: 00000001097b1000 CR4: 0000000000350ea0 Call Trace: <TASK> ioc_weight_write+0x13d/0x410 cgroup_file_write+0x7a/0x130 kernfs_fop_write_iter+0xf5/0x170 vfs_write+0x298/0x370 ksys_write+0x5f/0xb0 __x64_sys_write+0x1b/0x20 do_syscall_64+0x3d/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0 发生这种情况的原因是 iocg->ioc 为空。该字段由 ioc_pd_init() 初始化且从未清除。NULL 取消引用是因为 blkcg_activate_policy() 在初始化 blkg_policy_data 之前对其进行安装造成的。 blkcg_activate_policy() 进行以下操作1. 为所有现有的 blkg 分配 pd 并将其安装在 blkg->pd[] 中。 2. 初始化所有 pd。 3. 使所有 pd 联机。
    blkcg_activate_policy() 仅获取 queue_lock且可能释放并重新获取锁定因为分配可能需要休眠。 ioc_weight_write() 获取 blkcg->lock 并迭代其所有 blkg。二者会争用如果 ioc_weight_write() 在 #1 期间或 #1 和 #2之间运行可能遇到未初始化的 pd从而导致崩溃。使用以下脚本可重现崩溃问题 #!/bin/bash echo +io > /sys/fs/cgroup/cgroup.subtree_control systemd-run --unit touch-sda --scope dd if=/dev/sda of=/ dev/null bs=1M count=1 iflag=direct echo 100 > /sys/fs/cgroup/system.slice/io.weight bash -c echo '8:0 enable=1' > /sys/fs/cgroup/io.cost应用了以下修补程序的 .qos & sleep .2 echo 100 > /sys/fs/cgroup/system.slice/io.weight: > diff --git a/block/blk-cgroup.cb/block/blk-cgroup.c > 索引 fc49be622e05..38d671d5e10c 100644 > --- a/block/blk-cgroup.c > +++ b/block/blk-cgroup.c > @@ -1553,6 +1553,12 @@ int blkcg_activate_policy(struct gendisk *disk, const struct blkcg_policy *pol) > pd->online = false; > } > > + if (system_state == SYSTEM_RUNNING) { > + spin_unlock_irq(&q->queue_lock); > + ssleep(1); > + spin_lock_irq(&q->queue_lock); > + } > + > /* all aligned, init in the same order */ > if (pol->pd_init_fn) > list_for_each_entry_reverse(blkg, &q->blkg_list, q_node) 我没有看到为什么所有 pd一起分配、初始化和上线。唯一的排序要求是父 blkg 在子区块之前初始化和在线这是通过遍历顺序保证的。我们通过为每个 blkg 分配、初始化 pd 并使其联机并在初始化和联机时保持 blkcg->lock来修复此缺陷。这可确保安装的 blkg 始终经过完全初始化和在线删除争用窗口。 (CVE-2023-54271)

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

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

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

    程序包：linux-6.1 版本：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 错误：1130365 1119093

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

    对于 Debian 11 bullseye，这些问题已在 6.1.176-1~deb11u1 版本中修复。此版本还包括来自稳定更新6.1.1756.1.176和 的更多缺陷补丁。

    建议您升级 linux-6.1 程序包。

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

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

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

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

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

  - 已修复 Linux 内核中的下列漏洞：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)

  - 在 Linux 内核的 TeleTYpe 子系统中发现越界读取缺陷。在 flush_to_ldisc 函数中存在内存泄漏时，用户使用 ioctls TIOCSPTLCK 和 TIOCGPTPEER 以及 TIOCSTI 和 TCXONC 触发争用条件时会发生此问题。此缺陷会让本地用户导致系统崩溃或从内存读取未经授权的随机数据。 (CVE-2022-1462)

  - 已修复 Linux 内核中的下列漏洞：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)

  - 已修复 Linux 内核中的下列漏洞：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)

  - 已修复 Linux 内核中的下列漏洞：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)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
325059	Debian dla-4665：affs-modules-6.1.0-48-4kc-malta-di - 安全更新	Nessus	Debian Local Security Checks	2026/7/3	2026/9/23	high
280714	Linux Distros 未修补的漏洞：CVE-2023-54271	Nessus	Misc.	2025/12/30	2026/10/6	medium
325283	Debian DLA-4671：linux-config-6.1 - 安全更新	Nessus	Debian Local Security Checks	2026/7/6	2026/9/23	high
352871	AlmaLinux 9.2 [TuxCare] 安全更新：bpftool / kernel / kernel-abi-stablelists / kernel-core / 等多个漏洞（ALMALINUX9.2：CLSA-2026：1783791447）	Nessus	Alma Linux Local Security Checks	2026/9/30	2026/10/1	medium

检测

插件搜索

high

medium

high

medium