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

  - jffs2jffs2_clear_xattr_subsystem の use-after-free を修正します。jffs2 イメージをマウントするとき、イメージの最初の数ブロックは正常で、少なくとも 1 つの xattr 関連の inode を含みますが、次のブロックが異常であると仮定します。その結果、jffs2_scan_eraseblock() でエラーが返されます。 jffs2_clear_xattr_subsystem() が jffs2_build_filesystem() で呼び出され、再び jffs2_do_fill_super() で呼び出されます。最終的に、以下のレポートを確認することができます ============================================ ========================================================================================================================================================================================================= 719 Call Trace: dump_stack+0x115/0x16b jffs2_clear_xattr_subsystem+0x95/0x6ac jffs2_do_fill_super+0x84f/0xc30 jffs2_fill_super+0x2ea/0x4c0 mtd_get_sb+0x254/0x400 mtd_get_sb_by_nr+0x4f/0xd0 get_tree_mtd+0x498/0x840 jffs2_get_tree+0x25/0x30 vfs_get_tree+0x8d/0x2e0 path_mount +0x50f/0x1e50 do_mount+0x107/0x130 __se_sys_mount+0x1c5/0x2f0 __x64_sys_mount+0xc7/0x160 do_syscall_64+0x45/0x70 entry_SYSCALL_64_after_hwframe+0x44/0xa9 タスク 719 による割り当て
    kasan_save_stack+0x23/0x60 __kasan_kmalloc.constprop.0+0x10b/0x120 kasan_slab_alloc+0x12/0x20 kmem_cache_alloc+0x1c0/0x870 jffs2_alloc_xattr_ref+0x2f/0xa0 jffs2_scan_medium.cold+0x3713/0x4794 jffs2_do_mount_fs.cold+0xa7/0x2253 jffs2_do_fill_super+0x383/0xc30 jffs2_fill_super+ 0x2ea/0x4c0 [...] Freed by task 719: kmem_cache_free+0xcc/0x7b0 jffs2_free_xattr_ref+0x78/0x98 jffs2_clear_xattr_subsystem+0xa1/0x6ac jffs2_do_mount_fs.cold+0x5e6/0x2253 jffs2_do_fill_super+0x383/0xc30 jffs2_fill_super+0x2ea/0x4c0 [...]バグのあるアドレスは、サイズ 48 のキャッシュ jffs2_xattr_ref に属する ffff8881243384b8 のオブジェクトに属しています。バグのあるアドレスは、48 バイトの領域の 40 バイト内部にあります。[ffff8881243384b8、ffff8881243384e8] [...] ========== ======================================================== ======= BUG の発生は、次のスタックで示されます --------------------------------- -------------------------------- jffs2_fill_super jffs2_do_fill_super jffs2_do_mount_fs jffs2_build_filesystem jffs2_build_filesystem jff s2_scan_medium jffs2_scan_eraseblock <--- ERROR jffs2_clear_xattr_subsystem <--- free jffs2_clear_xattr_subsystem <--- 再度解放
    -------------------------------------------------- --------- jffs2_do_mount_fs() でエラーが返されます。
    エラーが jffs2_sum_init() により返される場合、jffs2_clear_xattr_subsystem() を実行する必要はありません。エラーが jffs2_build_filesystem() によって返される場合も、jffs2_clear_xattr_subsystem() を再度実行する必要はありません。jffs2_clear_xattr_subsystem() を「out_inohash」から「out_root」へ移動して、この UAF 問題を修正します。CVE-2021-47656

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

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

  - jffs2修正 jffs2_clear_xattr_subsystem 中的釋放後使用錯誤 當我們掛載 jffs2 影像時假設影像的前幾個區塊正常且包含至少一個 xattr 相關的 inode但下一個區塊則異常。因此會在 jffs2_scan_eraseblock() 中傳回錯誤。 jffs2_clear_xattr_subsystem() 會在 jffs2_build_filesystem() 中呼叫然後在 jffs2_do_fill_super() 中再次呼叫。最後我們可以看到下列報告 ========================================== ======================== 錯誤KASAN在 jffs2_clear_xattr_subsystem+0x95/0x6ac 中大小為 8 的讀取 (工作 mount/ 工作在 addr ffff8881243384e0 發生大小為 8 的讀取) 719 Call Trace: dump_stack+0x115/0x16b jffs2_clear_xattr_subsystem+0x95/0x6ac jffs2_do_fill_super+0x84f/0xc30 jffs2_fill_super+0x2ea/0x4c0 mtd_get_sb+0x254/0x400 mtd_get_sb_by_nr+0x4f/0xd0 get_tree_mtd+0x498/0x840 jffs2_get_tree+0x25/0x30 vfs_get_tree+0x8d/0x2e0 path_mount +0x50f/0x1e50 do_mount+0x107/0x130 __se_sys_mount+0x1c5/0x2f0 __x64_sys_mount+0xc7/0x160 do_syscall_64+0x45/0x70 entry_SYSCALL_64_after_hwframe+0x44/0xa9 由工作 719 配置
    kasan_save_stack+0x23/0x60 __kasan_kmalloc.constprop.0+0x10b/0x120 kasan_slab_alloc+0x12/0x20 kmem_cache_alloc+0x1c0/0x870 jffs2_alloc_xattr_ref+0x2f/0xa0 jffs2_scan_medium.cold+0x3713/0x4794 jffs2_do_mount_fs.cold+0xa7/0x2253 jffs2_do_fill_super+0x383/0xc30 jffs2_fill_super+ 0x2ea/0x4c0 [...] Freed by task 719: kmem_cache_free+0xcc/0x7b0 jffs2_free_xattr_ref+0x78/0x98 jffs2_clear_xattr_subsystem+0xa1/0x6ac jffs2_do_mount_fs.cold+0x5e6/0x2253 jffs2_do_fill_super+0x383/0xc30 jffs2_fill_super+0x2ea/0x4c0 [...]錯誤位址屬於 ffff8881243384b8 處的物件該物件屬於大小 48 的快取 jffs2_xattr_ref 錯誤位址位於 48 位元組區域內 40 個位元組 [ffff8881243384b8, ffff8881243384e8) [...] ========= ================================================== ======= 此錯誤的觸發顯示在下列堆疊中 -------------------------------------------- ---------------------------------------- jffs2_fill_super jffs2_do_fill_super jffs2_do_mount_fs jffs2_build_filesystem jff s2_scan_medium jffs2_scan_eraseblock <--- ERROR jffs2_clear_xattr_subsystem <--- 釋放 jffs2_clear_xattr_subsystem <--- 再次釋放
    -------------------------------------------------- --------- 在 jffs2_do_mount_fs() 中傳回一個錯誤。
    如果錯誤是由 jffs2_sum_init() 傳回則不需要執行 jffs2_clear_xattr_subsystem()。如果錯誤是由 jffs2_build_filesystem() 傳回則 jffs2_clear_xattr_subsystem() 也不需要再次執行。因此請將 jffs2_clear_xattr_subsystem() 從「out_inohash」移至「out_root」以修正此 UAF 問題。 (CVE-2021-47656)

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

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

  - jffs2修复 jffs2_clear_xattr_subsystem 中的释放后使用当挂载 jffs2 图像时假设图像的前几个区块正常且包含至少一个与 xattr 相关的 inode但下一个区块异常。因此在 jffs2_scan_eraseblock() 中返回错误。 jffs2_clear_xattr_subsystem() 后会在 jffs2_build_filesystem() 中被调用再在 jffs2_do_fill_super() 中再次被调用。最后我们可以观察到以下报告： ========================================== ======================== 缺陷KASAN由任务挂载造成的 jffs2_clear_xattr_subsystem+0x95/0x6ac 大小为 8 的读取中存在释放后使用/ 719 Call Trace: dump_stack+0x115/0x16b jffs2_clear_xattr_subsystem+0x95/0x6ac jffs2_do_fill_super+0x84f/0xc30 jffs2_fill_super+0x2ea/0x4c0 mtd_get_sb+0x254/0x400 mtd_get_sb_by_nr+0x4f/0xd0 get_tree_mtd+0x498/0x840 jffs2_get_tree+0x25/0x30 vfs_get_tree+0x8d/0x2e0 path_mount +0x50f/0x1e50 do_mount+0x107/0x130 __se_sys_mount+0x1c5/0x2f0 __x64_sys_mount+0xc7/0x160 do_syscall_64+0x45/0x70 entry_SYSCALL_64_after_hwframe+0x44/0xa9 由任务 719 分配
    kasan_save_stack+0x23/0x60 __kasan_kmalloc.constprop.0+0x10b/0x120 kasan_slab_alloc+0x12/0x20 kmem_cache_alloc+0x1c0/0x870 jffs2_alloc_xattr_ref+0x2f/0xa0 jffs2_scan_medium.cold+0x3713/0x4794 jffs2_do_mount_fs.cold+0xa7/0x2253 jffs2_do_fill_super+0x383/0xc30 jffs2_fill_super+ 0x2ea/0x4c0 [...] Freed by task 719: kmem_cache_free+0xcc/0x7b0 jffs2_free_xattr_ref+0x78/0x98 jffs2_clear_xattr_subsystem+0xa1/0x6ac jffs2_do_mount_fs.cold+0x5e6/0x2253 jffs2_do_fill_super+0x383/0xc30 jffs2_fill_super+0x2ea/0x4c0 [...]有缺陷的地址属于 ffff8881243384b8 的对象该对象属于大小为 48 的缓存 jffs2_xattr_ref 有缺陷的地址位于 48 字节区域内 40 字节 [ffff8881243384b8、ffff8881243384e8] [...] ========= ================================================== ======= BUG 的触发情况在以下堆栈中显示 ------------------------------ ---------------------------- jffs2_fill_super jffs2_do_fill_super jffs2_do_mount_fs jffs2_build_filesystem jff s2_scan_medium jffs2_scan_eraseblock <--- 错误 jffs2_clear_xattr_subsystem <--- 释放 jffs2_clear_xattr_subsystem <--- 再次释放
    -------------------------------------------------- --------- jffs2_do_mount_fs() 中返回错误。
    如果该错误由 jffs2_sum_init() 返回则无需执行 jffs2_clear_xattr_subsystem()。如果该错误由 jffs2_build_filesystem() 返回则也无需再次执行 jffs2_clear_xattr_subsystem()。因此将 jffs2_clear_xattr_subsystem() 从“out_inhash”移动到“out_root”以修复此 UAF 问题。 (CVE-2021-47656)

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

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

  - jffs2: fix use-after-free in jffs2_clear_xattr_subsystem When we mount a jffs2 image, assume that the     first few blocks of the image are normal and contain at least one xattr-related inode, but the next block     is abnormal. As a result, an error is returned in jffs2_scan_eraseblock(). jffs2_clear_xattr_subsystem()     is then called in jffs2_build_filesystem() and then again in jffs2_do_fill_super(). Finally we can observe     the following report: ================================================================== BUG: KASAN: use-     after-free in jffs2_clear_xattr_subsystem+0x95/0x6ac Read of size 8 at addr ffff8881243384e0 by task     mount/719 Call Trace: dump_stack+0x115/0x16b jffs2_clear_xattr_subsystem+0x95/0x6ac     jffs2_do_fill_super+0x84f/0xc30 jffs2_fill_super+0x2ea/0x4c0 mtd_get_sb+0x254/0x400     mtd_get_sb_by_nr+0x4f/0xd0 get_tree_mtd+0x498/0x840 jffs2_get_tree+0x25/0x30 vfs_get_tree+0x8d/0x2e0     path_mount+0x50f/0x1e50 do_mount+0x107/0x130 __se_sys_mount+0x1c5/0x2f0 __x64_sys_mount+0xc7/0x160     do_syscall_64+0x45/0x70 entry_SYSCALL_64_after_hwframe+0x44/0xa9 Allocated by task 719:
    kasan_save_stack+0x23/0x60 __kasan_kmalloc.constprop.0+0x10b/0x120 kasan_slab_alloc+0x12/0x20     kmem_cache_alloc+0x1c0/0x870 jffs2_alloc_xattr_ref+0x2f/0xa0 jffs2_scan_medium.cold+0x3713/0x4794     jffs2_do_mount_fs.cold+0xa7/0x2253 jffs2_do_fill_super+0x383/0xc30 jffs2_fill_super+0x2ea/0x4c0 [...]     Freed by task 719: kmem_cache_free+0xcc/0x7b0 jffs2_free_xattr_ref+0x78/0x98     jffs2_clear_xattr_subsystem+0xa1/0x6ac jffs2_do_mount_fs.cold+0x5e6/0x2253 jffs2_do_fill_super+0x383/0xc30     jffs2_fill_super+0x2ea/0x4c0 [...] The buggy address belongs to the object at ffff8881243384b8 which     belongs to the cache jffs2_xattr_ref of size 48 The buggy address is located 40 bytes inside of 48-byte     region [ffff8881243384b8, ffff8881243384e8) [...]     ================================================================== The triggering of the BUG is shown in     the following stack: ----------------------------------------------------------- jffs2_fill_super     jffs2_do_fill_super jffs2_do_mount_fs jffs2_build_filesystem jffs2_scan_medium jffs2_scan_eraseblock <---     ERROR jffs2_clear_xattr_subsystem <--- free jffs2_clear_xattr_subsystem <--- free again
    ----------------------------------------------------------- An error is returned in jffs2_do_mount_fs().
    If the error is returned by jffs2_sum_init(), the jffs2_clear_xattr_subsystem() does not need to be     executed. If the error is returned by jffs2_build_filesystem(), the jffs2_clear_xattr_subsystem() also     does not need to be executed again. So move jffs2_clear_xattr_subsystem() from 'out_inohash' to 'out_root'     to fix this UAF problem. (CVE-2021-47656)

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

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

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

    jffs2: fix use-after-free in jffs2_clear_xattr_subsystem

    When we mount a jffs2 image, assume that the first few blocks of     the image are normal and contain at least one xattr-related inode,     but the next block is abnormal. As a result, an error is returned     in jffs2_scan_eraseblock(). jffs2_clear_xattr_subsystem() is then     called in jffs2_build_filesystem() and then again in     jffs2_do_fill_super().

    Finally we can observe the following report:
     ==================================================================      BUG: KASAN: use-after-free in jffs2_clear_xattr_subsystem+0x95/0x6ac      Read of size 8 at addr ffff8881243384e0 by task mount/719

     Call Trace:
      dump_stack+0x115/0x16b       jffs2_clear_xattr_subsystem+0x95/0x6ac       jffs2_do_fill_super+0x84f/0xc30       jffs2_fill_super+0x2ea/0x4c0       mtd_get_sb+0x254/0x400       mtd_get_sb_by_nr+0x4f/0xd0       get_tree_mtd+0x498/0x840       jffs2_get_tree+0x25/0x30       vfs_get_tree+0x8d/0x2e0       path_mount+0x50f/0x1e50       do_mount+0x107/0x130
      __se_sys_mount+0x1c5/0x2f0
      __x64_sys_mount+0xc7/0x160       do_syscall_64+0x45/0x70       entry_SYSCALL_64_after_hwframe+0x44/0xa9

     Allocated by task 719:
      kasan_save_stack+0x23/0x60
      __kasan_kmalloc.constprop.0+0x10b/0x120       kasan_slab_alloc+0x12/0x20       kmem_cache_alloc+0x1c0/0x870       jffs2_alloc_xattr_ref+0x2f/0xa0       jffs2_scan_medium.cold+0x3713/0x4794       jffs2_do_mount_fs.cold+0xa7/0x2253       jffs2_do_fill_super+0x383/0xc30       jffs2_fill_super+0x2ea/0x4c0      [...]

     Freed by task 719:
      kmem_cache_free+0xcc/0x7b0       jffs2_free_xattr_ref+0x78/0x98       jffs2_clear_xattr_subsystem+0xa1/0x6ac       jffs2_do_mount_fs.cold+0x5e6/0x2253       jffs2_do_fill_super+0x383/0xc30       jffs2_fill_super+0x2ea/0x4c0      [...]

     The buggy address belongs to the object at ffff8881243384b8       which belongs to the cache jffs2_xattr_ref of size 48      The buggy address is located 40 bytes inside of       48-byte region [ffff8881243384b8, ffff8881243384e8)      [...]      ==================================================================

    The triggering of the BUG is shown in the following stack:
    -----------------------------------------------------------     jffs2_fill_super       jffs2_do_fill_super         jffs2_do_mount_fs           jffs2_build_filesystem             jffs2_scan_medium               jffs2_scan_eraseblock        <--- ERROR             jffs2_clear_xattr_subsystem    <--- free         jffs2_clear_xattr_subsystem        <--- free again
    -----------------------------------------------------------

    An error is returned in jffs2_do_mount_fs(). If the error is returned     by jffs2_sum_init(), the jffs2_clear_xattr_subsystem() does not need to     be executed. If the error is returned by jffs2_build_filesystem(), the     jffs2_clear_xattr_subsystem() also does not need to be executed again.
    So move jffs2_clear_xattr_subsystem() from 'out_inohash' to 'out_root'     to fix this UAF problem.

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.

