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

  - bpf: Do mark_chain_precision for ARG_CONST_ALLOC_SIZE_OR_ZERO Precision markers need to be propagated     whenever we have an ARG_CONST_* style argument, as the verifier cannot consider imprecise scalars to be     equivalent for the purposes of states_equal check when such arguments refine the return value (in this     case, set mem_size for PTR_TO_MEM). The resultant mem_size for the R0 is derived from the constant value,     and if the verifier incorrectly prunes states considering them equivalent where such arguments exist (by     seeing that both registers have reg->precise as false in regsafe), we can end up with invalid programs     passing the verifier which can do access beyond what should have been the correct mem_size in that     explored state. To show a concrete example of the problem: 0000000000000000 <prog>: 0: r2 = *(u32 *)(r1 +     80) 1: r1 = *(u32 *)(r1 + 76) 2: r3 = r1 3: r3 += 4 4: if r3 > r2 goto +18 <LBB5_5> 5: w2 = 0 6: *(u32
    *)(r1 + 0) = r2 7: r1 = *(u32 *)(r1 + 0) 8: r2 = 1 9: if w1 == 0 goto +1 <LBB5_3> 10: r2 = -1     0000000000000058 <LBB5_3>: 11: r1 = 0 ll 13: r3 = 0 14: call bpf_ringbuf_reserve 15: if r0 == 0 goto +7     <LBB5_5> 16: r1 = r0 17: r1 += 16777215 18: w2 = 0 19: *(u8 *)(r1 + 0) = r2 20: r1 = r0 21: r2 = 0 22:
    call bpf_ringbuf_submit 00000000000000b8 <LBB5_5>: 23: w0 = 0 24: exit For the first case, the single line     execution's exploration will prune the search at insn 14 for the branch insn 9's second leg as it will be     verified first using r2 = -1 (UINT_MAX), while as w1 at insn 9 will always be 0 so at runtime we don't get     error for being greater than UINT_MAX/4 from bpf_ringbuf_reserve. The verifier during regsafe just sees     reg->precise as false for both r2 registers in both states, hence considers them equal for purposes of     states_equal. If we propagated precise markers using the backtracking support, we would use the precise     marking to then ensure that old r2 (UINT_MAX) was within the new r2 (1) and this would never be true, so     the verification would rightfully fail. The end result is that the out of bounds access at instruction 19     would be permitted without this fix. Note that reg->precise is always set to true when user does not have     CAP_BPF (or when subprog count is greater than 1 (i.e. use of any static or global functions)), hence this     is only a problem when precision marks need to be explicitly propagated (i.e. privileged users with     CAP_BPF). A simplified test case has been included in the next patch to prevent future regressions.
    (CVE-2022-49961)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2022-49961

high Nessus Plugin ID 245820

Version 1.21

Version 1.20

Version 1.19

Version 1.18

Version 1.17

Version 1.16

Version 1.15

Version 1.14

Version 1.13

Version 1.12

Version 1.10

Version 1.9

Version 1.8

Version 1.7

Version 1.6

Version 1.5

Version 1.21 Aug 1, 2026, 6:58 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202608010658
Version 1.20 Aug 1, 2026, 2:26 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202608010226
Version 1.19 Jul 29, 2026, 9:32 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202607292132
Version 1.18 Jul 25, 2026, 6:18 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202607250618
Version 1.17 Jul 21, 2026, 12:41 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202607210041
Version 1.16 Jul 16, 2026, 9:04 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202607162104
Version 1.15 Jul 6, 2026, 4:58 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202607060458
Version 1.14 Jul 2, 2026, 3:38 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202607021538
Version 1.13 Jun 30, 2026, 12:42 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202606300042
Version 1.12 Jun 28, 2026, 7:50 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202606280750
Version 1.10 May 15, 2026, 12:01 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202605151201
Version 1.9 Feb 7, 2026, 12:50 AM Detection (updated detection logic) Plugin metadata Plugin Feed: 202602070050
Version 1.8 Jan 16, 2026, 10:12 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202601162212
Version 1.7 Jan 10, 2026, 7:58 PM CVSS metrics ("CVSSv3 score" set to 7.1) CVSS metrics ("CVSSv3 vector" set to "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H") CVSSv3 severity (based on None, severity increased from "Medium" to "High") Detection (updated detection logic) Plugin metadata Plugin Feed: 202601101958
Version 1.6 Oct 29, 2025, 3:03 AM Detection (updated detection logic) Plugin Feed: 202510290303
Version 1.5 Oct 27, 2025, 11:56 PM CVSS temporal metrics ("CVSSv2 temporal vector" set to "CVSS2#E:U/RL:U/RC:C") CVSS temporal metrics ("CVSSv3 temporal vector" set to "CVSS:3.0/E:U/RL:U/RC:C") Detection (updated detection logic) Plugin Feed: 202510272356