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.

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.

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.

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.

ID	Name	Product	Family	Severity
244200	Linux Distros Unpatched Vulnerability : CVE-2024-42072	Nessus	Misc.	high
215820	Azure Linux 3.0 Security Update: kernel (CVE-2024-42072)	Nessus	Azure Linux Local Security Checks	high
205369	CBL Mariner 2.0 Security Update: kernel (CVE-2024-42072)	Nessus	MarinerOS Local Security Checks	high

Detections

Analytics

CVE-2024-42072

high

Tenable Plugins

high

high

high