リモートの SUSE Linux SLES15 / SLES_SAP15 ホストには、SUSE-SU-2025:1027-1 のアドバイザリに記載された複数の脆弱性の影響を受けるパッケージがインストールされています。

    SUSE Linux Enterprise 15 SP4 カーネルが更新され、さまざまなセキュリティバグ修正が行われています。


    次のセキュリティバグを修正しました。

    - CVE-2024-2201: x86/BHI での情報漏洩を修正しました (bsc#1217339)。
    - CVE-2024-41092: drm/i915/gt: フェンスレジスタの取り消しによる潜在的なメモリ解放後使用 (Use After Free) を修正しました (bsc#1228483)。
    - CVE-2024-42098: crypto: ecdh - private_key を明示的にゼロ化します (bsc#1228779)。
    - CVE-2024-42229: crypto: aead,cipher - 使用後にキーバッファをゼロ化します (bsc#1228708)。
    - CVE-2024-57996: net_sched: sch_sfq: 1 パケット制限を許可しません (bsc#1239076)。
    - CVE-2024-58014: wifi: brcmsmac: wlc_phy_iqcal_gainparams_nphy() にゲイン範囲チェックを追加しました (bsc#1239109)。
    - CVE-2025-21718: net: rose: ユーザースレッドに対するタイマーの競合状態を修正しました (bsc#1239073)。
    - CVE-2025-21780: drm/amdgpu: smu_sys_set_pp_table() のバッファオーバーフローのアタッチを回避します (bsc#1239115)。


Tenable は、前述の記述ブロックを SUSE セキュリティアドバイザリから直接抽出しています。

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:1027-1 advisory.

    The SUSE Linux Enterprise 15 SP4 kernel was updated to receive various security bugfixes.


    The following security bugs were fixed:

    - CVE-2024-2201: Fixed information leak in x86/BHI (bsc#1217339).
    - CVE-2024-41092: drm/i915/gt: Fix potential UAF by revoke of fence registers (bsc#1228483).
    - CVE-2024-42098: crypto: ecdh - explicitly zeroize private_key (bsc#1228779).
    - CVE-2024-42229: crypto: aead,cipher - zeroize key buffer after use (bsc#1228708).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
    - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).


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

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

リモートの SUSE Linux SLES15 / SLES_SAP15 ホストには、SUSE-SU-2025:1241-1 のアドバイザリに記載された複数の脆弱性の影響を受けるパッケージがインストールされています。

    SUSE Linux Enterprise 15 SP5 カーネルが更新され、さまざまなセキュリティバグ修正が行われています。

    次のセキュリティバグを修正しました。

    - CVE-2022-49053：scsi：target：tcmu：潜在的なページ UAF を修正します（bsc#1237918）。
    - CVE-2022-49465：blk-throttle：bio が調整されているときに BIO_THROTTLED を設定します（bsc#1238919）。
    - CVE-2022-49739：gfs2：インライン inode の inode サイズを常にチェックします（bsc#1240207）。
    - CVE-2023-52935：mm/khugepaged：->anon_vma の競合を修正します（bsc#1240276）。
    - CVE-2024-53124：net：sk->sk_forward_alloc 周辺のデータ競合を修正します（bsc#1234074）。
    - CVE-2024-53176: smb: アンマウント中に、キャッシュされたすべての dir インスタンスが dentry を確実にドロップするようにします (bsc#1234894)。
    - CVE-2024-53178: smb: 再接続が open_cached_dir と競合する際に cfid を漏洩しません (bsc#1234895)。
    - CVE-2024-56651：can: hi311x：hi3110_can_ist()：潜在的な use-after-free を修正します（bsc#1235528）。
    - CVE-2024-57996: net_sched: sch_sfq: 1 パケット制限を許可しません (bsc#1239076)。
    - CVE-2024-58013：Bluetooth： MGMT：mgmt_remove_adv_monitor_sync の slab-use-after-free 読み取りを修正（bsc#1239095）。
    - CVE-2024-58014: wifi: brcmsmac: wlc_phy_iqcal_gainparams_nphy() にゲイン範囲チェックを追加しました (bsc#1239109)。
    - CVE-2025-21693：mm：zswap：CPU ホットアンプラグ中に適切に同期してリソースを解放します（bsc#1237029）。
    - CVE-2025-21718: net: rose: ユーザースレッドに対するタイマーの競合状態を修正しました (bsc#1239073)。
    - CVE-2025-21772：パーティション：mac：偽造パーティションテーブルの処理を修正します（bsc#1238911）。
    - CVE-2025-21780: drm/amdgpu: smu_sys_set_pp_table() のバッファオーバーフローのアタッチを回避します (bsc#1239115)。


Tenable は、前述の記述ブロックを SUSE セキュリティアドバイザリから直接抽出しています。

Nessus はこれらの問題をテストしておらず、代わりにアプリケーションが自己報告するバージョン番号にのみ依存していることに注意してください。

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

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

    jffs2: fix use-after-free in jffs2_clear_xattr_subsystem

    When we mount a jffs2 image, assume that the first few blocks of     the image are normal and contain at least one xattr-related inode,     but the next block is abnormal. As a result, an error is returned     in jffs2_scan_eraseblock(). jffs2_clear_xattr_subsystem() is then     called in jffs2_build_filesystem() and then again in     jffs2_do_fill_super().

    Finally we can observe the following report:
     ==================================================================      BUG: KASAN: use-after-free in jffs2_clear_xattr_subsystem+0x95/0x6ac      Read of size 8 at addr ffff8881243384e0 by task mount/719

     Call Trace:
      dump_stack+0x115/0x16b       jffs2_clear_xattr_subsystem+0x95/0x6ac       jffs2_do_fill_super+0x84f/0xc30       jffs2_fill_super+0x2ea/0x4c0       mtd_get_sb+0x254/0x400       mtd_get_sb_by_nr+0x4f/0xd0       get_tree_mtd+0x498/0x840       jffs2_get_tree+0x25/0x30       vfs_get_tree+0x8d/0x2e0       path_mount+0x50f/0x1e50       do_mount+0x107/0x130
      __se_sys_mount+0x1c5/0x2f0
      __x64_sys_mount+0xc7/0x160       do_syscall_64+0x45/0x70       entry_SYSCALL_64_after_hwframe+0x44/0xa9

     Allocated by task 719:
      kasan_save_stack+0x23/0x60
      __kasan_kmalloc.constprop.0+0x10b/0x120       kasan_slab_alloc+0x12/0x20       kmem_cache_alloc+0x1c0/0x870       jffs2_alloc_xattr_ref+0x2f/0xa0       jffs2_scan_medium.cold+0x3713/0x4794       jffs2_do_mount_fs.cold+0xa7/0x2253       jffs2_do_fill_super+0x383/0xc30       jffs2_fill_super+0x2ea/0x4c0      [...]

     Freed by task 719:
      kmem_cache_free+0xcc/0x7b0       jffs2_free_xattr_ref+0x78/0x98       jffs2_clear_xattr_subsystem+0xa1/0x6ac       jffs2_do_mount_fs.cold+0x5e6/0x2253       jffs2_do_fill_super+0x383/0xc30       jffs2_fill_super+0x2ea/0x4c0      [...]

     The buggy address belongs to the object at ffff8881243384b8       which belongs to the cache jffs2_xattr_ref of size 48      The buggy address is located 40 bytes inside of       48-byte region [ffff8881243384b8, ffff8881243384e8)      [...]      ==================================================================

    The triggering of the BUG is shown in the following stack:
    -----------------------------------------------------------     jffs2_fill_super       jffs2_do_fill_super         jffs2_do_mount_fs           jffs2_build_filesystem             jffs2_scan_medium               jffs2_scan_eraseblock        <--- ERROR             jffs2_clear_xattr_subsystem    <--- free         jffs2_clear_xattr_subsystem        <--- free again
    -----------------------------------------------------------

    An error is returned in jffs2_do_mount_fs(). If the error is returned     by jffs2_sum_init(), the jffs2_clear_xattr_subsystem() does not need to     be executed. If the error is returned by jffs2_build_filesystem(), the     jffs2_clear_xattr_subsystem() also does not need to be executed again.
    So move jffs2_clear_xattr_subsystem() from 'out_inohash' to 'out_root'     to fix this UAF problem.

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 remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2025:1241-1 advisory.

    The SUSE Linux Enterprise 15 SP5 kernel was updated to receive various security bugfixes.

    The following security bugs were fixed:

    - CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
    - CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
    - CVE-2022-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
    - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
    - CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
    - CVE-2024-53176: smb: During unmount, ensure all cached dir instances drop their dentry (bsc#1234894).
    - CVE-2024-53178: smb: Do not leak cfid when reconnect races with open_cached_dir (bsc#1234895).
    - CVE-2024-56651: can: hi311x: hi3110_can_ist(): fix potential use-after-free (bsc#1235528).
    - CVE-2024-57996: net_sched: sch_sfq: do not allow 1 packet limit (bsc#1239076).
    - CVE-2024-58013: Bluetooth: MGMT: Fix slab-use-after-free Read in mgmt_remove_adv_monitor_sync     (bsc#1239095).
    - CVE-2024-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - CVE-2025-21693: mm: zswap: properly synchronize freeing resources during CPU hotunplug (bsc#1237029).
    - CVE-2025-21718: net: rose: fix timer races against user threads (bsc#1239073).
    - CVE-2025-21772: partitions: mac: fix handling of bogus partition table (bsc#1238911).
    - CVE-2025-21780: drm/amdgpu: avoid buffer overflow attach in smu_sys_set_pp_table() (bsc#1239115).


Tenable has extracted the preceding description block directly from the SUSE 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	名称	产品	系列	发布时间	最近更新时间	严重程度
224374	Linux Distros のパッチ未適用の脆弱性: CVE-2021-47656	Nessus	Misc.	2025/3/5	2025/10/28	high
224374	Linux Distros 未修補的弱點：CVE-2021-47656	Nessus	Misc.	2025/3/5	2025/10/28	high
224374	Linux Distros 未修补的漏洞：CVE-2021-47656	Nessus	Misc.	2025/3/5	2025/10/28	high
224374	Linux Distros Unpatched Vulnerability : CVE-2021-47656	Nessus	Misc.	2025/3/5	2025/10/28	high
273689	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989825)	Nessus	Unity Linux Local Security Checks	2025/11/5	2025/11/5	high
233410	SUSE SLES15 セキュリティ更新 : kernel (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	2025/3/27	2025/9/24	high
233410	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	2025/3/27	2025/9/24	high
234407	SUSE SLES15 セキュリティ更新 : kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	2025/4/15	2025/10/28	high
268432	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-987398)	Nessus	Unity Linux Local Security Checks	2025/10/7	2025/10/15	high
234407	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	2025/4/15	2025/10/28	high

检测

插件搜索

high

high

high

high

high

high

high

high

high

high