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

  - ubifsubifs_releasepage移除 ubifs_assert(0) 以使此處理程序有效 ubifs 寫入頁面有兩種狀態 1. 已變更、私人 2. 非已變更、非私人 正常的處理程序無法前往 ubifs_releasepage()這表示有正在private but not dirty。Reproducer[1] 顯示下列處理程序可能會發生此問題 (可能與 [2] 有關)PA PB PC lock(page)[PA] ubifs_write_end attach_page_private // set Private __set_page_dirty_nobuffers // set Dirty unlock(page) write_cache_pages[PA ] lock(page) clear_page_dirty_for_io(page) // 清除 Dirty ubifs_writepage do_truncation[PB] truncate_setsize i_size_write(inode, newsize) // newsize = 0 i_size = i_size_read(inode) // i_size = 0 end_index = i_size >> PAGE_SHIFT if (page ->index > end_index) goto out // 跳出
    unlock(page) // Private Not Dirty generic_fadvise[PC] lock(page) invalidate_inode_page try_to_release_page ubifs_releasepage ubifs_assert(c, 0) // 錯誤宣告unlock(page) truncate_pagecache[PB] 則可能會出現下列宣告失敗UBIFS 錯誤 (ubi0:0 pid 1683)
    ubifs_assert_failed [ubifs]: UBIFS 宣告失敗0, in fs/ubifs/file.c:1513 UBIFS 警告 (ubi0:0 pid 1683)ubifs_ro_mode [ubifs]切換到唯讀模式錯誤 -22 CPU2 PID 1683 Commaa 未受污染的 5.16.0-rc5-00184-g0bca5994cacc-dirty #308 呼叫追踪 dump_stack+0x13/0x1b ubifs_ro_mode+0x54/0x60 [ubifs] ubifs_assert_failed+0x4b/0x80 [ubifs] ubifs_assert_failed+0x4b/0x80 [ubifs] ubifs_assert_failed+0x4b/0x80 [ubifs] ubifs_assert_failed+0x4b/0x80 [ubifs] ubifs_releasepage+0x67/0 ubifs] try_to_release_page+0x57/0xe0 invalidate_inode_page+0xfb/0x130 __invalidate_mapping_pages+0xb9/0x280 invalidate_mapping_pagevec+0x12/0x20 generic_fadvise+0x303/0x3c0 ksys_fadvise64_64+0x4c[]/0xb0 [1] https://bugzilla.kernel.org/show_bug.cgi?id=215373 [2]/0xb0 [1] https://linux-mtd.infradead.narkive.com/NQoBeT1u/patch-rfc-ubifs-fix-assert-failed-in-ubifs-set-page-dirty[2]/ 0xb0CVE-2023-53584[1 ]

