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

  - 已修复 Linux 内核中的下列漏洞：ntfs: grow index root value before reparent header update ntfs_ir_reparent() moves the resident index root entries into an index block and leaves a small root stub containing the child VCN. That root stub can be larger than the existing resident value. For example, an empty root with value_length 48 has an index area of 32 bytes, while the large-index root stub needs index_length and allocated_size of 40 bytes. The current code publishes the larger index.index_length and index.allocated_size before resizing the resident value. If the resize returns
    -ENOSPC, the recovery path can call ntfs_inode_add_attrlist(), which looks attributes up again while the root header says allocated_size 40 but the resident value still only provides 32 bytes of index area.
    Lookup-time $INDEX_ROOT validation then correctly rejects that transient layout as corrupt. This reproduces as a generic/013 failure under qemu. In the failing run, the transient root had value_len=48, index_size=32, index_length=40, and allocated_size=40, and ntfsprogs-plus ntfsck reported Corrupt index root in MFT record 1177. When the root stub grows, resize the resident value before publishing the larger root header. If the resize fails, the old root remains valid for recovery lookups. Keep the existing header-before-resize ordering for shrink or same-size cases so the resident value never temporarily exposes an allocated_size beyond its bounds. (CVE-2026-72211)

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

Linux/Unix 主機上安裝了一個或多個受到弱點影響的套件，且供應商未提供可用的修補程式。

  - 已解決 Linux 核心中的下列弱點：ntfs: grow index root value before reparent header update ntfs_ir_reparent() moves the resident index root entries into an index block and leaves a small root stub containing the child VCN. That root stub can be larger than the existing resident value. For example, an empty root with value_length 48 has an index area of 32 bytes, while the large-index root stub needs index_length and allocated_size of 40 bytes. The current code publishes the larger index.index_length and index.allocated_size before resizing the resident value. If the resize returns
    -ENOSPC, the recovery path can call ntfs_inode_add_attrlist(), which looks attributes up again while the root header says allocated_size 40 but the resident value still only provides 32 bytes of index area.
    Lookup-time $INDEX_ROOT validation then correctly rejects that transient layout as corrupt. This reproduces as a generic/013 failure under qemu. In the failing run, the transient root had value_len=48, index_size=32, index_length=40, and allocated_size=40, and ntfsprogs-plus ntfsck reported Corrupt index root in MFT record 1177. When the root stub grows, resize the resident value before publishing the larger root header. If the resize fails, the old root remains valid for recovery lookups. Keep the existing header-before-resize ordering for shrink or same-size cases so the resident value never temporarily exposes an allocated_size beyond its bounds. (CVE-2026-72211)

請注意，Nessus 依賴供應商報告的套件存在。

Linux/Unix ホストには、ベンダーが提供するパッチが利用できない脆弱性の影響を受ける複数のパッケージがインストールされています。

  - Linux カーネルでは、以下の脆弱性が解決されています: ntfs: grow index root value before reparent header update ntfs_ir_reparent() moves the resident index root entries into an index block and leaves a small root stub containing the child VCN. That root stub can be larger than the existing resident value. For example, an empty root with value_length 48 has an index area of 32 bytes, while the large-index root stub needs index_length and allocated_size of 40 bytes. The current code publishes the larger index.index_length and index.allocated_size before resizing the resident value. If the resize returns
    -ENOSPC, the recovery path can call ntfs_inode_add_attrlist(), which looks attributes up again while the root header says allocated_size 40 but the resident value still only provides 32 bytes of index area.
    Lookup-time $INDEX_ROOT validation then correctly rejects that transient layout as corrupt. This reproduces as a generic/013 failure under qemu. In the failing run, the transient root had value_len=48, index_size=32, index_length=40, and allocated_size=40, and ntfsprogs-plus ntfsck reported Corrupt index root in MFT record 1177. When the root stub grows, resize the resident value before publishing the larger root header. If the resize fails, the old root remains valid for recovery lookups. Keep the existing header-before-resize ordering for shrink or same-size cases so the resident value never temporarily exposes an allocated_size beyond its bounds. (CVE-2026-72211)

Nessus は、ベンダーによって報告されたパッケージの存在に依存していることに注意してください。

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - In the Linux kernel, the following vulnerability has been resolved: ntfs: grow index root value before     reparent header update ntfs_ir_reparent() moves the resident index root entries into an index block and     leaves a small root stub containing the child VCN. That root stub can be larger than the existing resident     value. For example, an empty root with value_length 48 has an index area of 32 bytes, while the large-     index root stub needs index_length and allocated_size of 40 bytes. The current code publishes the larger     index.index_length and index.allocated_size before resizing the resident value. If the resize returns
    -ENOSPC, the recovery path can call ntfs_inode_add_attrlist(), which looks attributes up again while the     root header says allocated_size 40 but the resident value still only provides 32 bytes of index area.
    Lookup-time $INDEX_ROOT validation then correctly rejects that transient layout as corrupt. This     reproduces as a generic/013 failure under qemu. In the failing run, the transient root had value_len=48,     index_size=32, index_length=40, and allocated_size=40, and ntfsprogs-plus ntfsck reported Corrupt index     root in MFT record 1177. When the root stub grows, resize the resident value before publishing the larger     root header. If the resize fails, the old root remains valid for recovery lookups. Keep the existing     header-before-resize ordering for shrink or same-size cases so the resident value never temporarily     exposes an allocated_size beyond its bounds. (CVE-2026-72211)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
335713	Linux Distros 未修补的漏洞：CVE-2026-72211	Nessus	Misc.	2026/8/15	2026/8/24	critical
335713	Linux Distros 未修補弱點：CVE-2026-72211	Nessus	Misc.	2026/8/15	2026/8/24	critical
335713	Linux Distros のパッチ未適用の脆弱性: CVE-2026-72211	Nessus	Misc.	2026/8/15	2026/8/24	critical
335713	Linux Distros Unpatched Vulnerability : CVE-2026-72211	Nessus	Misc.	2026/8/15	2026/8/24	critical

检测

插件搜索

critical

critical

critical

critical