In the Linux kernel, the following vulnerability has been resolved: HID: core: Fix assumption that Resolution Multipliers must be in Logical Collections A report in 2019 by the syzbot fuzzer was found to be connected to two errors in the HID core associated with Resolution Multipliers. One of the errors was fixed by commit ea427a222d8b ("HID: core: Fix deadloop in hid_apply_multiplier."), but the other has not been fixed. This error arises because hid_apply_multipler() assumes that every Resolution Multiplier control is contained in a Logical Collection, i.e., there's no way the routine can ever set multiplier_collection to NULL. This is in spite of the fact that the function starts with a big comment saying: * "The Resolution Multiplier control must be contained in the same * Logical Collection as the control(s) to which it is to be applied. ... * If no Logical Collection is * defined, the Resolution Multiplier is associated with all * controls in the report." * HID Usage Table, v1.12, Section 4.3.1, p30 * * Thus, search from the current collection upwards until we find a * logical collection... The comment and the code overlook the possibility that none of the collections found may be a Logical Collection. The fix is to set the multiplier_collection pointer to NULL if the collection found isn't a Logical Collection.

The remote Debian 11 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-4102 advisory.

    -------------------------------------------------------------------------     Debian LTS Advisory DLA-4102-1                debian-lts@lists.debian.org     https://www.debian.org/lts/security/                        Ben Hutchings     March 31, 2025                                https://wiki.debian.org/LTS
    -------------------------------------------------------------------------

    Package        : linux-6.1     Version        : 6.1.129-1~deb11u1     CVE ID         : CVE-2024-26596 CVE-2024-40945 CVE-2024-42069 CVE-2024-42122                      CVE-2024-45001 CVE-2024-47726 CVE-2024-49989 CVE-2024-50061                      CVE-2024-54458 CVE-2024-56549 CVE-2024-57834 CVE-2024-57973                      CVE-2024-57978 CVE-2024-57979 CVE-2024-57980 CVE-2024-57981                      CVE-2024-57986 CVE-2024-57993 CVE-2024-57996 CVE-2024-57997                      CVE-2024-57998 CVE-2024-58001 CVE-2024-58007 CVE-2024-58009                      CVE-2024-58010 CVE-2024-58011 CVE-2024-58013 CVE-2024-58014                      CVE-2024-58016 CVE-2024-58017 CVE-2024-58020 CVE-2024-58034                      CVE-2024-58051 CVE-2024-58052 CVE-2024-58054 CVE-2024-58055                      CVE-2024-58056 CVE-2024-58058 CVE-2024-58061 CVE-2024-58063                      CVE-2024-58068 CVE-2024-58069 CVE-2024-58071 CVE-2024-58072                      CVE-2024-58076 CVE-2024-58077 CVE-2024-58080 CVE-2024-58083                      CVE-2024-58085 CVE-2024-58086 CVE-2025-21684 CVE-2025-21700                      CVE-2025-21701 CVE-2025-21703 CVE-2025-21704 CVE-2025-21705                      CVE-2025-21706 CVE-2025-21707 CVE-2025-21708 CVE-2025-21711                      CVE-2025-21715 CVE-2025-21716 CVE-2025-21718 CVE-2025-21719                      CVE-2025-21722 CVE-2025-21724 CVE-2025-21725 CVE-2025-21726                      CVE-2025-21727 CVE-2025-21728 CVE-2025-21731 CVE-2025-21734                      CVE-2025-21735 CVE-2025-21736 CVE-2025-21738 CVE-2025-21744                      CVE-2025-21745 CVE-2025-21748 CVE-2025-21749 CVE-2025-21750                      CVE-2025-21753 CVE-2025-21758 CVE-2025-21760 CVE-2025-21761                      CVE-2025-21762 CVE-2025-21763 CVE-2025-21764 CVE-2025-21765                      CVE-2025-21766 CVE-2025-21767 CVE-2025-21772 CVE-2025-21775                      CVE-2025-21776 CVE-2025-21779 CVE-2025-21780 CVE-2025-21781                      CVE-2025-21782 CVE-2025-21785 CVE-2025-21787 CVE-2025-21790                      CVE-2025-21791 CVE-2025-21792 CVE-2025-21794 CVE-2025-21795                      CVE-2025-21796 CVE-2025-21799 CVE-2025-21802 CVE-2025-21804                      CVE-2025-21806 CVE-2025-21811 CVE-2025-21812 CVE-2025-21814                      CVE-2025-21819 CVE-2025-21820 CVE-2025-21821 CVE-2025-21823                      CVE-2025-21826 CVE-2025-21829 CVE-2025-21830 CVE-2025-21832                      CVE-2025-21835     Debian Bug     : 1071562 1087807 1088159 1091517 1091858 1093371 1095435                      1095745 1095764 1098250 1098354 1099138

    Several vulnerabilities have been discovered in the Linux kernel that     may lead to a privilege escalation, denial of service or information     leaks.

    For Debian 11 bullseye, these problems have been fixed in version     6.1.129-1~deb11u1.  This additionally includes many more bug fixes     from stable update 6.1.129, and a fix for a regression affecting some     Rockchip SoCs.

    We recommend that you upgrade your linux-6.1 packages.

    For the detailed security status of linux-6.1 please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/linux-6.1

    Further information about Debian LTS security advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://wiki.debian.org/LTS     Attachment:
    signature.asc     Description: PGP signature

Tenable has extracted the preceding description block directly from the Debian security advisory.

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

An update of the linux package has been released.

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: HID: core: Fix assumption that     Resolution Multipliers must be in Logical Collections A report in 2019 by the syzbot fuzzer was found to     be connected to two errors in the HID core associated with Resolution Multipliers. One of the errors was     fixed by commit ea427a222d8b (HID: core: Fix deadloop in hid_apply_multiplier.), but the other has not     been fixed. This error arises because hid_apply_multipler() assumes that every Resolution Multiplier     control is contained in a Logical Collection, i.e., there's no way the routine can ever set     multiplier_collection to NULL. This is in spite of the fact that the function starts with a big comment     saying: * The Resolution Multiplier control must be contained in the same * Logical Collection as the     control(s) to which it is to be applied. ... * If no Logical Collection is * defined, the Resolution     Multiplier is associated with all * controls in the report. * HID Usage Table, v1.12, Section 4.3.1, p30
    * * Thus, search from the current collection upwards until we find a * logical collection... The comment     and the code overlook the possibility that none of the collections found may be a Logical Collection. The     fix is to set the multiplier_collection pointer to NULL if the collection found isn't a Logical     Collection. (CVE-2024-57986)

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

ID	Name	Product	Family	Severity
233595	Debian dla-4102 : linux-config-6.1 - security update	Nessus	Debian Local Security Checks	high
233213	Photon OS 4.0: Linux PHSA-2025-4.0-0771	Nessus	PhotonOS Local Security Checks	high
232764	Photon OS 5.0: Linux PHSA-2025-5.0-0486	Nessus	PhotonOS Local Security Checks	high
230926	Linux Distros Unpatched Vulnerability : CVE-2024-57986	Nessus	Misc.	high

Detections

Analytics

CVE-2024-57986

high

Tenable Plugins

high

high

high

high