請注意，Nessus 的判定取決於廠商所報告的套件是否存在。

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

  - ubifsubifs_releasepage删除 ubifs_assert(0) 使此进程有效 ubifs 写入页面有两种状态1. 脏、私有 2. 非脏、非私有 正常进程无法转至 ubifs_releasepage()即存在页面正在写入隐私但不脏。Re Producer [1] 表明此问题可能与 [2] 相关通过以下进程发生 PA PB PC lock(page)[PA] ubifs_write_end attach_page_private // set Private __set_page_dirty_nobuffers // set Dirty unlock(page) write_cache_pages[PA] ] lock(page) clear_page_dirty_for_io(page) // 清除脏 ubifs_writepage do_truncation[PB] truncate_setsize i_size_write(inode, newsize) // newsize = 0 i_size = i_size_read(inode) // i_size = 0 end_index = i_size >> PAGE_SHIFT if (page ->index > end_index) goto out // 跳出
    unlock(page) // 私有、非脏 generic_fadvise[PC] lock(page) invalidate_inode_page try_to_release_page ubifs_releasepage ubifs_assert(c, 0) // 错误的断言unlock(page) truncate_pagecache[PB] 然后我们可能得到以下 assertion failed: UBIFS 错误 (ubi0:0 pid 1683):
    ubifs_assert_failed [ubifs] UBIFS 断言失败fs/ubifs/file.c:1513 UBIFS 警告 (ubi0:0 pid 1683)ubifs_ro_mode [ubifs]切换至只读模式错误 -22 CPU2 PID 1683 Commaa Not tainted 5.16.0-rc5-00184-g0bca5994cacc-dirty #308 调用跟踪dump_stack+0x13/0x1b ubifs_ro_mode+0x54/0x60 [ubifs] ubifs_assert_failed+0x4b/0x80 [ubifs] ubifs_releasepage+0x67/0x1d0[ ubifs] try_to_release_page+0x57/0xe0 invalidate_inode_page+0xfb/0x130 __invalidate_mapping_pages+0xb9/0x280 invalidate_mapping_pagevec+0x12/0x20 generic_fadvise+0x303/0x3c0 ksys_fadvise64_64+0x4c/0xb0 [1] https://bugzilla.kernel.org/show_bug.cgi?id=215373 [2] https://linux-mtd.infradead.narkive.com/NQoBeT1u/patch-rfc-ubifs-fix-assert-failed-in-ubifs-set-page-dirty2CVE-2023-53584

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

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

  - ubifsubifs_releasepageこのプロセスを検証するために ubifs_assert(0) を削除します ページを書き込む ubifs には 2 つの状態があります 1. ダーティ、プライベート 2. ダーティではありません、プライベートではありません通常のプロセスは ubifs_releasepage() に移動できないため、ページが存在することを意味しますプライベートだがダーティではない。Reducer[1] は次のプロセスでこれが発生する可能性があることを示しています[2] に関連しているかもしれませんPA PB PC lock(page)[PA] ubifs_write_end attach_page_private // set Private __set_page_dirty_nobuffers // set Dirty unlock(page) write_cache_pages[PA ] lock(page) clear_page_dirty_for_io(page) // clear Dirty ubifs_writepage do_truncation[PB] truncate_setsize i_size_write(inode, newsize) // newsize = 0 i_size = i_size_read(inode) / / i_size = 0 end_index = i_size >> PAGE_SHIFT if (page) ->index > end_index) goto out // jump out
    unlock(page) // Private、Not Dirty generic_fadvise[PC] lock(page)validate_inode_page try_to_release_page ubifs_releasepage ubifs_assert(c, 0) // 不適切なアサーション! unlock(page) truncate_pagecache[PB] その後、以下のアサーションが失敗する可能性があります UBIFS エラーubi0:0 pid 1683
    ubifs_assert_failed [ubifs]UBIFS アサートが失敗しました0、 fs/ubifs/file.c:1513 UBIFS 警告bi0:0 pid 1683ubifs_ro_mode [ubifs]読み取り専用モードに切り替えました、エラー -22 CPU: 2 PID 1683 通信: aa 汚染されていない 5.16.0-rc5-00184-g0bca5994cacc-dirty #308 呼び出しトレースdump_stack+0x13/0x1b ubifs_ro_mode+0x54/0x60 [bifs] ubifs_assert_failed+0x4b/0x80 [ubifs] ubifs_release [x1067] [] [try_to_release_page+0x57/0xe0validate_inode_page+0xfb/0x130 __invalidate_mapping_pages+0xb9/0x280validate_mapping_pagevec+0x12/0x20 generic_fadvise+0x303/0x3c0 ksys_fadvise64_64+0x4c/0xb0 [ https://bugzilla.kernel.org/show_bug.cgi?id=215373 ]  [] https://linux-mtd.infradead.narkive.com/NQoBeT1u/patch-rfc-ubifs-fix-assert-failed-in-ubifs-set-page-dirtyCVE-2023-53584]

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-013823 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    ubifs: ubifs_releasepage: Remove ubifs_assert(0) to valid this process

    There are two states for ubifs writing pages:
    1. Dirty, Private     2. Not Dirty, Not Private

    The normal process cannot go to ubifs_releasepage() which means there     exists pages being private but not dirty. Reproducer[1] shows that it     could occur (which maybe related to [2]) with following process:

         PA                     PB                    PC     lock(page)[PA]     ubifs_write_end       attach_page_private         // set Private
      __set_page_dirty_nobuffers  // set Dirty     unlock(page)

    write_cache_pages[PA]       lock(page)       clear_page_dirty_for_io(page) // clear Dirty       ubifs_writepage

                            do_truncation[PB]                               truncate_setsize                                 i_size_write(inode, newsize) // newsize = 0

        i_size = i_size_read(inode) // i_size = 0         end_index = i_size >> PAGE_SHIFT         if (page->index > end_index)           goto out // jump     out:
    unlock(page)   // Private, Not Dirty

                                                    generic_fadvise[PC]                                                       lock(page)                                                       invalidate_inode_page                                                         try_to_release_page                                                           ubifs_releasepage                                                             ubifs_assert(c, 0)                                                             // bad assertion!                                                       unlock(page)                               truncate_pagecache[PB]

    Then we may get following assertion failed:
      UBIFS error (ubi0:0 pid 1683): ubifs_assert_failed [ubifs]:
      UBIFS assert failed: 0, in fs/ubifs/file.c:1513       UBIFS warning (ubi0:0 pid 1683): ubifs_ro_mode [ubifs]:
      switched to read-only mode, error -22       CPU: 2 PID: 1683 Comm: aa Not tainted 5.16.0-rc5-00184-g0bca5994cacc-dirty #308       Call Trace:
        dump_stack+0x13/0x1b         ubifs_ro_mode+0x54/0x60 [ubifs]         ubifs_assert_failed+0x4b/0x80 [ubifs]         ubifs_releasepage+0x67/0x1d0 [ubifs]         try_to_release_page+0x57/0xe0         invalidate_inode_page+0xfb/0x130
        __invalidate_mapping_pages+0xb9/0x280         invalidate_mapping_pagevec+0x12/0x20         generic_fadvise+0x303/0x3c0         ksys_fadvise64_64+0x4c/0xb0

    [1] https://bugzilla.kernel.org/show_bug.cgi?id=215373     [2] https://linux-mtd.infradead.narkive.com/NQoBeT1u/patch-rfc-ubifs-fix-assert-failed-in-ubifs-set-page-     dirty

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

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

