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

  - bpf: Infer zext_dst based on static register liveness analysis As reported in the thread [1], the     verifier's 32-bit operations zero extension logic is broken. This logic is responsible for correct     semantics of 32-bit operations on s390 architecture. According to BPF semantics, operation `w1 += 1` is     supposed to zero extend the upper half of the register `r1`. On s390 the JIT relies on the verifier     emitting explicit zero extension before such operations. The verifier attempts to minimize the amount of     zero extensions inserted by tracking whether upper halves of the 64-bit registers are ever used.
    Previously such tracking worked as follows: - bpf_reg_state->subreg_def field was set by do_check_insn()     for each operation defining lower but not the upper halves of the register. - Whenever an operation     reading the whole register was verified, the verifier checked register's subreg_def and set     bpf_insn_aux_data->zext_dst flag as true via a call to mark_insn_zext() function. - After the verification     was complete, a special pass bpf_opt_subreg_zext_lo32_rnd_hi32() extended 32-bit operations with     bpf_insn_aux_data->zext_dst set as true by adding explicit zero extension. Note that the logic above     relies on bpf_reg_state->subreg_def, which is a property of a current verifier state. Before the commit     [2] two additional steps happened: - The verifier tracked upper and lower register halves' liveness as     flags REG_LIVE_READ{32,64} in bpf_reg_state->live. - The function propagate_liveness() called     mark_insn_zext() in order to transfer the knowledge about which registers have their upper halves alive     (and thus might require zero extension). The commit [2] removed the two steps described above, hence     making possible a situation like below: - The register's upper half is set and is used on some     verification path P1 and the register happens not to be marked as precise. - The checkpoint C is created     while processing some instruction between register initialization and usage. - On some other verification     path P2 the register's upper half is not initialized and that path ends hitting the checkpoint C. - In     such a case the register's initialization on path P2 would lack zext_dst mark, making it possible for the     program to inject an arbitrary value in the register's upper half. This commit replaces subreg_def based     logic with computing zext_dst statically, as a part of the bpf_compute_live_registers() analysis: - The     analysis now tracks usage of upper and lower halves of the registers separately. - If some instruction     defines a 32-bit subregister, but not the whole register, *and* the upper half of the register is alive     after that instruction, the instruction is marked as zext_dst. There is one notable drop in precision:
    whenever a BPF subprogram is called, all 64 bits of parameter registers are presumed to be used. The     assumption is that such a drop in precision would not inflict a noticeable performance penalty. [1]     https://lore.kernel.org/bpf/CAGKGUv=sOuqQtA1Ub-5JXfA4FPosJFYKAQE4B79cK+P1erxqtg@mail.gmail.com/ [2] commit     107e16979905 (bpf: disable and remove registers chain based liveness) (CVE-2026-98869)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2026-98869

high Nessus Plugin ID 370051

Version 1.8

Version 1.7

Version 1.6

Version 1.5

Version 1.4

Version 1.3

Version 1.2

Version 1.1

Version 1.8 Nov 12, 2026, 7:08 AM CVSS metrics ("CVSSv2 score" set to 2.1. "CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:N/C:N/I:P/A:N") CVSSv2 severity (based on CVE-2026-98869, severity decreased from "Medium" to "Low") Detection (updated detection logic) Plugin metadata Plugin Feed: 202611120708
Version 1.7 Oct 30, 2026, 8:32 AM CVSS metrics ("CVSSv2 score" set to 6.8) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C") CVSSv2 severity (based on CVE-2026-98869, severity increased from "Low" to "Medium") Plugin Feed: 202610300832
Version 1.6 Oct 29, 2026, 7:21 AM CVSS metrics ("CVSSv2 score" set to 2.1) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:N/C:N/I:P/A:N") CVSSv2 severity (based on CVE-2026-98869, severity decreased from "Medium" to "Low") Detection (updated detection logic) Plugin metadata Plugin Feed: 202610290721
Version 1.5 Oct 26, 2026, 8:43 AM CVSS metrics ("CVSSv2 score" set to 6.8) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C") CVSSv2 severity (based on CVE-2026-98869, severity increased from "Low" to "Medium") Plugin Feed: 202610260843
Version 1.4 Oct 24, 2026, 11:07 PM CVSS metrics ("CVSSv3 score" set to 7.8) CVSS metrics ("CVSSv3 vector" set to "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H") CVSSv3 severity (based on None, severity increased from "Low" to "High") Detection (updated detection logic) Plugin metadata Plugin Feed: 202610242307
Version 1.3 Oct 23, 2026, 5:56 PM Detection (updated detection logic) Plugin metadata Plugin Feed: 202610231756
Version 1.2 Oct 23, 2026, 11:36 AM CVSS metrics ("CVSSv2 score" set to 2.1) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:N/C:N/I:P/A:N") CVSS metrics ("CVSSv3 score" set to 3.3) CVSS metrics ("CVSSv3 vector" set to "CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N") CVSSv2 severity (based on CVE-2026-98869, severity decreased from "High" to "Low") CVSSv3 severity (based on None, severity decreased from "High" to "Low") Detection (updated detection logic) Plugin metadata Plugin Feed: 202610231136
Version 1.1 Oct 22, 2026, 12:02 AM New Plugin Feed: 202610220002