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

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

    blk-iolatency: Fix inflight count imbalances and IO hangs on offline

    iolatency needs to track the number of inflight IOs per cgroup. As this     tracking can be expensive, it is disabled when no cgroup has iolatency     configured for the device. To ensure that the inflight counters stay     balanced, iolatency_set_limit() freezes the request_queue while manipulating     the enabled counter, which ensures that no IO is in flight and thus all     counters are zero.

    Unfortunately, iolatency_set_limit() isn't the only place where the enabled     counter is manipulated. iolatency_pd_offline() can also dec the counter and     trigger disabling. As this disabling happens without freezing the q, this     can easily happen while some IOs are in flight and thus leak the counts.

    This can be easily demonstrated by turning on iolatency on an one empty     cgroup while IOs are in flight in other cgroups and then removing the     cgroup. Note that iolatency shouldn't have been enabled elsewhere in the     system to ensure that removing the cgroup disables iolatency for the whole     device.

    The following keeps flipping on and off iolatency on sda:

      echo +io > /sys/fs/cgroup/cgroup.subtree_control       while true; do           mkdir -p /sys/fs/cgroup/test           echo '8:0 target=100000' > /sys/fs/cgroup/test/io.latency           sleep 1           rmdir /sys/fs/cgroup/test           sleep 1       done

    and there's concurrent fio generating direct rand reads:

      fio --name test --filename=/dev/sda --direct=1 --rw=randread \
          --runtime=600 --time_based --iodepth=256 --numjobs=4 --bs=4k

    while monitoring with the following drgn script:

      while True:
        for css in css_for_each_descendant_pre(prog['blkcg_root'].css.address_of_()):
            for pos in hlist_for_each(container_of(css, 'struct blkcg', 'css').blkg_list):
                blkg = container_of(pos, 'struct blkcg_gq', 'blkcg_node')                 pd = blkg.pd[prog['blkcg_policy_iolatency'].plid]                 if pd.value_() == 0:
                    continue                 iolat = container_of(pd, 'struct iolatency_grp', 'pd')                 inflight = iolat.rq_wait.inflight.counter.value_()                 if inflight:
                    print(f'inflight={inflight} {disk_name(blkg.q.disk).decode(utf-8)} '                           f'{cgroup_path(css.cgroup).decode(utf-8)}')         time.sleep(1)

    The monitoring output looks like the following:

      inflight=1 sda /user.slice       inflight=1 sda /user.slice       ...
      inflight=14 sda /user.slice       inflight=13 sda /user.slice       inflight=17 sda /user.slice       inflight=15 sda /user.slice       inflight=18 sda /user.slice       inflight=17 sda /user.slice       inflight=20 sda /user.slice       inflight=19 sda /user.slice <- fio stopped, inflight stuck at 19       inflight=19 sda /user.slice       inflight=19 sda /user.slice

    If a cgroup with stuck inflight ends up getting throttled, the throttled IOs     will never get issued as there's no completion event to wake it up leading     to an indefinite hang.

    This patch fixes the bug by unifying enable handling into a work item which     is automatically kicked off from iolatency_set_min_lat_nsec() which is     called from both iolatency_set_limit() and iolatency_pd_offline() paths.
    Punting to a work item is necessary as iolatency_pd_offline() is called     under spinlocks while freezing a request_queue requires a sleepable context.

    This also simplifies the code reducing LOC sans the comments and avoids the     unnecessary freezes which were happening whenever a cgroup's latency target     is newly set or cleared.

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.

  - In the Linux kernel, the following vulnerability has been resolved: blk-iolatency: Fix inflight count     imbalances and IO hangs on offline iolatency needs to track the number of inflight IOs per cgroup. As this     tracking can be expensive, it is disabled when no cgroup has iolatency configured for the device. To     ensure that the inflight counters stay balanced, iolatency_set_limit() freezes the request_queue while     manipulating the enabled counter, which ensures that no IO is in flight and thus all counters are zero.
    Unfortunately, iolatency_set_limit() isn't the only place where the enabled counter is manipulated.
    iolatency_pd_offline() can also dec the counter and trigger disabling. As this disabling happens without     freezing the q, this can easily happen while some IOs are in flight and thus leak the counts. This can be     easily demonstrated by turning on iolatency on an one empty cgroup while IOs are in flight in other     cgroups and then removing the cgroup. Note that iolatency shouldn't have been enabled elsewhere in the     system to ensure that removing the cgroup disables iolatency for the whole device. The following keeps     flipping on and off iolatency on sda: echo +io > /sys/fs/cgroup/cgroup.subtree_control while true; do     mkdir -p /sys/fs/cgroup/test echo '8:0 target=100000' > /sys/fs/cgroup/test/io.latency sleep 1 rmdir     /sys/fs/cgroup/test sleep 1 done and there's concurrent fio generating direct rand reads: fio --name test
    --filename=/dev/sda --direct=1 --rw=randread \ --runtime=600 --time_based --iodepth=256 --numjobs=4
    --bs=4k while monitoring with the following drgn script: while True: for css in     css_for_each_descendant_pre(prog['blkcg_root'].css.address_of_()): for pos in     hlist_for_each(container_of(css, 'struct blkcg', 'css').blkg_list): blkg = container_of(pos, 'struct     blkcg_gq', 'blkcg_node') pd = blkg.pd[prog['blkcg_policy_iolatency'].plid] if pd.value_() == 0: continue     iolat = container_of(pd, 'struct iolatency_grp', 'pd') inflight = iolat.rq_wait.inflight.counter.value_()     if inflight: print(f'inflight={inflight} {disk_name(blkg.q.disk).decode(utf-8)} '     f'{cgroup_path(css.cgroup).decode(utf-8)}') time.sleep(1) The monitoring output looks like the     following: inflight=1 sda /user.slice inflight=1 sda /user.slice ... inflight=14 sda /user.slice     inflight=13 sda /user.slice inflight=17 sda /user.slice inflight=15 sda /user.slice inflight=18 sda     /user.slice inflight=17 sda /user.slice inflight=20 sda /user.slice inflight=19 sda /user.slice <- fio     stopped, inflight stuck at 19 inflight=19 sda /user.slice inflight=19 sda /user.slice If a cgroup with     stuck inflight ends up getting throttled, the throttled IOs will never get issued as there's no completion     event to wake it up leading to an indefinite hang. This patch fixes the bug by unifying enable handling     into a work item which is automatically kicked off from iolatency_set_min_lat_nsec() which is called from     both iolatency_set_limit() and iolatency_pd_offline() paths. Punting to a work item is necessary as     iolatency_pd_offline() is called under spinlocks while freezing a request_queue requires a sleepable     context. This also simplifies the code reducing LOC sans the comments and avoids the unnecessary freezes     which were happening whenever a cgroup's latency target is newly set or cleared. (CVE-2022-49394)

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

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

  - Linux カーネルでは、以下の脆弱性が解決されています: blk-iolatency: Fix inflight count imbalances and IO hangs on offline iolatency needs to track the number of inflight IOs per cgroup. As this tracking can be expensive, it is disabled when no cgroup has iolatency configured for the device. To ensure that the inflight counters stay balanced, iolatency_set_limit() freezes the request_queue while manipulating the enabled counter, which ensures that no IO is in flight and thus all counters are zero.
    Unfortunately, iolatency_set_limit() isn't the only place where the enabled counter is manipulated.
    iolatency_pd_offline() can also dec the counter and trigger disabling. As this disabling happens without freezing the q, this can easily happen while some IOs are in flight and thus leak the counts. This can be easily demonstrated by turning on iolatency on an one empty cgroup while IOs are in flight in other cgroups and then removing the cgroup. Note that iolatency shouldn't have been enabled elsewhere in the system to ensure that removing the cgroup disables iolatency for the whole device. The following keeps flipping on and off iolatency on sda: echo +io > /sys/fs/cgroup/cgroup.subtree_control while true; do mkdir -p /sys/fs/cgroup/test echo '8:0 target=100000' > /sys/fs/cgroup/test/io.latency sleep 1 rmdir /sys/fs/cgroup/test sleep 1 done and there's concurrent fio generating direct rand reads: fio --name test
    --filename=/dev/sda --direct=1 --rw=randread \ --runtime=600 --time_based --iodepth=256 --numjobs=4
    --bs=4k while monitoring with the following drgn script: while True: for css in css_for_each_descendant_pre(prog['blkcg_root'].css.address_of_()): for pos in hlist_for_each(container_of(css, 'struct blkcg', 'css').blkg_list): blkg = container_of(pos, 'struct blkcg_gq', 'blkcg_node') pd = blkg.pd[prog['blkcg_policy_iolatency'].plid] if pd.value_() == 0: continue iolat = container_of(pd, 'struct iolatency_grp', 'pd') inflight = iolat.rq_wait.inflight.counter.value_() if inflight: print(f'inflight={inflight} {disk_name(blkg.q.disk).decode(utf-8)} ' f'{cgroup_path(css.cgroup).decode(utf-8)}') time.sleep(1) The monitoring output looks like the following: inflight=1 sda /user.slice inflight=1 sda /user.slice ... inflight=14 sda /user.slice inflight=13 sda /user.slice inflight=17 sda /user.slice inflight=15 sda /user.slice inflight=18 sda /user.slice inflight=17 sda /user.slice inflight=20 sda /user.slice inflight=19 sda /user.slice <- fio stopped, inflight stuck at 19 inflight=19 sda /user.slice inflight=19 sda /user.slice If a cgroup with stuck inflight ends up getting throttled, the throttled IOs will never get issued as there's no completion event to wake it up leading to an indefinite hang. This patch fixes the bug by unifying enable handling into a work item which is automatically kicked off from iolatency_set_min_lat_nsec() which is called from both iolatency_set_limit() and iolatency_pd_offline() paths. Punting to a work item is necessary as iolatency_pd_offline() is called under spinlocks while freezing a request_queue requires a sleepable context. This also simplifies the code reducing LOC sans the comments and avoids the unnecessary freezes which were happening whenever a cgroup's latency target is newly set or cleared. (CVE-2022-49394)

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

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

  - 已修复 Linux 内核中的下列漏洞：blk-iolatency: Fix inflight count imbalances and IO hangs on offline iolatency needs to track the number of inflight IOs per cgroup. As this tracking can be expensive, it is disabled when no cgroup has iolatency configured for the device. To ensure that the inflight counters stay balanced, iolatency_set_limit() freezes the request_queue while manipulating the enabled counter, which ensures that no IO is in flight and thus all counters are zero.
    Unfortunately, iolatency_set_limit() isn't the only place where the enabled counter is manipulated.
    iolatency_pd_offline() can also dec the counter and trigger disabling. As this disabling happens without freezing the q, this can easily happen while some IOs are in flight and thus leak the counts. This can be easily demonstrated by turning on iolatency on an one empty cgroup while IOs are in flight in other cgroups and then removing the cgroup. Note that iolatency shouldn't have been enabled elsewhere in the system to ensure that removing the cgroup disables iolatency for the whole device. The following keeps flipping on and off iolatency on sda: echo +io > /sys/fs/cgroup/cgroup.subtree_control while true; do mkdir -p /sys/fs/cgroup/test echo '8:0 target=100000' > /sys/fs/cgroup/test/io.latency sleep 1 rmdir /sys/fs/cgroup/test sleep 1 done and there's concurrent fio generating direct rand reads: fio --name test
    --filename=/dev/sda --direct=1 --rw=randread \ --runtime=600 --time_based --iodepth=256 --numjobs=4
    --bs=4k while monitoring with the following drgn script: while True: for css in css_for_each_descendant_pre(prog['blkcg_root'].css.address_of_()): for pos in hlist_for_each(container_of(css, 'struct blkcg', 'css').blkg_list): blkg = container_of(pos, 'struct blkcg_gq', 'blkcg_node') pd = blkg.pd[prog['blkcg_policy_iolatency'].plid] if pd.value_() == 0: continue iolat = container_of(pd, 'struct iolatency_grp', 'pd') inflight = iolat.rq_wait.inflight.counter.value_() if inflight: print(f'inflight={inflight} {disk_name(blkg.q.disk).decode(utf-8)} ' f'{cgroup_path(css.cgroup).decode(utf-8)}') time.sleep(1) The monitoring output looks like the following: inflight=1 sda /user.slice inflight=1 sda /user.slice ... inflight=14 sda /user.slice inflight=13 sda /user.slice inflight=17 sda /user.slice inflight=15 sda /user.slice inflight=18 sda /user.slice inflight=17 sda /user.slice inflight=20 sda /user.slice inflight=19 sda /user.slice <- fio stopped, inflight stuck at 19 inflight=19 sda /user.slice inflight=19 sda /user.slice If a cgroup with stuck inflight ends up getting throttled, the throttled IOs will never get issued as there's no completion event to wake it up leading to an indefinite hang. This patch fixes the bug by unifying enable handling into a work item which is automatically kicked off from iolatency_set_min_lat_nsec() which is called from both iolatency_set_limit() and iolatency_pd_offline() paths. Punting to a work item is necessary as iolatency_pd_offline() is called under spinlocks while freezing a request_queue requires a sleepable context. This also simplifies the code reducing LOC sans the comments and avoids the unnecessary freezes which were happening whenever a cgroup's latency target is newly set or cleared. (CVE-2022-49394)

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

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

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

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

    - CVE-2021-47248：udp：close() と udp_abort() の間の競合を修正します（bsc#1224867）。
    - CVE-2022-49051：net：usb：aqc111：RX 修正で領域外アクセスを修正します（bsc#1237903）。
    - CVE-2022-49053：scsi：target：tcmu：潜在的なページ UAF を修正します（bsc#1237918）。
    - CVE-2022-49275：can：m_can：m_can_tx_handler()：skb の use-after-free を修正します（bsc#1238719）。
    - CVE-2022-49413：bfq：bio をマージする前に cgroup 情報を更新します（bsc#1238710）。
    - CVE-2022-49465：blk-throttle：bio が調整されているときに BIO_THROTTLED を設定します（bsc#1238919）。
    - CVE-2022-49545：ALSA：usb-audio：MIDI サブストリームを閉じる際に保留中の作業をキャンセルします（bsc#1238729）。
    - CVE-2022-49563：crypto：qat - RSA 用のパラメーターチェックを追加します（bsc#1238787）。
    - CVE-2022-49564：crypto：qat - DH に対するパラメーターチェックを追加します（bsc#1238789）。
    - CVE-2022-49739：gfs2：インライン inode の inode サイズを常にチェックします（bsc#1240207）。
    - CVE-2023-52935：mm/khugepaged：->anon_vma の競合を修正します（bsc#1240276）。
    - CVE-2024-56642: tipc: cleanup_bearer() のカーネルソケットのメモリ解放後使用 (Use After Free) を修正します (bsc#1235433)。
    - 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-58014: wifi: brcmsmac: wlc_phy_iqcal_gainparams_nphy() にゲイン範囲チェックを追加しました (bsc#1239109)。
    - CVE-2025-21772：パーティション：mac：偽造パーティションテーブルの処理を修正します（bsc#1238911）。
    - CVE-2025-21780: drm/amdgpu: smu_sys_set_pp_table() のバッファオーバーフローのアタッチを回避します (bsc#1239115)。


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

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

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

  - 已解決 Linux 核心中的下列弱點：blk-iolatency: Fix inflight count imbalances and IO hangs on offline iolatency needs to track the number of inflight IOs per cgroup. As this tracking can be expensive, it is disabled when no cgroup has iolatency configured for the device. To ensure that the inflight counters stay balanced, iolatency_set_limit() freezes the request_queue while manipulating the enabled counter, which ensures that no IO is in flight and thus all counters are zero.
    Unfortunately, iolatency_set_limit() isn't the only place where the enabled counter is manipulated.
    iolatency_pd_offline() can also dec the counter and trigger disabling. As this disabling happens without freezing the q, this can easily happen while some IOs are in flight and thus leak the counts. This can be easily demonstrated by turning on iolatency on an one empty cgroup while IOs are in flight in other cgroups and then removing the cgroup. Note that iolatency shouldn't have been enabled elsewhere in the system to ensure that removing the cgroup disables iolatency for the whole device. The following keeps flipping on and off iolatency on sda: echo +io > /sys/fs/cgroup/cgroup.subtree_control while true; do mkdir -p /sys/fs/cgroup/test echo '8:0 target=100000' > /sys/fs/cgroup/test/io.latency sleep 1 rmdir /sys/fs/cgroup/test sleep 1 done and there's concurrent fio generating direct rand reads: fio --name test
    --filename=/dev/sda --direct=1 --rw=randread \ --runtime=600 --time_based --iodepth=256 --numjobs=4
    --bs=4k while monitoring with the following drgn script: while True: for css in css_for_each_descendant_pre(prog['blkcg_root'].css.address_of_()): for pos in hlist_for_each(container_of(css, 'struct blkcg', 'css').blkg_list): blkg = container_of(pos, 'struct blkcg_gq', 'blkcg_node') pd = blkg.pd[prog['blkcg_policy_iolatency'].plid] if pd.value_() == 0: continue iolat = container_of(pd, 'struct iolatency_grp', 'pd') inflight = iolat.rq_wait.inflight.counter.value_() if inflight: print(f'inflight={inflight} {disk_name(blkg.q.disk).decode(utf-8)} ' f'{cgroup_path(css.cgroup).decode(utf-8)}') time.sleep(1) The monitoring output looks like the following: inflight=1 sda /user.slice inflight=1 sda /user.slice ... inflight=14 sda /user.slice inflight=13 sda /user.slice inflight=17 sda /user.slice inflight=15 sda /user.slice inflight=18 sda /user.slice inflight=17 sda /user.slice inflight=20 sda /user.slice inflight=19 sda /user.slice <- fio stopped, inflight stuck at 19 inflight=19 sda /user.slice inflight=19 sda /user.slice If a cgroup with stuck inflight ends up getting throttled, the throttled IOs will never get issued as there's no completion event to wake it up leading to an indefinite hang. This patch fixes the bug by unifying enable handling into a work item which is automatically kicked off from iolatency_set_min_lat_nsec() which is called from both iolatency_set_limit() and iolatency_pd_offline() paths. Punting to a work item is necessary as iolatency_pd_offline() is called under spinlocks while freezing a request_queue requires a sleepable context. This also simplifies the code reducing LOC sans the comments and avoids the unnecessary freezes which were happening whenever a cgroup's latency target is newly set or cleared. (CVE-2022-49394)

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

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

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

    blk-iolatency: Fix inflight count imbalances and IO hangs on offline

    iolatency needs to track the number of inflight IOs per cgroup. As this     tracking can be expensive, it is disabled when no cgroup has iolatency     configured for the device. To ensure that the inflight counters stay     balanced, iolatency_set_limit() freezes the request_queue while manipulating     the enabled counter, which ensures that no IO is in flight and thus all     counters are zero.

    Unfortunately, iolatency_set_limit() isn't the only place where the enabled     counter is manipulated. iolatency_pd_offline() can also dec the counter and     trigger disabling. As this disabling happens without freezing the q, this     can easily happen while some IOs are in flight and thus leak the counts.

    This can be easily demonstrated by turning on iolatency on an one empty     cgroup while IOs are in flight in other cgroups and then removing the     cgroup. Note that iolatency shouldn't have been enabled elsewhere in the     system to ensure that removing the cgroup disables iolatency for the whole     device.

    The following keeps flipping on and off iolatency on sda:

      echo +io > /sys/fs/cgroup/cgroup.subtree_control       while true; do           mkdir -p /sys/fs/cgroup/test           echo '8:0 target=100000' > /sys/fs/cgroup/test/io.latency           sleep 1           rmdir /sys/fs/cgroup/test           sleep 1       done

    and there's concurrent fio generating direct rand reads:

      fio --name test --filename=/dev/sda --direct=1 --rw=randread \
          --runtime=600 --time_based --iodepth=256 --numjobs=4 --bs=4k

    while monitoring with the following drgn script:

      while True:
        for css in css_for_each_descendant_pre(prog['blkcg_root'].css.address_of_()):
            for pos in hlist_for_each(container_of(css, 'struct blkcg', 'css').blkg_list):
                blkg = container_of(pos, 'struct blkcg_gq', 'blkcg_node')                 pd = blkg.pd[prog['blkcg_policy_iolatency'].plid]                 if pd.value_() == 0:
                    continue                 iolat = container_of(pd, 'struct iolatency_grp', 'pd')                 inflight = iolat.rq_wait.inflight.counter.value_()                 if inflight:
                    print(f'inflight={inflight} {disk_name(blkg.q.disk).decode(utf-8)} '                           f'{cgroup_path(css.cgroup).decode(utf-8)}')         time.sleep(1)

    The monitoring output looks like the following:

      inflight=1 sda /user.slice       inflight=1 sda /user.slice       ...
      inflight=14 sda /user.slice       inflight=13 sda /user.slice       inflight=17 sda /user.slice       inflight=15 sda /user.slice       inflight=18 sda /user.slice       inflight=17 sda /user.slice       inflight=20 sda /user.slice       inflight=19 sda /user.slice <- fio stopped, inflight stuck at 19       inflight=19 sda /user.slice       inflight=19 sda /user.slice

    If a cgroup with stuck inflight ends up getting throttled, the throttled IOs     will never get issued as there's no completion event to wake it up leading     to an indefinite hang.

    This patch fixes the bug by unifying enable handling into a work item which     is automatically kicked off from iolatency_set_min_lat_nsec() which is     called from both iolatency_set_limit() and iolatency_pd_offline() paths.
    Punting to a work item is necessary as iolatency_pd_offline() is called     under spinlocks while freezing a request_queue requires a sleepable context.

    This also simplifies the code reducing LOC sans the comments and avoids the     unnecessary freezes which were happening whenever a cgroup's latency target     is newly set or cleared.

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-990619 advisory.

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

    blk-iolatency: Fix inflight count imbalances and IO hangs on offline

    iolatency needs to track the number of inflight IOs per cgroup. As this     tracking can be expensive, it is disabled when no cgroup has iolatency     configured for the device. To ensure that the inflight counters stay     balanced, iolatency_set_limit() freezes the request_queue while manipulating     the enabled counter, which ensures that no IO is in flight and thus all     counters are zero.

    Unfortunately, iolatency_set_limit() isn't the only place where the enabled     counter is manipulated. iolatency_pd_offline() can also dec the counter and     trigger disabling. As this disabling happens without freezing the q, this     can easily happen while some IOs are in flight and thus leak the counts.

    This can be easily demonstrated by turning on iolatency on an one empty     cgroup while IOs are in flight in other cgroups and then removing the     cgroup. Note that iolatency shouldn't have been enabled elsewhere in the     system to ensure that removing the cgroup disables iolatency for the whole     device.

    The following keeps flipping on and off iolatency on sda:

      echo +io > /sys/fs/cgroup/cgroup.subtree_control       while true; do           mkdir -p /sys/fs/cgroup/test           echo '8:0 target=100000' > /sys/fs/cgroup/test/io.latency           sleep 1           rmdir /sys/fs/cgroup/test           sleep 1       done

    and there's concurrent fio generating direct rand reads:

      fio --name test --filename=/dev/sda --direct=1 --rw=randread \
          --runtime=600 --time_based --iodepth=256 --numjobs=4 --bs=4k

    while monitoring with the following drgn script:

      while True:
        for css in css_for_each_descendant_pre(prog['blkcg_root'].css.address_of_()):
            for pos in hlist_for_each(container_of(css, 'struct blkcg', 'css').blkg_list):
                blkg = container_of(pos, 'struct blkcg_gq', 'blkcg_node')                 pd = blkg.pd[prog['blkcg_policy_iolatency'].plid]                 if pd.value_() == 0:
                    continue                 iolat = container_of(pd, 'struct iolatency_grp', 'pd')                 inflight = iolat.rq_wait.inflight.counter.value_()                 if inflight:
                    print(f'inflight={inflight} {disk_name(blkg.q.disk).decode(utf-8)} '                           f'{cgroup_path(css.cgroup).decode(utf-8)}')         time.sleep(1)

    The monitoring output looks like the following:

      inflight=1 sda /user.slice       inflight=1 sda /user.slice       ...
      inflight=14 sda /user.slice       inflight=13 sda /user.slice       inflight=17 sda /user.slice       inflight=15 sda /user.slice       inflight=18 sda /user.slice       inflight=17 sda /user.slice       inflight=20 sda /user.slice       inflight=19 sda /user.slice <- fio stopped, inflight stuck at 19       inflight=19 sda /user.slice       inflight=19 sda /user.slice

    If a cgroup with stuck inflight ends up getting throttled, the throttled IOs     will never get issued as there's no completion event to wake it up leading     to an indefinite hang.

    This patch fixes the bug by unifying enable handling into a work item which     is automatically kicked off from iolatency_set_min_lat_nsec() which is     called from both iolatency_set_limit() and iolatency_pd_offline() paths.
    Punting to a work item is necessary as iolatency_pd_offline() is called     under spinlocks while freezing a request_queue requires a sleepable context.

    This also simplifies the code reducing LOC sans the comments and avoids the     unnecessary freezes which were happening whenever a cgroup's latency target     is newly set or cleared.

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:1263-1 advisory.

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

    The following security bugs were fixed:

    - CVE-2021-47248: udp: fix race between close() and udp_abort() (bsc#1224867).
    - 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-49275: can: m_can: m_can_tx_handler(): fix use after free of skb (bsc#1238719).
    - CVE-2022-49413: bfq: Update cgroup information before merging bio (bsc#1238710).
    - CVE-2022-49465: blk-throttle: Set BIO_THROTTLED when bio has been throttled (bsc#1238919).
    - CVE-2022-49545: ALSA: usb-audio: Cancel pending work at closing a MIDI substream (bsc#1238729).
    - 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-49739: gfs2: Always check inode size of inline inodes (bsc#1240207).
    - CVE-2023-52935: mm/khugepaged: fix ->anon_vma race (bsc#1240276).
    - CVE-2024-56642: tipc: Fix use-after-free of kernel socket in cleanup_bearer() (bsc#1235433).
    - 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-58014: wifi: brcmsmac: add gain range check to wlc_phy_iqcal_gainparams_nphy() (bsc#1239109).
    - 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.

遠端 Redhat Enterprise Linux 9 主機上安裝的多個套件受到 RHSA-2022:8267 公告中提及的多個弱點影響。

    核心套件中包含 Linux 核心，後者是任何 Linux 作業系統的核心。

    安全性修正：

    * 路徑外攻擊者可插入資料或終止受害者的 TCP 工作階段 (CVE-2020-36516)

    * 函式 sco_sock_sendmsg() 中的釋放後使用弱點 (CVE-2021-3640)

    * smb2_ioctl_query_info NULL 指標解除參照 (CVE-2022-0168)

    * 回寫期間 udf_expand_file_adinicbdue() 中發生 NULL 指標解除參照 (CVE-2022-0617)

    * 因 DMA_FROM_DEVICE 的 swiotlb 資訊洩漏 (CVE-2022-0854)

    * nft_do_chain 中堆疊上的未初始化暫存器可造成核心指標洩漏至 UM (CVE-2022-1016)

    * snd_pcm_hw_free 中的爭用情形會導致釋放後使用 (CVE-2022-1048)

    * 在損毀的影像上掛載並操作時ext4 中發生釋放後使用和記憶體錯誤 (CVE-2022-1184)

    * drm_setmaster_ioctl 和 drm_mode_getresources 之間的並行釋放後使用 (CVE-2022-1280)

    * pfkey_register 中有核心資訊洩漏問題 (CVE-2022-1353)

    * ath9k_htc_probe_device() 中的釋放後使用問題可造成權限提升 (CVE-2022-1679)

    * x86_emulate_insn 中的 NULL 指標解除參照可能導致 DoS (CVE-2022-1852)

    * fanotify 誤用可導致釋放後使用的 fd_install() (CVE-2022-1998)

    * nf_tables 跨表格潛在釋放後使用可能導致本機權限提升 (CVE-2022-2586)

    * 整數反向溢位導致 reserve_sfa_size() 中的超出邊界寫入 (CVE-2022-2639)

    * packet_recvmsg() 中的 slab 超出邊界存取 (CVE-2022-20368)

    * 不完整的多核心共用緩衝區清理 (即 SBDR) (CVE-2022-21123)

    * 微架構填補緩衝區 (即 SBDS) 的不完整清理 (CVE-2022-21125)

    * 特定特殊暫存器寫入作業中的不完整清理 (即 DRPW) (CVE-2022-21166)

    * 可使用除錯程式將零寫入所選位置 (CVE-2022-21499)

    * AMDRetBleed 任意推測程式碼執行及傳回指示 (CVE-2022-23816、 CVE-2022-29900)

    * AMD分支類型混淆 (非 retbleed) (CVE-2022-23825)

    * IntelPost-barrier 傳回堆疊緩衝區預測 (CVE-2022-26373)

    * drivers/net/can/usb/ems_usb.c 中的 ems_usb_start_xmit 中存在雙重釋放 (CVE-2022-28390)

    * SUNRPC 子系統中的釋放後使用 (CVE-2022-28893)

    * 不當更新 net/sched/cls_u32.c 中的參照計數所導致的釋放後使用 (CVE-2022-29581)

    * IntelRetBleed 任意推測程式碼執行及傳回指示 (CVE-2022-29901)

    * net/netfilter/nfnetlink_queue.c 中 nfqnl_mangle 中的 DoS (CVE-2022-36946)

    * nf_tables 不允許系結至已系結鏈結 (CVE-2022-39190)

    * nfs_atomic_open() 傳回未初始化的資料而非 ENOTDIR (CVE-2022-24448)

    如需安全性問題的詳細資料，包括影響、CVSS 評分、致謝及其他相關資訊，請參閱〈參照〉一節列出的 CVE 頁面。

    其他變更：

    如需有關此發行版本的詳細變更資訊，請參閱可從「參考資料」一節連結的 Red Hat Enterprise Linux 9.1 版本資訊。

Tenable 已直接從 Red Hat Enterprise Linux 安全公告擷取前置描述區塊。

請注意，Nessus 並未測試這些問題，而是僅依據應用程式自我報告的版本號碼作出判斷。

The remote Redhat Enterprise Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2022:8267 advisory.

    The kernel packages contain the Linux kernel, the core of any Linux operating system.

    Security Fix(es):

    * off-path attacker may inject data or terminate victim's TCP session (CVE-2020-36516)

    * use-after-free vulnerability in function sco_sock_sendmsg() (CVE-2021-3640)

    * smb2_ioctl_query_info NULL pointer dereference (CVE-2022-0168)

    * NULL pointer dereference in udf_expand_file_adinicbdue() during writeback (CVE-2022-0617)

    * swiotlb information leak with DMA_FROM_DEVICE (CVE-2022-0854)

    * uninitialized registers on stack in nft_do_chain can cause kernel pointer leakage to UM (CVE-2022-1016)

    * race condition in snd_pcm_hw_free leading to use-after-free (CVE-2022-1048)

    * use-after-free and memory errors in ext4 when mounting and operating on a corrupted image     (CVE-2022-1184)

    * concurrency use-after-free between drm_setmaster_ioctl and drm_mode_getresources (CVE-2022-1280)

    * kernel info leak issue in pfkey_register (CVE-2022-1353)

    * use-after-free in ath9k_htc_probe_device() could cause an escalation of privileges (CVE-2022-1679)

    * NULL pointer dereference in x86_emulate_insn may lead to DoS (CVE-2022-1852)

    * fanotify misuses fd_install() which could lead to use-after-free (CVE-2022-1998)

    * nf_tables cross-table potential use-after-free may lead to local privilege escalation (CVE-2022-2586)

    * integer underflow leads to out-of-bounds write in reserve_sfa_size() (CVE-2022-2639)

    * slab-out-of-bounds access in packet_recvmsg() (CVE-2022-20368)

    * incomplete clean-up of multi-core shared buffers (aka SBDR) (CVE-2022-21123)

    * incomplete clean-up of microarchitectural fill buffers (aka SBDS) (CVE-2022-21125)

    * incomplete clean-up in specific special register write operations (aka DRPW) (CVE-2022-21166)

    * possible to use the debugger to write zero into a location of choice (CVE-2022-21499)

    * AMD: RetBleed Arbitrary Speculative Code Execution with Return Instructions (CVE-2022-23816,     CVE-2022-29900)

    * AMD: Branch Type Confusion (non-retbleed) (CVE-2022-23825)

    * Intel: Post-barrier Return Stack Buffer Predictions (CVE-2022-26373)

    * double free in ems_usb_start_xmit in drivers/net/can/usb/ems_usb.c (CVE-2022-28390)

    * use after free in SUNRPC subsystem (CVE-2022-28893)

    * use-after-free due to improper update of reference count in net/sched/cls_u32.c (CVE-2022-29581)

    * Intel: RetBleed Arbitrary Speculative Code Execution with Return Instructions (CVE-2022-29901)

    * DoS in nfqnl_mangle in net/netfilter/nfnetlink_queue.c (CVE-2022-36946)

    * nf_tables disallow binding to already bound chain (CVE-2022-39190)

    * nfs_atomic_open() returns uninitialized data instead of ENOTDIR (CVE-2022-24448)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    Additional Changes:

    For detailed information on changes in this release, see the Red Hat Enterprise Linux 9.1 Release Notes     linked from the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux 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 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.

远程 Redhat Enterprise Linux 9 主机上安装的程序包受到 RHSA-2022:8267 公告中提及的多个漏洞影响。

    内核程序包中包含 Linux 内核，后者是任何 Linux 操作系统的核心。

    安全修复：

    * 路径外攻击者可注入数据或终止受害者的 TCP 会话 (CVE-2020-36516)

    * 函数 sco_sock_sendmsg() 中存在释放后使用漏洞 (CVE-2021-3640)

    * smb2_ioctl_query_info 空指针取消引用 (CVE-2022-0168)

    * 回写期间 udf_expand_file_adinicb CPU 中发生空指针取消引用 (CVE-2022-0617)

    * DMA_FROM_DEVICE 的 swiotlb 信息泄漏 (CVE-2022-0854)

    * nft_do_chain 中堆栈上未初始化的寄存器可导致内核指针泄漏给 UM (CVE-2022-1016)

    * snd_pcm_hw_free 中的争用条件导致释放后使用 (CVE-2022-1048)

    * 装载损坏的图像并进行操作时 ext4 中存在释放后使用和内存错误 (CVE-2022-1184)

    * drm_setmaster_ioctl 与 drm_mode_getresources 之间的并发释放后使用 (CVE-2022-1280)

    * pfkey_register 中的内核信息泄漏问题 (CVE-2022-1353)

    * ath9k_htc_probe_device() 中的释放后使用可导致权限升级 (CVE-2022-1679)

    * x86_emulate_insn 中的空指针取消引用可能导致 DoSCVE-2022-1852

    * fanotify 滥用 fd_install() 可导致释放后使用 (CVE-2022-1998)

    * nf_tables 跨表潜在的释放后使用可能导致本地权限升级 (CVE-2022-2586)

    * 整数下溢导致 reserve_sfa_size() 中的越界写入 (CVE-2022-2639)

    * packet_recvmsg() 中的 slab 越界访问 (CVE-2022-20368)

    * 多核心共享缓冲区的不完整清理也称为 SBDRCVE-2022-21123

    * 微架构填充缓冲区的不完整清理也称为 SBDS (CVE-2022-21125)

    * 特定的特殊寄存器写入操作中的清理不完整又称为 DRPW (CVE-2022-21166)

    * 可以使用调试程序将零写入所选位置 (CVE-2022-21499)

    * AMD通过返回指令的 RetBleed 任意推测代码执行CVE-2022-23816、 CVE-2022-29900

    * AMD分支类型混淆non-retbleed(CVE-2022-23825)

    * IntelPost-barrier 返回堆栈缓冲区预测 (CVE-2022-26373)

    * drivers/net/can/usb/ems_usb.c 中 ems_usb_start_xmit 中存在的双重释放 (CVE-2022-28390)

    * SUNRPC 子系统中的释放后使用 (CVE-2022-28893)

    * 由于未正确更新 net/sched/cls_u32.c 中的引用计数导致释放后使用 (CVE-2022-29581)

    * IntelRetBleed 含返回指令的任意推测代码执行 (CVE-2022-29901)

    * net/netfilter/nfnetlink_queue.c 中的 nfqnl_mangle 中的 DoS (CVE-2022-36946)

    * nf_tables 不允许绑定到已绑定的链 (CVE-2022-39190)

    * nfs_atomic_open() 返回未初始化的数据而不是 ENOTDIR (CVE-2022-24448)

    有关上述安全问题的更多详细信息，包括其影响、CVSS 得分、致谢，以及其他相关信息，请参阅列于“参考”部分的 CVE 页面。

    其他变更：

    如需有关此发行版本的详细变更信息，请参阅可从“参考”部分链接的 Red Hat Enterprise Linux 9.1 版本说明。

Tenable 已直接从 Red Hat Enterprise Linux 安全公告中提取上述描述块。

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

リモート Redhat Enterprise Linux 9 ホストに、RHSA-2022:8267 アドバイザリに記載されている複数の脆弱性の影響を受けるパッケージがインストールされています。

    カーネルパッケージには、Linux オペレーティングシステムのコアである Linux カーネルが含まれています。

    セキュリティ修正プログラム:

    * オフパス攻撃者がデータを注入するか、被害者の TCP セッションを終了させる可能性がありますCVE-2020-36516

    * 関数 sco_sock_sendmsg() での use-after-free の脆弱性CVE-2021-3640

    * smb2_ioctl_query_info NULL ポインターデリファレンスCVE-2022-0168

    * writeback 中の udf_expand_file_adinicbdue() における NULL ポインターデリファレンスCVE-2022-0617

    * DMA_FROM_DEVICE による swiotlb 情報漏洩CVE-2022-0854

    * nft_do_chain のスタック上の初期化されていないレジスターが、UM へのカーネルポインター漏洩を引き起こす可能性がありますCVE-2022-1016

    * use-after-free につながる snd_pcm_hw_free の競合状態CVE-2022-1048

    * 破損したイメージをマウントし操作する際の ext4 における use-after-free およびメモリエラーCVE-2022-1184

    * drm_setmaster_ioctl と drm_mode_getresources の間の同時実行 use-after-freeCVE-2022-1280

    * pfkey_register のカーネル情報漏洩の問題CVE-2022-1353

    * ath9k_htc_probe_device() の use-after-free は、権限昇格を引き起こす可能性がありますCVE-2022-1679

    * x86_emulate_insn の NULL ポインターデリファレンスにより、DoS が引き起こされる可能性がありますCVE-2022-1852

    * fanotify が fd_install() を誤って使用します。これにより、use-after-free が引き起こされる可能性がありますCVE-2022-1998

    * nf_tables のクロステーブルにおける潜在的な use-after-free により、ローカルの権限昇格が発生する可能性がありますCVE-2022-2586

    * 整数アンダーフローにより、 reserve_sfa_size() での領域外の書き込みが引き起こされますCVE-2022-2639

    * packet_recvmsg() での slab-out-of-bounds アクセスCVE-2022-20368

    * マルチコア共有バッファ別名 SBDR の不完全なクリーンアップCVE-2022-21123

    * マイクロアーキテクチャフィルバッファ別名 SBDSの不完全なクリーンアップCVE-2022-21125

    * 特定の特殊なレジスター書き込み操作別名 DRPWで不完全なクリーンアップCVE-2022-21166

    * デバッガーを使用して、選択したロケーションにゼロを書き込むことが可能ですCVE-2022-21499

    * AMDReturn 命令による任意の投機的コードの実行CVE-2022-23816、 CVE-2022-29900

    * AMDブランチの型の取り違えnon-retbleedCVE-2022-23825

    * IntelPost-barrier Return Stack Buffer PredictionsCVE-2022-26373

    * drivers/net/can/usb/ems_usb.c の ems_usb_start_xmit における二重解放CVE-2022-28390

    * SUNRPC サブシステムでの use-after-freeCVE-2022-28893

    * net/sched/cls_u32.c の参照カウントの不適切な更新による use-after-freeCVE-2022-29581

    * IntelReturn 命令による RetBleed の任意の投機的コードの実行CVE-2022-29901

    * net/netfilter/nfnetlink_queue.c の nfqnl_mangle での DoSCVE-2022-36946

    * nf_tables は、すでにバインドされたチェーンへのバインドを許可しませんCVE-2022-39190

    * nfs_atomic_open() は、ENOTDIR の代わりに、初期化されていないデータを返しますCVE-2022-24448]

    影響、CVSS スコア、謝辞、その他の関連情報を含むセキュリティ問題の詳細については、「参照」セクションに記載されている CVE のページを参照してください。

    追加の変更:

    このリリースの変更に関する詳細については、「参照」セクションからリンクされている Red Hat Enterprise Linux 9.1 リリースノートを参照してください。

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

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
273145	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-988773)	Nessus	Unity Linux Local Security Checks	2025/11/5	2025/11/5	medium
225455	Linux Distros Unpatched Vulnerability : CVE-2022-49394	Nessus	Misc.	2025/3/5	2025/10/28	medium
225455	Linux Distros のパッチ未適用の脆弱性: CVE-2022-49394	Nessus	Misc.	2025/3/5	2025/10/28	medium
225455	Linux Distros 未修补的漏洞：CVE-2022-49394	Nessus	Misc.	2025/3/5	2025/10/28	medium
234484	SUSE SLES15 セキュリティ更新 : kernel (SUSE-SU-2025:1263-1)	Nessus	SuSE Local Security Checks	2025/4/16	2025/9/24	high
225455	Linux Distros 未修補的弱點：CVE-2022-49394	Nessus	Misc.	2025/3/5	2025/10/28	medium
234407	SUSE SLES15 セキュリティ更新 : kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	2025/4/15	2025/10/28	high
273719	Unity Linux 20.1070e Security Update: kernel (UTSA-2025-989782)	Nessus	Unity Linux Local Security Checks	2025/11/5	2025/11/5	medium
234407	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1241-1)	Nessus	SuSE Local Security Checks	2025/4/15	2025/10/28	high
274303	Unity Linux 20.1070a Security Update: kernel (UTSA-2025-990619)	Nessus	Unity Linux Local Security Checks	2025/11/6	2025/11/6	medium
234484	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1263-1)	Nessus	SuSE Local Security Checks	2025/4/16	2025/9/24	high
167620	RHEL 9：核心 (RHSA-2022:8267)	Nessus	Red Hat Local Security Checks	2022/11/16	2025/9/12	high
167620	RHEL 9 : kernel (RHSA-2022:8267)	Nessus	Red Hat Local Security Checks	2022/11/16	2025/9/12	high
233410	SUSE SLES15 Security Update : kernel (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	2025/3/27	2025/9/24	high
167620	RHEL 9：内核 (RHSA-2022:8267)	Nessus	Red Hat Local Security Checks	2022/11/16	2025/9/12	high
167620	RHEL 9 : kernel (RHSA-2022:8267)	Nessus	Red Hat Local Security Checks	2022/11/16	2025/9/12	high
233410	SUSE SLES15 セキュリティ更新 : kernel (SUSE-SU-2025:1027-1)	Nessus	SuSE Local Security Checks	2025/3/27	2025/9/24	high

检测

插件搜索

medium

medium

medium

medium

high

medium

high

medium

high

medium

high

high

high

high

high

high

high