The Unity Linux 20 host has a package installed that is affected by a vulnerability as referenced in the UTSA-2026-011124 advisory.

    In the Linux kernel, the following vulnerability has been resolved:

    ubifs: ubifs_releasepage: Remove ubifs_assert(0) to valid this process

    There are two states for ubifs writing pages:
    1. Dirty, Private     2. Not Dirty, Not Private

    The normal process cannot go to ubifs_releasepage() which means there     exists pages being private but not dirty. Reproducer[1] shows that it     could occur (which maybe related to [2]) with following process:

         PA                     PB                    PC     lock(page)[PA]     ubifs_write_end       attach_page_private         // set Private
      __set_page_dirty_nobuffers  // set Dirty     unlock(page)

    write_cache_pages[PA]       lock(page)       clear_page_dirty_for_io(page) // clear Dirty       ubifs_writepage

                            do_truncation[PB]                               truncate_setsize                                 i_size_write(inode, newsize) // newsize = 0

        i_size = i_size_read(inode) // i_size = 0         end_index = i_size >> PAGE_SHIFT         if (page->index > end_index)           goto out // jump     out:
    unlock(page)   // Private, Not Dirty

                                                    generic_fadvise[PC]                                                       lock(page)                                                       invalidate_inode_page                                                         try_to_release_page                                                           ubifs_releasepage                                                             ubifs_assert(c, 0)                                                             // bad assertion!                                                       unlock(page)                               truncate_pagecache[PB]

    Then we may get following assertion failed:
      UBIFS error (ubi0:0 pid 1683): ubifs_assert_failed [ubifs]:
      UBIFS assert failed: 0, in fs/ubifs/file.c:1513       UBIFS warning (ubi0:0 pid 1683): ubifs_ro_mode [ubifs]:
      switched to read-only mode, error -22       CPU: 2 PID: 1683 Comm: aa Not tainted 5.16.0-rc5-00184-g0bca5994cacc-dirty #308       Call Trace:
        dump_stack+0x13/0x1b         ubifs_ro_mode+0x54/0x60 [ubifs]         ubifs_assert_failed+0x4b/0x80 [ubifs]         ubifs_releasepage+0x67/0x1d0 [ubifs]         try_to_release_page+0x57/0xe0         invalidate_inode_page+0xfb/0x130
        __invalidate_mapping_pages+0xb9/0x280         invalidate_mapping_pagevec+0x12/0x20         generic_fadvise+0x303/0x3c0         ksys_fadvise64_64+0x4c/0xb0

    [1] https://bugzilla.kernel.org/show_bug.cgi?id=215373     [2] https://linux-mtd.infradead.narkive.com/NQoBeT1u/patch-rfc-ubifs-fix-assert-failed-in-ubifs-set-page-     dirty

