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

  - HID: wacom: validate report length in wacom_intuos_pro2_bt_irq wacom_intuos_pro2_bt_irq() receives the     wire report length in `len` but never consults it before parsing. After the report-id gate it     unconditionally calls wacom_intuos_pro2_bt_pen() and then, selected by features.type, a fixed chain of     sub-parsers, none of which receive `len`: wacom_intuos_pro2_bt_pen(wacom); if (type == INTUOSP2_BT || type     == INTUOSP2S_BT) { wacom_intuos_pro2_bt_touch(wacom); wacom_intuos_pro2_bt_pad(wacom);
    wacom_intuos_pro2_bt_battery(wacom); } else { wacom_intuos_gen3_bt_pad(wacom);
    wacom_intuos_gen3_bt_battery(wacom); } Each sub-parser dereferences wacom->data at fixed offsets. The     furthest byte touched on each branch is: INTUOSP2_BT / INTUOSP2S_BT: wacom_intuos_pro2_bt_pad() reads     data[285] (the touchring byte), so the report must be at least 286 bytes; INTUOSHT3_BT (gen3):
    wacom_intuos_gen3_bt_battery() reads data[45], so the report must be at least 46 bytes. features.type is     selected from the VID/PID id_table entry and wacom_setup_device_quirks() force-registers the pen/pad/touch     inputs for that type independent of the report descriptor, so a malicious or malfunctioning paired/spoofed     Bluetooth peripheral can advertise that VID/PID and send an undersized report that still satisfies the     data[0] == 0x80/0x81 gate. The driver then reads past the received report and forwards the bytes to     userspace via evdev (MSC_SERIAL / ABS_MISC / ABS_WHEEL on the pen and pad input nodes), an out-of-bounds     read with a concrete userspace read-back channel, and a true out-of-bounds read on transports whose     backing buffer is sized to the (small) report descriptor rather than a fixed-size staging buffer. This is     the same class of bug commit 2f1763f62909 (HID: wacom: fix out-of-bounds read in wacom_intuos_bt_irq)     already hardened in the sibling wacom_intuos_bt_irq(), which guards each report id against its minimum     length before parsing. Guard wacom_intuos_pro2_bt_irq() the same way: before parsing, reject reports     shorter than the furthest offset the selected branch actually dereferences, warn, and bail out. Because     the whole pen/touch/pad/ battery chain runs unconditionally per branch, a single up-front check against     the maximum offset (286 bytes for INTUOSP2_BT/INTUOSP2S_BT, 46 bytes for the gen3 branch) bounds every     sub-parser. Returning 0 on a short report also skips those calls for the same malformed report, which is     the safe, conservative behavior. (CVE-2026-89999)

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

Detections

Analytics

Linux Distros Unpatched Vulnerability : CVE-2026-89999

high Nessus Plugin ID 346723

Version 1.4

Version 1.2

Version 1.1

Version 1.4 Sep 18, 2026, 2:17 PM CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:A/AC:L/Au:N/C:C/I:N/A:C") CVSSv2 severity (based on CVE-2026-89999, severity increased from "Low" to "High") Detection (updated detection logic) Plugin metadata Plugin Feed: 202609181417
Version 1.2 Sep 18, 2026, 12:24 AM CVSS metrics ("CVSSv2 score" set to 3.6) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:N/C:P/I:N/A:P") CVSSv2 severity (based on CVE-2026-89999, severity decreased from "High" to "Low") Detection (updated detection logic) Plugin metadata Plugin Feed: 202609180024
Version 1.1 Sep 17, 2026, 12:32 PM New Plugin Feed: 202609171232