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: bpf: Fix may_goto with negative     offset. Zac's syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto     is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when     current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite     loop. It's not correct to prune exploration of the program at this point. Note, that this check doesn't     limit the program to only one may_goto insn, since 2nd and any further may_goto will increment     may_goto_depth only in the queued state pushed for future exploration. The current state will have     may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program     until bpf_exit. (CVE-2024-42072)

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

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

  - Linux カーネルでは、以下の脆弱性が解決されています: bpf: Fix may_goto with negative offset. Zac's syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It's not correct to prune exploration of the program at this point. Note, that this check doesn't limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit. (CVE-2024-42072)

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

远程 Azure Linux 3.0 主机上安装的内核版本低于 测试的版本。因此，该程序受到 CVE-2024-42072 公告中提及的一个漏洞影响。

  - 已修复 Linux 内核中的下列漏洞：bpf: Fix may_goto with negative offset. Zac's syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It's not correct to prune exploration of the program at this point. Note, that this check doesn't limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit. (CVE-2024-42072)

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

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

  - 已解決 Linux 核心中的下列弱點：bpf: Fix may_goto with negative offset. Zac's syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It's not correct to prune exploration of the program at this point. Note, that this check doesn't limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit. (CVE-2024-42072)

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

遠端 Azure Linux 3.0 主機上安裝的核心版本比測試版舊。因此，此版本會受到 CVE-2024-42072 公告中提及的一個弱點影響。

  - 已解決 Linux 核心中的下列弱點：bpf: Fix may_goto with negative offset. Zac's syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It's not correct to prune exploration of the program at this point. Note, that this check doesn't limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit. (CVE-2024-42072)

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

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

  - 已修复 Linux 内核中的下列漏洞：bpf: Fix may_goto with negative offset. Zac's syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It's not correct to prune exploration of the program at this point. Note, that this check doesn't limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit. (CVE-2024-42072)

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

リモートの Azure Linux 3.0 ホストにインストールされているカーネルのバージョンは、テスト済みのバージョンより前です。したがって、CVE-2024-42072 のアドバイザリに記載されている脆弱性の影響を受けます。

  - Linux カーネルでは、以下の脆弱性が解決されています: bpf: Fix may_goto with negative offset. Zac's syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite loop. It's not correct to prune exploration of the program at this point. Note, that this check doesn't limit the program to only one may_goto insn, since 2nd and any further may_goto will increment may_goto_depth only in the queued state pushed for future exploration. The current state will have may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program until bpf_exit. (CVE-2024-42072)

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

The version of kernel installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-42072 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Fix may_goto with negative     offset. Zac's syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto     is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when     current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite     loop. It's not correct to prune exploration of the program at this point. Note, that this check doesn't     limit the program to only one may_goto insn, since 2nd and any further may_goto will increment     may_goto_depth only in the queued state pushed for future exploration. The current state will have     may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program     until bpf_exit. (CVE-2024-42072)

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

The version of kernel installed on the remote Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-42072 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: bpf: Fix may_goto with negative     offset. Zac's syzbot crafted a bpf prog that exposed two bugs in may_goto. The 1st bug is the way may_goto     is patched. When offset is negative it should be patched differently. The 2nd bug is in the verifier: when     current state may_goto_depth is equal to visited state may_goto_depth it means there is an actual infinite     loop. It's not correct to prune exploration of the program at this point. Note, that this check doesn't     limit the program to only one may_goto insn, since 2nd and any further may_goto will increment     may_goto_depth only in the queued state pushed for future exploration. The current state will have     may_goto_depth == 0 regardless of number of may_goto insns and the verifier has to explore the program     until bpf_exit. (CVE-2024-42072)

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

ID	Name	Product	Family	Published	Updated	Severity
244200	Linux Distros Unpatched Vulnerability : CVE-2024-42072	Nessus	Misc.	8/6/2025	8/6/2025	high
244200	Linux Distros のパッチ未適用の脆弱性: CVE-2024-42072	Nessus	Misc.	8/6/2025	8/6/2025	high
215820	Azure Linux 3.0 安全更新内核 (CVE-2024-42072)	Nessus	Azure Linux Local Security Checks	2/10/2025	2/10/2025	high
244200	Linux Distros 未修補的弱點：CVE-2024-42072	Nessus	Misc.	8/6/2025	8/6/2025	high
215820	Azure Linux 3.0 安全性更新核心 (CVE-2024-42072)	Nessus	Azure Linux Local Security Checks	2/10/2025	2/10/2025	high
244200	Linux Distros 未修补的漏洞：CVE-2024-42072	Nessus	Misc.	8/6/2025	8/6/2025	high
215820	Azure Linux 3.0 セキュリティ更新カーネルCVE-2024-42072	Nessus	Azure Linux Local Security Checks	2/10/2025	2/10/2025	high
205369	CBL Mariner 2.0 Security Update: kernel (CVE-2024-42072)	Nessus	MarinerOS Local Security Checks	8/11/2024	2/10/2025	high
215820	Azure Linux 3.0 Security Update: kernel (CVE-2024-42072)	Nessus	Azure Linux Local Security Checks	2/10/2025	2/10/2025	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high

high

high