CVE-2026-64273

NameCVE-2026-64273
DescriptionIn the Linux kernel, the following vulnerability has been resolved: Input: iforce - bound the device-reported force-feedback effect index iforce_process_packet() handles a status report (packet id 0x02) by taking a force-feedback effect index straight from the device wire and using it to address the per-effect state array: i = data[1] & 0x7f; if (data[1] & 0x80) { if (!test_and_set_bit(FF_CORE_IS_PLAYED, iforce->core_effects[i].flags)) ... } else if (test_and_clear_bit(FF_CORE_IS_PLAYED, iforce->core_effects[i].flags)) { ... } The index is masked only with 0x7f, so it ranges 0..127, but core_effects[] holds only IFORCE_EFFECTS_MAX (32) entries. For an index of 32..127 the test_and_set_bit()/test_and_clear_bit() is an out-of-bounds single-bit read-modify-write past the array. core_effects[] is the second-to-last member of struct iforce, so the write lands in the trailing members and beyond the embedding kzalloc()'d iforce_serio / iforce_usb object. data[1] is unvalidated device payload on both transports (the USB interrupt endpoint and serio), and the status path is not gated on force feedback being present, so a malicious or counterfeit device can set or clear a bit at an attacker-chosen offset past the object. Reject an out-of-range index instead of indexing with it. Bound against the array dimension IFORCE_EFFECTS_MAX rather than dev->ff->max_effects so the check guarantees memory safety regardless of how many effects the device registered. A legitimate "effect started/stopped" status always carries an index below IFORCE_EFFECTS_MAX, so well-formed devices are unaffected; the neighbouring mark_core_as_ready() loop is already bounded and is left untouched.
SourceCVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
ReferencesDLA-4717-1, DLA-4720-1, DLA-4723-1, DLA-4724-1

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
linux (PTS)bullseye5.10.223-1vulnerable
bullseye (security)5.10.262-1fixed
bookworm6.1.176-1vulnerable
bookworm (security)6.1.180-1fixed
trixie6.12.94-1vulnerable
trixie (security)6.12.101-1fixed
forky7.1.7-1fixed
sid7.1.8-1fixed
linux-6.1 (PTS)bullseye (security)6.1.180-1~deb11u1fixed
linux-6.12 (PTS)bookworm (security)6.12.100-1~deb12u1fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
linuxsourcebullseye5.10.262-1DLA-4717-1
linuxsourcebookworm6.1.180-1DLA-4720-1
linuxsourcetrixie6.12.96-1
linuxsource(unstable)7.1.4-1
linux-6.1sourcebullseye6.1.180-1~deb11u1DLA-4723-1
linux-6.12sourcebookworm6.12.100-1~deb12u1DLA-4724-1

Notes

https://git.kernel.org/linus/0e9943d2e4c63496b6ca84bc66fd3c71d40558e2 (7.2-rc1)

Search for package or bug name: Reporting problems