Tenable has extracted the preceding description block directly from the Unity Linux security advisory.

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

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

  - ubifs: ubifs_releasepage: Remove ubifs_assert(0) to valid this process There are two states for ubifs     writing pages: 1. Dirty, Private 2. Not Dirty, Not Private The normal process cannot go to     ubifs_releasepage() which means there exists pages being private but not dirty. Reproducer[1] shows that     it could occur (which maybe related to [2]) with following process: PA PB PC lock(page)[PA]     ubifs_write_end attach_page_private // set Private __set_page_dirty_nobuffers // set Dirty unlock(page)     write_cache_pages[PA] lock(page) clear_page_dirty_for_io(page) // clear Dirty ubifs_writepage     do_truncation[PB] truncate_setsize i_size_write(inode, newsize) // newsize = 0 i_size = i_size_read(inode)     // i_size = 0 end_index = i_size >> PAGE_SHIFT if (page->index > end_index) goto out // jump out:
    unlock(page) // Private, Not Dirty generic_fadvise[PC] lock(page) invalidate_inode_page     try_to_release_page ubifs_releasepage ubifs_assert(c, 0) // bad assertion! unlock(page)     truncate_pagecache[PB] Then we may get following assertion failed: UBIFS error (ubi0:0 pid 1683):
    ubifs_assert_failed [ubifs]: UBIFS assert failed: 0, in fs/ubifs/file.c:1513 UBIFS warning (ubi0:0 pid     1683): ubifs_ro_mode [ubifs]: switched to read-only mode, error -22 CPU: 2 PID: 1683 Comm: aa Not tainted     5.16.0-rc5-00184-g0bca5994cacc-dirty #308 Call Trace: dump_stack+0x13/0x1b ubifs_ro_mode+0x54/0x60 [ubifs]     ubifs_assert_failed+0x4b/0x80 [ubifs] ubifs_releasepage+0x67/0x1d0 [ubifs] try_to_release_page+0x57/0xe0     invalidate_inode_page+0xfb/0x130 __invalidate_mapping_pages+0xb9/0x280     invalidate_mapping_pagevec+0x12/0x20 generic_fadvise+0x303/0x3c0 ksys_fadvise64_64+0x4c/0xb0 [1]     https://bugzilla.kernel.org/show_bug.cgi?id=215373 [2] https://linux-     mtd.infradead.narkive.com/NQoBeT1u/patch-rfc-ubifs-fix-assert-failed-in-ubifs-set-page-dirty     (CVE-2023-53584)

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
269425	Linux Distros 未修補的弱點：CVE-2023-53584	Nessus	Misc.	2025/10/8	2026/2/6	medium
269425	Linux Distros 未修补的漏洞：CVE-2023-53584	Nessus	Misc.	2025/10/8	2026/2/6	medium
269425	Linux Distros のパッチ未適用の脆弱性: CVE-2023-53584	Nessus	Misc.	2025/10/8	2026/2/6	medium
309334	Unity Linux 20.1060a / 20.1070a Security Update: kernel (UTSA-2026-013823)	Nessus	Unity Linux Local Security Checks	2026/4/22	2026/4/26	medium
308677	Unity Linux 20.1050e / 20.1060e / 20.1070e Security Update: kernel (UTSA-2026-011124)	Nessus	Unity Linux Local Security Checks	2026/4/21	2026/4/22	medium
269425	Linux Distros Unpatched Vulnerability : CVE-2023-53584	Nessus	Misc.	2025/10/8	2026/2/6	medium

检测

插件搜索

medium

medium

medium

medium

medium

medium