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

  - ocfs2dlmfs修正 user_dlm_destroy_lock 的錯誤處理。當 user_dlm_destroy_lock 失敗時並未清理結束前所設定的旗標。針對 USER_LOCK_IN_TEARDOWN如果此函式因為鎖定仍在使用中而失敗下次取消連結叫用此函式時就會傳回成功然後如果鎖定未使用 (檔案已關閉)取消連結就會移除 inode 和 dentry但是 dlm鎖定仍連結在 dlm 鎖定資源中則當 bast 進入時會因釋放後使用而觸發不穩定。請參閱下列錯誤呼叫追踪。若要修正此失敗則應還原 USER_LOCK_IN_TEARDOWN。如果 USER_LOCK_IN_TEARDOWN 設定為讓使用者知道取消連結失敗也會傳回錯誤。針對 ocfs2_dlm_unlock 失敗的情況除了 USER_LOCK_IN_TEARDOWN 以外也需要清除 USER_LOCK_BUSY。
    即使微調鎖定在其間釋放但 USER_LOCK_IN_TEARDOWN 仍為 USER_LOCK_BUSY如果在每個等待此旗標的位置之前先檢查 USER_LOCK_IN_TEARDOWN 是否結束這將確保沒有流程等待由 user_dlm_destroy_lock( )我們可以在 ocfs2_dlm_unlock 失敗時簡單地還原 USER_LOCK_BUSY。修正 user_dlm_cluster_lock()這是唯一未遵循此問題的函式。 [ 941.336392] (python,26174,16):dlmfs_unlink:562 錯誤取消連結 004fb0000060000b5a90b8c847b72e1損毀時發生錯誤 -16 [ 989.757536] ------------[在這裡截取 ]----- ------- [ 989.757709] fs/ocfs2/dlmfs/userdlm.c:173! 的核心錯誤 989.757876[  ] invalid opcode: 0000 [#1] SMP [989.758027] Modules linked in: ksplice_2zhuk2jr_ib_ipoib_new(O) ksplice_2zhuk2jr(O) mptctl mptbase xen_netback xen_blkback xen_gntalloc xen_gntdev xen_evtchn cdc_ether usbnet mii ocfs2 jbd2 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfsv3 nfs_acl nfs fscache lockd grace ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs bnx2fc fcoe libfcoe libfc scsi_transport_fc sunrpc ipmi_devintf bridge stp llc rds_rdma rds bonding ib_sdp ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad rdma_cm ib_cm iw_cm falcon_lsm_serviceable(PE) falcon_nf_netcontain(PE) mlx4_vnic falcon_kal(E) falcon_lsm_pinned_13402(E) mlx4_ib ib_sa ib_mad ib_core ib_addr xenfs xen_privcmd dm_multipath iTCO_wdt iTCO_vendor_support pcspkr sb_edac edac_core i2c_i801 lpc_ich mfd_core ipmi_ssif i2c_core ipmi_si ipmi_msghandler [ 989.760686] ioatdma sg ext3 jbd mbcache sd_mod ahci libahci ixgbe dca ptp pps_core vxlan udp_tunnel ip6_udp_tunnel megaraid_sas mlx4_core crc32c_intel be2iscsi bnx 2i cnic uio cxgb4i cxgb4 cxgb3i libcxgbi ipv6 cxgb3 mdio libiscsi_tcp qla4xxx iscsi_boot_sysfs libiscsi scsi_transport_iscsi wmi dm_mirror dm_region_hash dm_log dm_mod [last unloaded: ksplice_2zhuk2jr_ib_ipoib_old] [ 989.761987] CPU: 10 PID: 19102 Comm: dlm_thread Tainted: P OE 4.1.12-124.57.1 .el6uek.x86_64 #2 [ 989.762290] 硬體名稱Oracle Corporation ORACLE SERVER X5-2/ASM,MotherBOARD,1U, BIOS 30350100 06/17/2021 [ 989.762599] 工作 ffff880178af6200 ti
    ffff88017f7c8000 task.ti: ffff88017f7c8000 [ 989.762848] RIPe030[<ffffffffc07d4316>] [<ffffffffc07d4316>] __user_dlm_queue_lockres.part.4+0x76/0x80 [ocfs2_dlmfs] [ 989.763185] RSP
    e02b:ffff88017f7cbcb8 EFLAGS00010246 [ 989.763353] RAX0000000000000000 RBXffff880174d48008 RCX
    0000000000000003 [ 989.763565] RDX: 0000000000120012 RSI: 0000000000000003 RDI: ffff880174d48170 [989.763778] RBP: ffff88017f7cbcc8 R08: ffff88021f4293b0 R09: 0000000000000000 [ 989.763991] R10:
    ffff880179c8c000 R110000000000000003 R12ffff880174d48008 [ 989.764204] R130000000000000003 R14
     R15ffff880179c8c000  : ffff88021db7a000 [ 989.764422] FS: 0000000000000000(0000) GS:ffff880247480000(0000) knlGS:ffff880247480000 [ 989.764685] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 989.764865] CR2:
    ffff8000007f6800 CR30000000001ae0000 CR40000000000042660 [ 989.765081] 堆疊[ 989.765167] 00000000000 ---truncated--- (CVE-2022-49337)

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

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

  - ocfs2: dlmfs修复 user_dlm_destroy_lock 的错误处理 user_dlm_destroy_lock 失败时未清除其在退出前设置的标记。对于 USER_LOCK_IN_TEARDOWN如果此函数因为锁定仍处于使用状态而失败则下次当取消链接时调用此函数时它将返回成功然后如果锁定不是使用文件已关闭而是使用 dlm 则取消链接将删除 inode 和 dentry lock 仍然在 dlm 锁定资源中链接这样当 bast 进入时将因释放后使用而触发错误。请参阅以下错误调用跟踪。要修复此问题应在失败时恢复 USER_LOCK_IN_TEARDOWN。此外如果设置 USER_LOCK_IN_TEARDOWN 则应返回错误让用户知道取消链接失败。对于 ocfs2_dlm_unlock 失败除了 USER_LOCK_IN_TEARDOWN 之外还需要清除 USER_LOCK_BUSY。
    即使自旋锁定其间已释放但仍设置了 USER_LOCK_IN_TEARDOWN对于 USER_LOCK_BUSY如果在等待此标记的每个位置之前都检查 USER_LOCK_IN_TEARDOWN 以进行补救这将确保没有流在由 user_dlm_destroy_lock 设置的忙碌标记上等待)那么我们可以在 ocfs2_dlm_unlock 失败时简单地恢复 USER_LOCK_BUSY。修复 user_dlm_cluster_lock()这是唯一不遵循此函数的函数。 [ 941.336392] (python,26174,16)dlmfs_unlink:562 错误从破坏中取消链接 004fb0000060000b5a90b8c847b72e1错误 -16 [ 989.757536] ------------[ 在此处切换 ]----- ------- [ 989.757709] fs/ocfs2/dlmfs/userdlm.c:173! 的内核缺陷 989.757876[  ] invalid opcode: 0000 [#1] SMP [989.758027] Modules linked in: ksplice_2zhuk2jr_ib_ipoib_new(O) ksplice_2zhuk2jr(O) mptctl mptbase xen_netback xen_blkback xen_gntalloc xen_gntdev xen_evtchn cdc_ether usbnet mii ocfs2 jbd2 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfsv3 nfs_acl nfs fscache lockd grace ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs bnx2fc fcoe libfcoe libfc scsi_transport_fc sunrpc ipmi_devintf bridge stp llc rds_rdma rds bonding ib_sdp ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad rdma_cm ib_cm iw_cm falcon_lsm_serviceable(PE) falcon_nf_netcontain(PE) mlx4_vnic falcon_kal(E) falcon_lsm_pinned_13402(E) mlx4_ib ib_sa ib_mad ib_core ib_addr xenfs xen_privcmd dm_multipath iTCO_wdt iTCO_vendor_support pcspkr sb_edac edac_core i2c_i801 lpc_ich mfd_core ipmi_ssif i2c_core ipmi_si ipmi_msghandler [ 989.760686] ioatdma sg ext3 jbd mbcache sd_mod ahci libahci ixgbe dca ptp pps_core vxlan udp_tunnel ip6_udp_tunnel megaraid_sas mlx4_core crc32c_intel be2iscsi bnx 2i cnic uio cxgb4i cxgb4 cxgb3i libcxgbi ipv6 cxgb3 mdio libiscsi_tcp qla4xxx iscsi_boot_sysfs libiscsi scsi_transport_iscsi wmi dm_mirror dm_region_hash dm_log dm_mod [last unloaded: ksplice_2zhuk2jr_ib_ipoib_old] [ 989.761987] CPU: 10 PID: 19102 Comm: dlm_thread Tainted: P OE 4.1.12-124.57.1 .el6uek.x86_64 #2 [ 989.762290] 硬件名称Oracle Corporation ORACLE SERVER X5-2/ASM,MotherBOARD,1U, BIOS 30350100 06/17/2021 [ 989.762599] 任务ffff880178af6200 ti
    ffff88017f7c8000 task.ti: ffff88017f7c8000 [ 989.762848] RIPe030:[<ffffffffc07d4316>] [<ffffffffc07d4316>] __user_dlm_queue_lockres.part.4+0x76/0x80 [ocfs2_dlmfs] [ 989.763185] RSP
    e02b:ffff88017f7cbcb8 EFLAGS: 00010246 [ 989.763353] RAX: 0000000000000000 RBX: ffff880174d48008 RCX
    0000000000000003 [ 989.763565] RDX: 0000000000120012 RSI: 0000000000000003 RDI: ffff880174d48170 [989.763778] RBP: ffff88017f7cbcc8 R08: ffff88021f4293b0 R09: 0000000000000000 [ 989.763991] R10:
    ffff880179c8c000 R110000000000000003 R12ffff880174d48008 [ 989.764204] R130000000000000003 R14
     R15ffff880179c8c000  : ffff88021db7a000 [ 989.764422] FS: 0000000000000000(0000) GS:ffff880247480000(0000) knlGS:ffff880247480000 [ 989.764685] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 989.764865] CR2:
    ffff8000007f6800 CR3: 0000000001ae0000 CR4: 0000000000042660 [ 989.765081] Stack: [ 989.765167] 00000000000 ---truncated--- (CVE-2022-49337)

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

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

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

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

  - ocfs2dlmfsuser_dlm_destroy_lock のエラー処理を修正します。user_dlm_destroy_lock が失敗した際、終了前に設定されたフラグをクリーンアップしませんでした。USER_LOCK_IN_TEARDOWN に関して、ロックがまだ使用中であるためにこの関数が失敗する場合、次回 unlink がこの関数を呼び出す際、成功を返します。ロックが使用されていない場合ファイルが閉じている場合、unlink は inode および dentry を削除しますが、dlm lock が dlm ロックリソースでまだリンクされているため、bast が着信すると、use-after-free によりパニックをトリガーします。次のパニック呼び出しトレースを参照してください。これを修正するには、失敗した場合に USER_LOCK_IN_TEARDOWN を元に戻す必要があります。また、USER_LOCK_IN_TEARDOWN がユーザーに unlink の失敗を通知するように設定されている場合、エラーも返される必要があります。ocfs2_dlm_unlock 失敗の場合は、USER_LOCK_IN_TEARDOWN に加えて、USER_LOCK_BUSY もクリアする必要があります。
    スピンロックが中間でリリースされるものの、USER_LOCK_IN_TEARDOWN が依然として設定されているにもかかわらず、USER_LOCK_BUSY に対して、このフラグで待機するすべての場所の前に、USER_LOCK_IN_TEARDOWN がチェックされて救済されると、user_dlm_destroy_lock() が設定したビジーフラグでフローを待機させません。から、ocfs2_dlm_unlock が失敗したときに USER_LOCK_BUSY を単純に元に戻すことができます。これに従わない唯一の関数である user_dlm_cluster_lock() を修正します。 [ 941.336392] python,26174,16:dlmfs_unlink:562 ERROR: unlink 004fb0000060000b5a90b8c847b72e1、error -16 from destroy [ 989.757536] ------------[cuther]---------- ------- [ 989.757709] fs/ocfs2/dlmfs/userdlm.c:173! のカーネルのバグ 989.757876[  ] invalid opcode: 0000 [#1] SMP [989.758027] Modules linked in: ksplice_2zhuk2jr_ib_ipoib_new(O) ksplice_2zhuk2jr(O) mptctl mptbase xen_netback xen_blkback xen_gntalloc xen_gntdev xen_evtchn cdc_ether usbnet mii ocfs2 jbd2 rpcsec_gss_krb5 auth_rpcgss nfsv4 nfsv3 nfs_acl nfs fscache lockd grace ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs bnx2fc fcoe libfcoe libfc scsi_transport_fc sunrpc ipmi_devintf bridge stp llc rds_rdma rds bonding ib_sdp ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad rdma_cm ib_cm iw_cm falcon_lsm_serviceable(PE) falcon_nf_netcontain(PE) mlx4_vnic falcon_kal(E) falcon_lsm_pinned_13402(E) mlx4_ib ib_sa ib_mad ib_core ib_addr xenfs xen_privcmd dm_multipath iTCO_wdt iTCO_vendor_support pcspkr sb_edac edac_core i2c_i801 lpc_ich mfd_core ipmi_ssif i2c_core ipmi_si ipmi_msghandler [ 989.760686] ioatdma sg ext3 jbd mbcache sd_mod ahci libahci ixgbe dca ptp pps_core vxlan udp_tunnel ip6_udp_tunnel megaraid_sas mlx4_core crc32c_intel be2iscsi bnx 2i cnic uio cxgb4i cxgb4 cxgb3i libcxgbi ipv6 cxgb3 mdio libiscsi_tcp qla4xxx iscsi_boot_sysfs libiscsi scsi_transport_iscsi wmi dm_mirror dm_region_hash dm_log dm_mod [last unloaded: ksplice_2zhuk2jr_ib_ipoib_old] [ 989.761987] CPU: 10 PID: 19102 Comm: dlm_thread Tainted: P OE 4.1.12-124.57.1 .el6uek.x86_64 #2 [ 989.762290] ハードウェア名: Oracle Corporation ORACLE SERVER X5-2/ASM、MotherBOARD、1U、BIOS 30350100 06/17/2021 [ 989.762599] タスク: ffff880178af6200 ti:
    ffff88017f7c8000 task.ti: ffff88017f7c8000 [ 989.762848] RIP: e030:[<ffffffffc07d4316>] [<ffffffffc07d4316>] __user_dlm_queue_lockres.part.4+0x76/0x80 [ocfs2_dlmfs] [ 989.763185] RSP
    e02b:ffff88017f7cbcb8 EFLAGS: 00010246 [ 989.763353] RAX: 0000000000000000 RBX: ffff880174d48008 RCX:
    0000000000000003 [ 989.763565] RDX: 0000000000120012 RSI: 0000000000000003 RDI: ffff880174d48170 [989.763778] RBP: ffff88017f7cbcc8 R08: ffff88021f4293b0 R09: 0000000000000000 [ 989.763991] R10:
    ffff880179c8c000 R110000000000000003 R12ffff880174d48008 [ 989.764204] R130000000000000003 R14
     R15ffff880179c8c000  : ffff88021db7a000 [ 989.764422] FS: 0000000000000000(0000) GS:ffff880247480000(0000) knlGS:ffff880247480000 [ 989.764685] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 989.764865] CR2:
    --truncated--- ffff8000007f6800CVE-2022-49337CR3000000001ae0000 989.765167CR4000000000004260 989.765081

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

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

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

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

    - CVE-2021-46925: smc_sock の競合によって引き起こされるカーネルパニックを修正しました (bsc#1220466)。
    - CVE-2021-47645: media: staging: media: zoran: zoran_reap_stat_com の正しいバッファ数を計算 (bsc#1237767)。
    - CVE-2021-47648: gpu: host1x:「host1x_remove()」でのメモリリークを修正 (bsc#1237725)。
    - CVE-2022-49046: i2c: dev: dev_set_name() を呼び出すときの戻り値をチェック (bsc#1237842)。
    - CVE-2022-49051: net: usb: aqc111: RX 修正で領域外アクセスを修正 (bsc#1237903)。
    - CVE-2022-49053:scsi: target: tcmu: 潜在的なページ UAF を修正 (bsc#1237918)。
    - CVE-2022-49059: nfc: nci: uaf を防ぐために flush_workqueue を追加 (bsc#1238007)。
    - CVE-2022-49074: irqchip/gic-v3: GICR_CTLR.RWP のポーリングを修正 (bsc#1237728)。
    - CVE-2022-49075: btrfs: qgroup 予約オーバーフローの qgroup 制限を修正 (bsc#1237733)。
    - CVE-2022-49084: qede: 使用する前に skb が割り当てられていることを確認する (bsc#1237751)。
    - CVE-2022-49107: ceph: note_last_dentry がエラーを返す場合に ceph_readdir でのメモリリークを修正 (bsc#1237973)。
    - CVE-2022-49109: ceph: ceph_get_snapdir() の inode 参照漏洩を修正 (bsc#1237836)。
    - CVE-2022-49119: scsi: pm8001: pm8001_chip_fw_flash_update_req() のメモリリークを修正 (bsc#1237925)。
    - CVE-2022-49120: scsi: pm8001: pm8001_send_abort_all() のタスク漏洩を修正 (bsc#1237969)。
    - CVE-2022-49209: bpf、sockmap: sk msg がいっぱいになっているときの tcp_bpf_sendmsg のメモリリークを修正 (bsc#1238252)。
    - CVE-2022-49220: dax: キャッシュを破壊する前に inode がフラッシュされるようにする (bsc#1237936)。
    - CVE-2022-49275: can: m_can: m_can_tx_handler(): skb の use-after-free を修正 (bsc#1238719)。
    - CVE-2022-49286: tpm: tpm-space.c で try_get_ops() を使用する (bsc#1238647)。
    - CVE-2022-49292: ALSA: oss: PCM OSS バッファ割り当てオーバーフローを修正 (bsc#1238625)。
    - CVE-2022-49308: extcon: ドライバーデータの設定後に作成されるように extcon デバイスを変更 (bsc#1238654)。
    - CVE-2022-49331: nfc: st21nfca: EVT_TRANSACTION 処理のメモリリークを修正 (bsc#1237813)。
    - CVE-2022-49344: af_unix: unix_dgram_peer_wake_me() でのデータ競合を修正 (bsc#1237988)。
    - CVE-2022-49367: net: dsa: mv88e6xxx: mv88e6xxx_mdios_register の refcount 漏洩を修正 (bsc#1238447)。
    - CVE-2022-49370: firmware: dmi-sysfs: dmi_sysfs_register_handle のメモリ漏洩を修正 (bsc#1238467)。
    - CVE-2022-49372: tcp: tcp_rtx_synack() は、プロセスコンテキストから呼び出される可能性がある (bsc#1238251)。
    - CVE-2022-49388: ubi: ubi_create_volume: ボリューム作成が失敗したときのメモリ解放後使用 (use-after-free) を修正 (bsc#1237934)。
    - CVE-2022-49395: um: LDT 設定の領域外読み取りを修正 (bsc#1237953)。
    - CVE-2022-49397: phy: qcom-qmp: プローブエラーの struct clk 漏洩を修正 (bsc#1237823)。
    - CVE-2022-49404: RDMA/hfi1: 潜在的な整数乗算オーバーフローのエラーを修正 (bsc#1238430)。
    - CVE-2022-49416: wifi: mac80211: chanctx コードのメモリ解放後使用 (Use After Free) を修正(bsc#1238293)。
    - CVE-2022-49433: RDMA/hfi1: 初期化される前のロックの使用を防止 (bsc#1238268)。
    - CVE-2022-49472: net: phy: micrel: .driver_data なしでプロービングを許可(bsc#1238951)。
    - CVE-2022-49488: drm/msm/mdp5: デッドロックが発生した場合、mdp5_mixer_release でエラーコードを返す (bsc#1238600)。
    - CVE-2022-49495: drm/msm/hdmi: platform_get_resource_byname() 呼び出し後に戻り値をチェックする (bsc#1237932)。
    - CVE-2022-49497: net: skb_checksum_help() から 2 つの BUG() を削除 (bsc#1238946)。
    - CVE-2022-49505: NFC: dev->rfkill を NULL 出力し、UAF を防ぐ (bsc#1238615)。
    - CVE-2022-49516: ice: VF VSI ポインターの値を常にチェック (bsc#1238953)。
    - CVE-2022-49519: ath10k: ドライバー状態 RESTARTING に対する中断中に ath10k_halt をスキップ (bsc#1238943)。
    - CVE-2022-49524: media: pci: cx23885: cx23885_initdev() のエラー処理を修正 (bsc#1238949)。
    - CVE-2022-49530: drm/amd/pm: si_parse_power_table() での二重解放を修正 (bsc#1238944)。
    - CVE-2022-49538: ALSA: jack: snd_jack_report() での mutex 呼び出しを修正 (bsc#1238843)。
    - CVE-2022-49544: ipw2x00: libipw_xmit() の潜在的な NULL デリファレンスを修正 (bsc#1238721).
    - CVE-2022-49545: ALSA: usb-audio: MIDI サブストリームを閉じる際に未解決の作業をキャンセル (bsc#1238729)。
    - CVE-2022-49546: x86/kexec: ヘッダーバッファの二重解放を修正 (bsc#1238750)。
    - CVE-2022-49563: crypto: qat - RSA 用の param チェックを追加 (bsc#1238787)。
    - CVE-2022-49564: crypto: qat - DH 用の param チェックを追加 (bsc#1238789)。
    - CVE-2022-49578: ip: sysctl_ip_prot_sock 周辺のデータ競合を修正。(bsc#1238794)。
    - CVE-2022-49581: be2net: be_get_module_eeprom のバッファオーバーフローを修正 (bsc#1238540)。
    - CVE-2022-49589: kABI: mr_ifc_count の変更を保護 (bsc#1238598)。
    - CVE-2022-49605: igc: IGC_REMOVED ロジックを元に戻し、適切に実装 (bsc#1238433)。
    - CVE-2022-49607: perf/core: perf_event_set_output() と perf_mmap_close() の間のデータ競合を修正 (bsc#1238817)。
    - CVE-2022-49610: KVM: VMX: vmenter の前に RSB アンダーフローを防止 (bsc#1238952)。
    - CVE-2022-49619: net: sfp: sfp_probe() のメモリリークを修正 (bsc#1239003)。
    - CVE-2022-49620: net: tipc: tipc_sk_create() の refcount 漏洩の可能性を修正 (bsc#1239002)。
    - CVE-2022-49640: sysctl: proc_douintvec_minmax() のデータ競合を修正 (bsc#1237782)。
    - CVE-2022-49641: sysctl: proc_douintvec() のデータ競合を修正 (bsc#1237831)。
    - CVE-2022-49667: net: bonding: 802.3ad スレーブのバインド解除後のメモリ解放後使用 (use-after-free) を修正 (bsc#1238282)。
    - CVE-2022-49672: net: tun: 破壊時にデバイスから NAPI のリンクを解除 (bsc#1238816)。
    - CVE-2022-49711: bus: fsl-mc-bus: fsl_mc_bus_remove() での KASAN use-after-free を修正 (bsc#1238416)。
    - CVE-2022-49727: ipv6: l2tp_ip6_sendmsg の符号付き整数オーバーフローを修正 (bsc#1239059)。
    - CVE-2022-49740: wifi: brcmfmac: 領域外読み取りを防ぐためにチャネル仕様のカウント値をチェック (bsc#1240233)。
    - CVE-2023-52935: mm/khugepaged: ->anon_vma の競合を修正 (bsc#1240276)。
    - CVE-2023-52997: ipv4: ip_metrics_convert() の spectre v1 ガジェットの可能性を阻止 (bsc#1240303)。
    - CVE-2023-53010: bnxt: テスト名の末尾を超えて読み取らない (bsc#1240290)。
    - CVE-2023-53019: net: mdio: mdiobus_get_phy() のパラメーター addr を検証 (bsc#1240286)。
    - CVE-2024-35910: kABI の tcp の修正: カーネルソケットのタイマーを適切に終了させる (bsc#1224489)。
    - CVE-2024-36968: Bluetooth: L2CAP: l2cap_le_flowctl_init() の div-by-zero を修正 (bsc#1226130)。
    - CVE-2024-38559: scsi: qedf: コピーされたバッファが NUL の終端であることを確認する (bsc#1226785)。
    - CVE-2024-41005: netpoll: netpoll_owner_active 内の競合状態の修正 (bsc#1227858)。
    - CVE-2024-49571: net/smc: 提案メッセージを受信する際に iparea_offset および ipv6_prefixes_cnt をチェック (bsc#1235733)。
    - CVE-2024-49935: ACPI: PAD: exit_round_robin() のクラッシュを修正 (bsc#1232370)。
    - CVE-2024-49940: l2tp: トンネルの参照カウントのアンダーフローを防ぐ (bsc#1232812)。
    - CVE-2024-50269: usb: musb: sunxi: リリースされた usb phy へのアクセスを修正 (bsc#1233458)。
    - CVE-2024-53124: net: sk->sk_forward_alloc 周辺のデータ競合を修正 (bsc#1234074)。
    - CVE-2024-53140: netlink: ソケットクローズでの未処理のダンプを終了する (bsc#1234222)。
    - CVE-2024-53680: ipvs: ip_vs_protocol_init() の初期化されていないスタックアクセスによる UB を修正 (bsc#1235715)。
    - CVE-2024-56640: net/smc: LGR および use-after-free 問題のリンクの修正 (bsc#1235436)。
    - CVE-2024-56770: net/sched: netem: 子 qdisc からのバックログ更新に対応 (bsc#1235637)。
    - CVE-2024-57900: ila: nf_register_net_hooks() への呼び出しをシリアル化 (bsc#1235973)。
    - CVE-2024-57973: rdma/cxgb4: 32 ビットでの潜在的な整数オーバーフローを防止 (bsc#1238531)。
    - CVE-2024-57979: pps の変更に対する kABI の回避策 (bsc#1238521)。
    - CVE-2024-57996: net_sched: sch_sfq: 1 パケット制限を許可しません (bsc#1239076)。
    - CVE-2024-58014: wifi: brcmsmac: wlc_phy_iqcal_gainparams_nphy() にゲイン範囲チェックを追加しました (bsc#1239109)。
    - CVE-2024-58052: drm/amdgpu: atomctrl_get_smc_sclk_range_table の潜在的な NULL ポインターデリファレンスを修正 (bsc#1238986)。
    - CVE-2024-58071: team: すでにチームデバイスであるデバイスを追加することを防ぐ (bsc#1238970)
    - CVE-2024-58072: wifi: rtlwifi: 未使用の check_buddy_priv を削除 (bsc#1238964)。
    - CVE-2024-58083: KVM: kvm_get_vcpu() で、ターゲット vCPU がオンラインであることを明示的に検証 (bsc#1239036)。
    - CVE-2025-21703: netem: qdisc_tree_reduce_backlog() の前に sch->q.qlen を更新 (bsc#1237313)。
    - CVE-2025-21708: net: usb: rtl8150: 基本的なエンドポイントチェックを有効にする (bsc#1239087)。
    - CVE-2025-21744: wifi: brcmfmac: brcmf_txfinalize() の NULL ポインターデリファレンスを修正 (bsc#1238903)。
    - CVE-2025-21759: ipv6: mcast: igmp6_send() の RCU 保護を拡張 (bsc#1238738)。
    - CVE-2025-21760: ndisc: ndisc_send_skb() の RCU 保護を拡張 (bsc#1238763)。
    - CVE-2025-21762: arp: arp_xmit() で RCU 保護を使用 (bsc#1238780)。
    - CVE-2025-21763: neighbour: __neigh_notify() で RCU 保護を使用 (bsc#1237897)。
    - CVE-2025-21765: ipv6: ip6_default_advmss() で RCU 保護を使用 (bsc#1237906)。
    - CVE-2025-21766: ipv4: __ip_rt_update_pmtu() で RCU 保護を使用 (bsc#1238754)。
    - CVE-2025-21776: USB: hub: 設定またはインターフェースが多すぎる非準拠デバイスを無視 (bsc#1238909)。
    - CVE-2025-21782: orangefs: orangefs_debug_write の oob を修正 (bsc#1239117)。
    - CVE-2025-21785: arm64: cacheinfo: cacheinfo 配列への領域外書き込みを回避 (bsc#1238747)。
    - CVE-2025-21791: vrf: l3mdev_l3_out() で RCU 保護を使用 (bsc#1238512)。
    - CVE-2025-21796: nfsd: acl_access/acl_default のリリース後に、それらをクリア (bsc#1238716)。
    - CVE-2025-21802: net: hns3: パラレル化するドライバーをアンロードする際の oops を修正します (bsc#1238751)。
    - CVE-2025-21821: fbdev: omap: LCD DMA に対してスレッド化された IRQ を使用 (bsc#1239174)。
    - CVE-2025-21831: PCI: TUXEDO Sirius Gen1 の D3 に一部の root ポートを配置するのを回避 (bsc#1239039)。
    - CVE-2025-21846: acct: ワークキューから最後の書き込みを実行 (bsc#1239508)。
    - CVE-2025-21848: nfp: bpf: nfp_app_ctrl_msg_alloc() のチェックを追加 (bsc#1239479)。
    - CVE-2025-21865: gtp: gtp_net_exit_batch_rtnl() のリスト破損スプラットを抑制 (bsc#1239481)。
    - CVE-2025-21871: tee: optee: supplicant 待機ループを修正 (bsc#1240183)。
    - CVE-2025-21877: usbnet: gl620a: genelink_bind() のエンドポイントチェックを修正 (bsc#1240172)。
    - CVE-2025-21891: ipvlan: ネットワークヘッダーが skb 線形部分にあることを確認 (bsc#1240186)。
    - CVE-2025-21916: usb: atm: cxacru: 既存のエンドポイントチェックにある欠陥を修正 (bsc#1240582)。
    - CVE-2025-21922: ppp: KMSAN uninit-value の警告を bpf で修正 (bsc#1240639)。
    - CVE-2025-21934: rapidio: rio_add_net() fails が失敗した場合の API ミスを修正 (bsc#1240708)。
    - CVE-2025-21935: rapidio: rio_scan_alloc_net() での rio_add_net() に対するチェックを追加 (bsc#1240700)。
    - CVE-2025-21969: Bluetooth: L2CAP: 一部の arch でのビルドエラーを修正 (bsc#1240784)。
    - CVE-2025-21993: iscsi_ibft: ibft_attr_show_nic() の UBSAN shift-out-of-bounds 警告を修正 (bsc#1240797)。
    - CVE-2025-21996: drm/radeon: radeon_vce_cs_parse() の初期化されていないサイズの問題を修正 (bsc#1240801)。
    - CVE-2025-22007: Bluetooth: chan_alloc_skb_cb() のエラーコードを修正(bsc#1240582)。


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

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

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

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

    ocfs2: dlmfs: fix error handling of user_dlm_destroy_lock

    When user_dlm_destroy_lock failed, it didn't clean up the flags it set     before exit.  For USER_LOCK_IN_TEARDOWN, if this function fails because of     lock is still in used, next time when unlink invokes this function, it     will return succeed, and then unlink will remove inode and dentry if lock     is not in used(file closed), but the dlm lock is still linked in dlm lock     resource, then when bast come in, it will trigger a panic due to     user-after-free.  See the following panic call trace.  To fix this,     USER_LOCK_IN_TEARDOWN should be reverted if fail.  And also error should     be returned if USER_LOCK_IN_TEARDOWN is set to let user know that unlink     fail.

    For the case of ocfs2_dlm_unlock failure, besides USER_LOCK_IN_TEARDOWN,     USER_LOCK_BUSY is also required to be cleared.  Even though spin lock is     released in between, but USER_LOCK_IN_TEARDOWN is still set, for     USER_LOCK_BUSY, if before every place that waits on this flag,     USER_LOCK_IN_TEARDOWN is checked to bail out, that will make sure no flow     waits on the busy flag set by user_dlm_destroy_lock(), then we can     simplely revert USER_LOCK_BUSY when ocfs2_dlm_unlock fails.  Fix     user_dlm_cluster_lock() which is the only function not following this.

    [  941.336392] (python,26174,16):dlmfs_unlink:562 ERROR: unlink     004fb0000060000b5a90b8c847b72e1, error -16 from destroy     [  989.757536] ------------[ cut here ]------------     [  989.757709] kernel BUG at fs/ocfs2/dlmfs/userdlm.c:173!     [  989.757876] invalid opcode: 0000 [#1] SMP     [  989.758027] Modules linked in: ksplice_2zhuk2jr_ib_ipoib_new(O)     ksplice_2zhuk2jr(O) mptctl mptbase xen_netback xen_blkback xen_gntalloc     xen_gntdev xen_evtchn cdc_ether usbnet mii ocfs2 jbd2 rpcsec_gss_krb5     auth_rpcgss nfsv4 nfsv3 nfs_acl nfs fscache lockd grace ocfs2_dlmfs     ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs bnx2fc     fcoe libfcoe libfc scsi_transport_fc sunrpc ipmi_devintf bridge stp llc     rds_rdma rds bonding ib_sdp ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad     rdma_cm ib_cm iw_cm falcon_lsm_serviceable(PE) falcon_nf_netcontain(PE)     mlx4_vnic falcon_kal(E) falcon_lsm_pinned_13402(E) mlx4_ib ib_sa ib_mad     ib_core ib_addr xenfs xen_privcmd dm_multipath iTCO_wdt iTCO_vendor_support     pcspkr sb_edac edac_core i2c_i801 lpc_ich mfd_core ipmi_ssif i2c_core ipmi_si     ipmi_msghandler     [  989.760686]  ioatdma sg ext3 jbd mbcache sd_mod ahci libahci ixgbe dca ptp     pps_core vxlan udp_tunnel ip6_udp_tunnel megaraid_sas mlx4_core crc32c_intel     be2iscsi bnx2i cnic uio cxgb4i cxgb4 cxgb3i libcxgbi ipv6 cxgb3 mdio     libiscsi_tcp qla4xxx iscsi_boot_sysfs libiscsi scsi_transport_iscsi wmi     dm_mirror dm_region_hash dm_log dm_mod [last unloaded:
    ksplice_2zhuk2jr_ib_ipoib_old]     [  989.761987] CPU: 10 PID: 19102 Comm: dlm_thread Tainted: P           OE     4.1.12-124.57.1.el6uek.x86_64 #2     [  989.762290] Hardware name: Oracle Corporation ORACLE SERVER     X5-2/ASM,MOTHERBOARD,1U, BIOS 30350100 06/17/2021     [  989.762599] task: ffff880178af6200 ti: ffff88017f7c8000 task.ti:
    ffff88017f7c8000     [  989.762848] RIP: e030:[<ffffffffc07d4316>]  [<ffffffffc07d4316>]
    __user_dlm_queue_lockres.part.4+0x76/0x80 [ocfs2_dlmfs]     [  989.763185] RSP: e02b:ffff88017f7cbcb8  EFLAGS: 00010246     [  989.763353] RAX: 0000000000000000 RBX: ffff880174d48008 RCX:
    0000000000000003     [  989.763565] RDX: 0000000000120012 RSI: 0000000000000003 RDI:
    ffff880174d48170     [  989.763778] RBP: ffff88017f7cbcc8 R08: ffff88021f4293b0 R09:
    0000000000000000     [  989.763991] R10: ffff880179c8c000 R11: 0000000000000003 R12:
    ffff880174d48008     [  989.764204] R13: 0000000000000003 R14: ffff880179c8c000 R15:
    ffff88021db7a000     [  989.764422] FS:  0000000000000000(0000) GS:ffff880247480000(0000)     knlGS:ffff880247480000     [  989.764685] CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033     [  989.764865] CR2: ffff8000007f6800 CR3: 0000000001ae0000 CR4:
    0000000000042660     [  989.765081] Stack:
    [  989.765167]  00000000000
    ---truncated---

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.

An update of the linux package has been released.

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

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

    ocfs2: dlmfs: fix error handling of user_dlm_destroy_lock

    When user_dlm_destroy_lock failed, it didn't clean up the flags it set     before exit.  For USER_LOCK_IN_TEARDOWN, if this function fails because of     lock is still in used, next time when unlink invokes this function, it     will return succeed, and then unlink will remove inode and dentry if lock     is not in used(file closed), but the dlm lock is still linked in dlm lock     resource, then when bast come in, it will trigger a panic due to     user-after-free.  See the following panic call trace.  To fix this,     USER_LOCK_IN_TEARDOWN should be reverted if fail.  And also error should     be returned if USER_LOCK_IN_TEARDOWN is set to let user know that unlink     fail.

    For the case of ocfs2_dlm_unlock failure, besides USER_LOCK_IN_TEARDOWN,     USER_LOCK_BUSY is also required to be cleared.  Even though spin lock is     released in between, but USER_LOCK_IN_TEARDOWN is still set, for     USER_LOCK_BUSY, if before every place that waits on this flag,     USER_LOCK_IN_TEARDOWN is checked to bail out, that will make sure no flow     waits on the busy flag set by user_dlm_destroy_lock(), then we can     simplely revert USER_LOCK_BUSY when ocfs2_dlm_unlock fails.  Fix     user_dlm_cluster_lock() which is the only function not following this.

    [  941.336392] (python,26174,16):dlmfs_unlink:562 ERROR: unlink     004fb0000060000b5a90b8c847b72e1, error -16 from destroy     [  989.757536] ------------[ cut here ]------------     [  989.757709] kernel BUG at fs/ocfs2/dlmfs/userdlm.c:173!     [  989.757876] invalid opcode: 0000 [#1] SMP     [  989.758027] Modules linked in: ksplice_2zhuk2jr_ib_ipoib_new(O)     ksplice_2zhuk2jr(O) mptctl mptbase xen_netback xen_blkback xen_gntalloc     xen_gntdev xen_evtchn cdc_ether usbnet mii ocfs2 jbd2 rpcsec_gss_krb5     auth_rpcgss nfsv4 nfsv3 nfs_acl nfs fscache lockd grace ocfs2_dlmfs     ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs bnx2fc     fcoe libfcoe libfc scsi_transport_fc sunrpc ipmi_devintf bridge stp llc     rds_rdma rds bonding ib_sdp ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad     rdma_cm ib_cm iw_cm falcon_lsm_serviceable(PE) falcon_nf_netcontain(PE)     mlx4_vnic falcon_kal(E) falcon_lsm_pinned_13402(E) mlx4_ib ib_sa ib_mad     ib_core ib_addr xenfs xen_privcmd dm_multipath iTCO_wdt iTCO_vendor_support     pcspkr sb_edac edac_core i2c_i801 lpc_ich mfd_core ipmi_ssif i2c_core ipmi_si     ipmi_msghandler     [  989.760686]  ioatdma sg ext3 jbd mbcache sd_mod ahci libahci ixgbe dca ptp     pps_core vxlan udp_tunnel ip6_udp_tunnel megaraid_sas mlx4_core crc32c_intel     be2iscsi bnx2i cnic uio cxgb4i cxgb4 cxgb3i libcxgbi ipv6 cxgb3 mdio     libiscsi_tcp qla4xxx iscsi_boot_sysfs libiscsi scsi_transport_iscsi wmi     dm_mirror dm_region_hash dm_log dm_mod [last unloaded:
    ksplice_2zhuk2jr_ib_ipoib_old]     [  989.761987] CPU: 10 PID: 19102 Comm: dlm_thread Tainted: P           OE     4.1.12-124.57.1.el6uek.x86_64 #2     [  989.762290] Hardware name: Oracle Corporation ORACLE SERVER     X5-2/ASM,MOTHERBOARD,1U, BIOS 30350100 06/17/2021     [  989.762599] task: ffff880178af6200 ti: ffff88017f7c8000 task.ti:
    ffff88017f7c8000     [  989.762848] RIP: e030:[<ffffffffc07d4316>]  [<ffffffffc07d4316>]
    __user_dlm_queue_lockres.part.4+0x76/0x80 [ocfs2_dlmfs]     [  989.763185] RSP: e02b:ffff88017f7cbcb8  EFLAGS: 00010246     [  989.763353] RAX: 0000000000000000 RBX: ffff880174d48008 RCX:
    0000000000000003     [  989.763565] RDX: 0000000000120012 RSI: 0000000000000003 RDI:
    ffff880174d48170     [  989.763778] RBP: ffff88017f7cbcc8 R08: ffff88021f4293b0 R09:
    0000000000000000     [  989.763991] R10: ffff880179c8c000 R11: 0000000000000003 R12:
    ffff880174d48008     [  989.764204] R13: 0000000000000003 R14: ffff880179c8c000 R15:
    ffff88021db7a000     [  989.764422] FS:  0000000000000000(0000) GS:ffff880247480000(0000)     knlGS:ffff880247480000     [  989.764685] CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033     [  989.764865] CR2: ffff8000007f6800 CR3: 0000000001ae0000 CR4:
    0000000000042660     [  989.765081] Stack:
    [  989.765167]  00000000000
    ---truncated---

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.

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

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

    ocfs2: dlmfs: fix error handling of user_dlm_destroy_lock

    When user_dlm_destroy_lock failed, it didn't clean up the flags it set     before exit.  For USER_LOCK_IN_TEARDOWN, if this function fails because of     lock is still in used, next time when unlink invokes this function, it     will return succeed, and then unlink will remove inode and dentry if lock     is not in used(file closed), but the dlm lock is still linked in dlm lock     resource, then when bast come in, it will trigger a panic due to     user-after-free.  See the following panic call trace.  To fix this,     USER_LOCK_IN_TEARDOWN should be reverted if fail.  And also error should     be returned if USER_LOCK_IN_TEARDOWN is set to let user know that unlink     fail.

    For the case of ocfs2_dlm_unlock failure, besides USER_LOCK_IN_TEARDOWN,     USER_LOCK_BUSY is also required to be cleared.  Even though spin lock is     released in between, but USER_LOCK_IN_TEARDOWN is still set, for     USER_LOCK_BUSY, if before every place that waits on this flag,     USER_LOCK_IN_TEARDOWN is checked to bail out, that will make sure no flow     waits on the busy flag set by user_dlm_destroy_lock(), then we can     simplely revert USER_LOCK_BUSY when ocfs2_dlm_unlock fails.  Fix     user_dlm_cluster_lock() which is the only function not following this.

    [  941.336392] (python,26174,16):dlmfs_unlink:562 ERROR: unlink     004fb0000060000b5a90b8c847b72e1, error -16 from destroy     [  989.757536] ------------[ cut here ]------------     [  989.757709] kernel BUG at fs/ocfs2/dlmfs/userdlm.c:173!     [  989.757876] invalid opcode: 0000 [#1] SMP     [  989.758027] Modules linked in: ksplice_2zhuk2jr_ib_ipoib_new(O)     ksplice_2zhuk2jr(O) mptctl mptbase xen_netback xen_blkback xen_gntalloc     xen_gntdev xen_evtchn cdc_ether usbnet mii ocfs2 jbd2 rpcsec_gss_krb5     auth_rpcgss nfsv4 nfsv3 nfs_acl nfs fscache lockd grace ocfs2_dlmfs     ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs bnx2fc     fcoe libfcoe libfc scsi_transport_fc sunrpc ipmi_devintf bridge stp llc     rds_rdma rds bonding ib_sdp ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad     rdma_cm ib_cm iw_cm falcon_lsm_serviceable(PE) falcon_nf_netcontain(PE)     mlx4_vnic falcon_kal(E) falcon_lsm_pinned_13402(E) mlx4_ib ib_sa ib_mad     ib_core ib_addr xenfs xen_privcmd dm_multipath iTCO_wdt iTCO_vendor_support     pcspkr sb_edac edac_core i2c_i801 lpc_ich mfd_core ipmi_ssif i2c_core ipmi_si     ipmi_msghandler     [  989.760686]  ioatdma sg ext3 jbd mbcache sd_mod ahci libahci ixgbe dca ptp     pps_core vxlan udp_tunnel ip6_udp_tunnel megaraid_sas mlx4_core crc32c_intel     be2iscsi bnx2i cnic uio cxgb4i cxgb4 cxgb3i libcxgbi ipv6 cxgb3 mdio     libiscsi_tcp qla4xxx iscsi_boot_sysfs libiscsi scsi_transport_iscsi wmi     dm_mirror dm_region_hash dm_log dm_mod [last unloaded:
    ksplice_2zhuk2jr_ib_ipoib_old]     [  989.761987] CPU: 10 PID: 19102 Comm: dlm_thread Tainted: P           OE     4.1.12-124.57.1.el6uek.x86_64 #2     [  989.762290] Hardware name: Oracle Corporation ORACLE SERVER     X5-2/ASM,MOTHERBOARD,1U, BIOS 30350100 06/17/2021     [  989.762599] task: ffff880178af6200 ti: ffff88017f7c8000 task.ti:
    ffff88017f7c8000     [  989.762848] RIP: e030:[<ffffffffc07d4316>]  [<ffffffffc07d4316>]
    __user_dlm_queue_lockres.part.4+0x76/0x80 [ocfs2_dlmfs]     [  989.763185] RSP: e02b:ffff88017f7cbcb8  EFLAGS: 00010246     [  989.763353] RAX: 0000000000000000 RBX: ffff880174d48008 RCX:
    0000000000000003     [  989.763565] RDX: 0000000000120012 RSI: 0000000000000003 RDI:
    ffff880174d48170     [  989.763778] RBP: ffff88017f7cbcc8 R08: ffff88021f4293b0 R09:
    0000000000000000     [  989.763991] R10: ffff880179c8c000 R11: 0000000000000003 R12:
    ffff880174d48008     [  989.764204] R13: 0000000000000003 R14: ffff880179c8c000 R15:
    ffff88021db7a000     [  989.764422] FS:  0000000000000000(0000) GS:ffff880247480000(0000)     knlGS:ffff880247480000     [  989.764685] CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033     [  989.764865] CR2: ffff8000007f6800 CR3: 0000000001ae0000 CR4:
    0000000000042660     [  989.765081] Stack:
    [  989.765167]  00000000000
    ---truncated---

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-2025-987619 advisory.

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

    ocfs2: dlmfs: fix error handling of user_dlm_destroy_lock

    When user_dlm_destroy_lock failed, it didn't clean up the flags it set     before exit.  For USER_LOCK_IN_TEARDOWN, if this function fails because of     lock is still in used, next time when unlink invokes this function, it     will return succeed, and then unlink will remove inode and dentry if lock     is not in used(file closed), but the dlm lock is still linked in dlm lock     resource, then when bast come in, it will trigger a panic due to     user-after-free.  See the following panic call trace.  To fix this,     USER_LOCK_IN_TEARDOWN should be reverted if fail.  And also error should     be returned if USER_LOCK_IN_TEARDOWN is set to let user know that unlink     fail.

    For the case of ocfs2_dlm_unlock failure, besides USER_LOCK_IN_TEARDOWN,     USER_LOCK_BUSY is also required to be cleared.  Even though spin lock is     released in between, but USER_LOCK_IN_TEARDOWN is still set, for     USER_LOCK_BUSY, if before every place that waits on this flag,     USER_LOCK_IN_TEARDOWN is checked to bail out, that will make sure no flow     waits on the busy flag set by user_dlm_destroy_lock(), then we can     simplely revert USER_LOCK_BUSY when ocfs2_dlm_unlock fails.  Fix     user_dlm_cluster_lock() which is the only function not following this.

    [  941.336392] (python,26174,16):dlmfs_unlink:562 ERROR: unlink     004fb0000060000b5a90b8c847b72e1, error -16 from destroy     [  989.757536] ------------[ cut here ]------------     [  989.757709] kernel BUG at fs/ocfs2/dlmfs/userdlm.c:173!     [  989.757876] invalid opcode: 0000 [#1] SMP     [  989.758027] Modules linked in: ksplice_2zhuk2jr_ib_ipoib_new(O)     ksplice_2zhuk2jr(O) mptctl mptbase xen_netback xen_blkback xen_gntalloc     xen_gntdev xen_evtchn cdc_ether usbnet mii ocfs2 jbd2 rpcsec_gss_krb5     auth_rpcgss nfsv4 nfsv3 nfs_acl nfs fscache lockd grace ocfs2_dlmfs     ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue configfs bnx2fc     fcoe libfcoe libfc scsi_transport_fc sunrpc ipmi_devintf bridge stp llc     rds_rdma rds bonding ib_sdp ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad     rdma_cm ib_cm iw_cm falcon_lsm_serviceable(PE) falcon_nf_netcontain(PE)     mlx4_vnic falcon_kal(E) falcon_lsm_pinned_13402(E) mlx4_ib ib_sa ib_mad     ib_core ib_addr xenfs xen_privcmd dm_multipath iTCO_wdt iTCO_vendor_support     pcspkr sb_edac edac_core i2c_i801 lpc_ich mfd_core ipmi_ssif i2c_core ipmi_si     ipmi_msghandler     [  989.760686]  ioatdma sg ext3 jbd mbcache sd_mod ahci libahci ixgbe dca ptp     pps_core vxlan udp_tunnel ip6_udp_tunnel megaraid_sas mlx4_core crc32c_intel     be2iscsi bnx2i cnic uio cxgb4i cxgb4 cxgb3i libcxgbi ipv6 cxgb3 mdio     libiscsi_tcp qla4xxx iscsi_boot_sysfs libiscsi scsi_transport_iscsi wmi     dm_mirror dm_region_hash dm_log dm_mod [last unloaded:
    ksplice_2zhuk2jr_ib_ipoib_old]     [  989.761987] CPU: 10 PID: 19102 Comm: dlm_thread Tainted: P           OE     4.1.12-124.57.1.el6uek.x86_64 #2     [  989.762290] Hardware name: Oracle Corporation ORACLE SERVER     X5-2/ASM,MOTHERBOARD,1U, BIOS 30350100 06/17/2021     [  989.762599] task: ffff880178af6200 ti: ffff88017f7c8000 task.ti:
    ffff88017f7c8000     [  989.762848] RIP: e030:[<ffffffffc07d4316>]  [<ffffffffc07d4316>]
    __user_dlm_queue_lockres.part.4+0x76/0x80 [ocfs2_dlmfs]     [  989.763185] RSP: e02b:ffff88017f7cbcb8  EFLAGS: 00010246     [  989.763353] RAX: 0000000000000000 RBX: ffff880174d48008 RCX:
    0000000000000003     [  989.763565] RDX: 0000000000120012 RSI: 0000000000000003 RDI:
    ffff880174d48170     [  989.763778] RBP: ffff88017f7cbcc8 R08: ffff88021f4293b0 R09:
    0000000000000000     [  989.763991] R10: ffff880179c8c000 R11: 0000000000000003 R12:
    ffff880174d48008     [  989.764204] R13: 0000000000000003 R14: ffff880179c8c000 R15:
    ffff88021db7a000     [  989.764422] FS:  0000000000000000(0000) GS:ffff880247480000(0000)     knlGS:ffff880247480000     [  989.764685] CS:  e033 DS: 0000 ES: 0000 CR0: 0000000080050033     [  989.764865] CR2: ffff8000007f6800 CR3: 0000000001ae0000 CR4:
    0000000000042660     [  989.765081] Stack:
    [  989.765167]  00000000000
    ---truncated---

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: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.

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

  - ocfs2: dlmfs: fix error handling of user_dlm_destroy_lock When user_dlm_destroy_lock failed, it didn't     clean up the flags it set before exit. For USER_LOCK_IN_TEARDOWN, if this function fails because of lock     is still in used, next time when unlink invokes this function, it will return succeed, and then unlink     will remove inode and dentry if lock is not in used(file closed), but the dlm lock is still linked in dlm     lock resource, then when bast come in, it will trigger a panic due to user-after-free. See the following     panic call trace. To fix this, USER_LOCK_IN_TEARDOWN should be reverted if fail. And also error should be     returned if USER_LOCK_IN_TEARDOWN is set to let user know that unlink fail. For the case of     ocfs2_dlm_unlock failure, besides USER_LOCK_IN_TEARDOWN, USER_LOCK_BUSY is also required to be cleared.
    Even though spin lock is released in between, but USER_LOCK_IN_TEARDOWN is still set, for USER_LOCK_BUSY,     if before every place that waits on this flag, USER_LOCK_IN_TEARDOWN is checked to bail out, that will     make sure no flow waits on the busy flag set by user_dlm_destroy_lock(), then we can simplely revert     USER_LOCK_BUSY when ocfs2_dlm_unlock fails. Fix user_dlm_cluster_lock() which is the only function not     following this. [ 941.336392] (python,26174,16):dlmfs_unlink:562 ERROR: unlink     004fb0000060000b5a90b8c847b72e1, error -16 from destroy [ 989.757536] ------------[ cut here ]------------     [ 989.757709] kernel BUG at fs/ocfs2/dlmfs/userdlm.c:173! [ 989.757876] invalid opcode: 0000 [#1] SMP [     989.758027] Modules linked in: ksplice_2zhuk2jr_ib_ipoib_new(O) ksplice_2zhuk2jr(O) mptctl mptbase     xen_netback xen_blkback xen_gntalloc xen_gntdev xen_evtchn cdc_ether usbnet mii ocfs2 jbd2 rpcsec_gss_krb5     auth_rpcgss nfsv4 nfsv3 nfs_acl nfs fscache lockd grace ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm     ocfs2_nodemanager ocfs2_stackglue configfs bnx2fc fcoe libfcoe libfc scsi_transport_fc sunrpc ipmi_devintf     bridge stp llc rds_rdma rds bonding ib_sdp ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad rdma_cm ib_cm iw_cm     falcon_lsm_serviceable(PE) falcon_nf_netcontain(PE) mlx4_vnic falcon_kal(E) falcon_lsm_pinned_13402(E)     mlx4_ib ib_sa ib_mad ib_core ib_addr xenfs xen_privcmd dm_multipath iTCO_wdt iTCO_vendor_support pcspkr     sb_edac edac_core i2c_i801 lpc_ich mfd_core ipmi_ssif i2c_core ipmi_si ipmi_msghandler [ 989.760686]     ioatdma sg ext3 jbd mbcache sd_mod ahci libahci ixgbe dca ptp pps_core vxlan udp_tunnel ip6_udp_tunnel     megaraid_sas mlx4_core crc32c_intel be2iscsi bnx2i cnic uio cxgb4i cxgb4 cxgb3i libcxgbi ipv6 cxgb3 mdio     libiscsi_tcp qla4xxx iscsi_boot_sysfs libiscsi scsi_transport_iscsi wmi dm_mirror dm_region_hash dm_log     dm_mod [last unloaded: ksplice_2zhuk2jr_ib_ipoib_old] [ 989.761987] CPU: 10 PID: 19102 Comm: dlm_thread     Tainted: P OE 4.1.12-124.57.1.el6uek.x86_64 #2 [ 989.762290] Hardware name: Oracle Corporation ORACLE     SERVER X5-2/ASM,MOTHERBOARD,1U, BIOS 30350100 06/17/2021 [ 989.762599] task: ffff880178af6200 ti:
    ffff88017f7c8000 task.ti: ffff88017f7c8000 [ 989.762848] RIP: e030:[<ffffffffc07d4316>]     [<ffffffffc07d4316>] __user_dlm_queue_lockres.part.4+0x76/0x80 [ocfs2_dlmfs] [ 989.763185] RSP:
    e02b:ffff88017f7cbcb8 EFLAGS: 00010246 [ 989.763353] RAX: 0000000000000000 RBX: ffff880174d48008 RCX:
    0000000000000003 [ 989.763565] RDX: 0000000000120012 RSI: 0000000000000003 RDI: ffff880174d48170 [     989.763778] RBP: ffff88017f7cbcc8 R08: ffff88021f4293b0 R09: 0000000000000000 [ 989.763991] R10:
    ffff880179c8c000 R11: 0000000000000003 R12: ffff880174d48008 [ 989.764204] R13: 0000000000000003 R14:
    ffff880179c8c000 R15: ffff88021db7a000 [ 989.764422] FS: 0000000000000000(0000) GS:ffff880247480000(0000)     knlGS:ffff880247480000 [ 989.764685] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 989.764865] CR2:
    ffff8000007f6800 CR3: 0000000001ae0000 CR4: 0000000000042660 [ 989.765081] Stack: [ 989.765167]     00000000000 ---truncated--- (CVE-2022-49337)

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

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

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

    The following security bugs were fixed:

    - CVE-2021-46925: Fixed kernel panic caused by race of smc_sock (bsc#1220466).
    - CVE-2021-47645: media: staging: media: zoran: calculate the right buffer number for zoran_reap_stat_com     (bsc#1237767).
    - CVE-2021-47648: gpu: host1x: Fix a memory leak in 'host1x_remove()' (bsc#1237725).
    - CVE-2022-49046: i2c: dev: check return value when calling dev_set_name() (bsc#1237842).
    - CVE-2022-49051: net: usb: aqc111: Fix out-of-bounds accesses in RX fixup (bsc#1237903).
    - CVE-2022-49053: scsi: target: tcmu: Fix possible page UAF (bsc#1237918).
    - CVE-2022-49059: nfc: nci: add flush_workqueue to prevent uaf (bsc#1238007).
    - CVE-2022-49074: irqchip/gic-v3: Fix GICR_CTLR.RWP polling (bsc#1237728).
    - CVE-2022-49075: btrfs: fix qgroup reserve overflow the qgroup limit (bsc#1237733).
    - CVE-2022-49084: qede: confirm skb is allocated before using (bsc#1237751).
    - CVE-2022-49107: ceph: fix memory leak in ceph_readdir when note_last_dentry returns error (bsc#1237973).
    - CVE-2022-49109: ceph: fix inode reference leakage in ceph_get_snapdir() (bsc#1237836).
    - CVE-2022-49119: scsi: pm8001: Fix memory leak in pm8001_chip_fw_flash_update_req() (bsc#1237925).
    - CVE-2022-49120: scsi: pm8001: Fix task leak in pm8001_send_abort_all() (bsc#1237969).
    - CVE-2022-49209: bpf, sockmap: Fix memleak in tcp_bpf_sendmsg while sk msg is full (bsc#1238252).
    - CVE-2022-49220: dax: make sure inodes are flushed before destroy cache (bsc#1237936).
    - CVE-2022-49275: can: m_can: m_can_tx_handler(): fix use after free of skb (bsc#1238719).
    - CVE-2022-49286: tpm: use try_get_ops() in tpm-space.c (bsc#1238647).
    - CVE-2022-49292: ALSA: oss: Fix PCM OSS buffer allocation overflow (bsc#1238625).
    - CVE-2022-49308: extcon: Modify extcon device to be created after driver data is set (bsc#1238654).
    - CVE-2022-49331: nfc: st21nfca: fix memory leaks in EVT_TRANSACTION handling (bsc#1237813).
    - CVE-2022-49344: af_unix: Fix a data-race in unix_dgram_peer_wake_me() (bsc#1237988).
    - CVE-2022-49367: net: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register (bsc#1238447).
    - CVE-2022-49370: firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle (bsc#1238467).
    - CVE-2022-49372: tcp: tcp_rtx_synack() can be called from process context (bsc#1238251).
    - CVE-2022-49388: ubi: ubi_create_volume: Fix use-after-free when volume creation failed (bsc#1237934).
    - CVE-2022-49395: um: Fix out-of-bounds read in LDT setup (bsc#1237953).
    - CVE-2022-49397: phy: qcom-qmp: fix struct clk leak on probe errors (bsc#1237823).
    - CVE-2022-49404: RDMA/hfi1: Fix potential integer multiplication overflow errors (bsc#1238430).
    - CVE-2022-49416: wifi: mac80211: fix use-after-free in chanctx code (bsc#1238293).
    - CVE-2022-49433: RDMA/hfi1: Prevent use of lock before it is initialized (bsc#1238268).
    - CVE-2022-49472: net: phy: micrel: Allow probing without .driver_data (bsc#1238951).
    - CVE-2022-49488: drm/msm/mdp5: Return error code in mdp5_mixer_release when deadlock (bsc#1238600).
    - CVE-2022-49495: drm/msm/hdmi: check return value after calling platform_get_resource_byname()     (bsc#1237932).
    - CVE-2022-49497: net: remove two BUG() from skb_checksum_help() (bsc#1238946).
    - CVE-2022-49505: NFC: NULL out the dev->rfkill to prevent UAF (bsc#1238615).
    - CVE-2022-49516: ice: always check VF VSI pointer values (bsc#1238953).
    - CVE-2022-49519: ath10k: skip ath10k_halt during suspend for driver state RESTARTING (bsc#1238943).
    - CVE-2022-49524: media: pci: cx23885: Fix the error handling in cx23885_initdev() (bsc#1238949).
    - CVE-2022-49530: drm/amd/pm: fix double free in si_parse_power_table() (bsc#1238944).
    - CVE-2022-49538: ALSA: jack: Fix mutex call in snd_jack_report() (bsc#1238843).
    - CVE-2022-49544: ipw2x00: Fix potential NULL dereference in libipw_xmit() (bsc#1238721).
    - CVE-2022-49545: ALSA: usb-audio: Cancel pending work at closing a MIDI substream (bsc#1238729).
    - CVE-2022-49546: x86/kexec: Fix double-free of elf header buffer (bsc#1238750).
    - CVE-2022-49563: crypto: qat - add param check for RSA (bsc#1238787).
    - CVE-2022-49564: crypto: qat - add param check for DH (bsc#1238789).
    - CVE-2022-49578: ip: Fix data-races around sysctl_ip_prot_sock. (bsc#1238794).
    - CVE-2022-49581: be2net: Fix buffer overflow in be_get_module_eeprom (bsc#1238540).
    - CVE-2022-49589: kABI: protect mr_ifc_count change (bsc#1238598).
    - CVE-2022-49605: igc: Reinstate IGC_REMOVED logic and implement it properly (bsc#1238433).
    - CVE-2022-49607: perf/core: Fix data race between perf_event_set_output() and perf_mmap_close()     (bsc#1238817).
    - CVE-2022-49610: KVM: VMX: Prevent RSB underflow before vmenter (bsc#1238952).
    - CVE-2022-49619: net: sfp: fix memory leak in sfp_probe() (bsc#1239003).
    - CVE-2022-49620: net: tipc: fix possible refcount leak in tipc_sk_create() (bsc#1239002).
    - CVE-2022-49640: sysctl: Fix data races in proc_douintvec_minmax() (bsc#1237782).
    - CVE-2022-49641: sysctl: Fix data races in proc_douintvec() (bsc#1237831).
    - CVE-2022-49667: net: bonding: fix use-after-free after 802.3ad slave unbind (bsc#1238282).
    - CVE-2022-49672: net: tun: unlink NAPI from device on destruction (bsc#1238816).
    - CVE-2022-49711: bus: fsl-mc-bus: fix KASAN use-after-free in fsl_mc_bus_remove() (bsc#1238416).
    - CVE-2022-49727: ipv6: Fix signed integer overflow in l2tp_ip6_sendmsg (bsc#1239059).
    - CVE-2022-49740: wifi: brcmfmac: Check the count value of channel spec to prevent out-of-bounds reads     (bsc#1240233).
    - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
    - CVE-2023-52997: ipv4: prevent potential spectre v1 gadget in ip_metrics_convert() (bsc#1240303).
    - CVE-2023-53010: bnxt: Do not read past the end of test names (bsc#1240290).
    - CVE-2023-53019: net: mdio: validate parameter addr in mdiobus_get_phy() (bsc#1240286).
    - CVE-2024-35910: kABI fix for tcp: properly terminate timers for kernel sockets (bsc#1224489).
    - CVE-2024-36968: Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init() (bsc#1226130).
    - CVE-2024-38559: scsi: qedf: Ensure the copied buf is NUL terminated (bsc#1226785).
    - CVE-2024-41005: netpoll: Fix race condition in netpoll_owner_active (bsc#1227858).
    - CVE-2024-49571: net/smc: check iparea_offset and ipv6_prefixes_cnt when receiving proposal msg     (bsc#1235733).
    - CVE-2024-49935: ACPI: PAD: fix crash in exit_round_robin() (bsc#1232370).
    - CVE-2024-49940: l2tp: prevent possible tunnel refcount underflow (bsc#1232812).
    - CVE-2024-50269: usb: musb: sunxi: Fix accessing an released usb phy (bsc#1233458).
    - CVE-2024-53124: net: fix data-races around sk->sk_forward_alloc (bsc#1234074).
    - CVE-2024-53140: netlink: terminate outstanding dump on socket close (bsc#1234222).
    - CVE-2024-53680: ipvs: fix UB due to uninitialized stack access in ip_vs_protocol_init() (bsc#1235715).
    - CVE-2024-56640: net/smc: fix LGR and link use-after-free issue (bsc#1235436).
    - CVE-2024-56770: net/sched: netem: account for backlog updates from child qdisc (bsc#1235637).
    - CVE-2024-57900: ila: serialize calls to nf_register_net_hooks() (bsc#1235973).
    - CVE-2024-57973: rdma/cxgb4: Prevent potential integer overflow on 32bit (bsc#1238531).
    - CVE-2024-57979: kABI workaround for pps changes (bsc#1238521).
    - 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-2024-58052: drm/amdgpu: Fix potential NULL pointer dereference in atomctrl_get_smc_sclk_range_table     (bsc#1238986).
    - CVE-2024-58071: team: prevent adding a device which is already a team device lower (bsc#1238970)
    - CVE-2024-58072: wifi: rtlwifi: remove unused check_buddy_priv (bsc#1238964).
    - CVE-2024-58083: KVM: Explicitly verify target vCPU is online in kvm_get_vcpu() (bsc#1239036).
    - CVE-2025-21703: netem: Update sch->q.qlen before qdisc_tree_reduce_backlog() (bsc#1237313).
    - CVE-2025-21708: net: usb: rtl8150: enable basic endpoint checking (bsc#1239087).
    - CVE-2025-21744: wifi: brcmfmac: fix NULL pointer dereference in brcmf_txfinalize() (bsc#1238903).
    - CVE-2025-21759: ipv6: mcast: extend RCU protection in igmp6_send() (bsc#1238738).
    - CVE-2025-21760: ndisc: extend RCU protection in ndisc_send_skb() (bsc#1238763).
    - CVE-2025-21762: arp: use RCU protection in arp_xmit() (bsc#1238780).
    - CVE-2025-21763: neighbour: use RCU protection in __neigh_notify() (bsc#1237897).
    - CVE-2025-21765: ipv6: use RCU protection in ip6_default_advmss() (bsc#1237906).
    - CVE-2025-21766: ipv4: use RCU protection in __ip_rt_update_pmtu() (bsc#1238754).
    - CVE-2025-21776: USB: hub: Ignore non-compliant devices with too many configs or interfaces     (bsc#1238909).
    - CVE-2025-21782: orangefs: fix a oob in orangefs_debug_write (bsc#1239117).
    - CVE-2025-21785: arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array (bsc#1238747).
    - CVE-2025-21791: vrf: use RCU protection in l3mdev_l3_out() (bsc#1238512).
    - CVE-2025-21796: nfsd: clear acl_access/acl_default after releasing them (bsc#1238716).
    - CVE-2025-21802: net: hns3: fix oops when unload drivers paralleling (bsc#1238751).
    - CVE-2025-21821: fbdev: omap: use threaded IRQ for LCD DMA (bsc#1239174).
    - CVE-2025-21831: PCI: Avoid putting some root ports into D3 on TUXEDO Sirius Gen1 (bsc#1239039).
    - CVE-2025-21846: acct: perform last write from workqueue (bsc#1239508).
    - CVE-2025-21848: nfp: bpf: Add check for nfp_app_ctrl_msg_alloc() (bsc#1239479).
    - CVE-2025-21865: gtp: Suppress list corruption splat in gtp_net_exit_batch_rtnl() (bsc#1239481).
    - CVE-2025-21871: tee: optee: Fix supplicant wait loop (bsc#1240183).
    - CVE-2025-21877: usbnet: gl620a: fix endpoint checking in genelink_bind() (bsc#1240172).
    - CVE-2025-21891: ipvlan: ensure network headers are in skb linear part (bsc#1240186).
    - CVE-2025-21916: usb: atm: cxacru: fix a flaw in existing endpoint checks (bsc#1240582).
    - CVE-2025-21922: ppp: Fix KMSAN uninit-value warning with bpf (bsc#1240639).
    - CVE-2025-21934: rapidio: fix an API misues when rio_add_net() fails (bsc#1240708).
    - CVE-2025-21935: rapidio: add check for rio_add_net() in rio_scan_alloc_net() (bsc#1240700).
    - CVE-2025-21969: Bluetooth: L2CAP: Fix build errors in some archs (bsc#1240784).
    - CVE-2025-21993: iscsi_ibft: Fix UBSAN shift-out-of-bounds warning in ibft_attr_show_nic() (bsc#1240797).
    - CVE-2025-21996: drm/radeon: fix uninitialized size issue in radeon_vce_cs_parse() (bsc#1240801).
    - CVE-2025-22007: Bluetooth: Fix error code in chan_alloc_skb_cb() (bsc#1240582).


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	名称	产品	系列	发布时间	最近更新时间	严重程度
225618	Linux Distros 未修補的弱點：CVE-2022-49337	Nessus	Misc.	2025/3/5	2026/7/17	medium
225618	Linux Distros 未修补的漏洞：CVE-2022-49337	Nessus	Misc.	2025/3/5	2026/7/17	medium
233410	SUSE SLES15 セキュリティ更新 : kernel (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	2025/3/27	2026/6/26	high
234407	SUSE SLES15 セキュリティ更新 : kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	2025/4/15	2026/6/26	high
225618	Linux Distros のパッチ未適用の脆弱性: CVE-2022-49337	Nessus	Misc.	2025/3/5	2026/7/17	medium
234545	SUSE SLES12 セキュリティ更新 : kernel (SUSE-SU-2025:1293-1)	Nessus	SuSE Local Security Checks	2025/4/17	2026/6/25	high
273215	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-989092)	Nessus	Unity Linux Local Security Checks	2025/11/5	2025/11/5	medium
151965	Photon OS 4.0: Linux PHSA-2021-4.0-0065	Nessus	PhotonOS Local Security Checks	2021/7/22	2026/3/23	high
274317	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-990391)	Nessus	Unity Linux Local Security Checks	2025/11/6	2025/11/6	medium
234407	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	2025/4/15	2026/6/26	high
272471	Unity Linux 20.1050e Security Update: kernel (UTSA-2025-990167)	Nessus	Unity Linux Local Security Checks	2025/11/5	2025/11/5	medium
271060	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-987619)	Nessus	Unity Linux Local Security Checks	2025/10/21	2025/10/21	medium
233410	SUSE SLES15: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	2025/3/27	2026/6/26	high
225618	Linux Distros Unpatched Vulnerability : CVE-2022-49337	Nessus	Misc.	2025/3/5	2026/7/17	medium
234545	SUSE SLES12: cluster-md-kmp-default / dlm-kmp-default / gfs2-kmp-default / etc (SUSE-SU-2025:1293-1)	Nessus	SuSE Local Security Checks	2025/4/17	2026/6/25	high

检测

插件搜索

medium

medium

high

high

medium

high

medium

high

medium

high

medium

medium

high

medium

high