Skip to main content
VulnerabilityPublished Updated

CVE-2026-64427: Linux kernel · HID: logitech-dj: Fix maxfield check in DJ short report validation

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f3790a6af9c7f47d454225cab9dc145270e48f62 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in f3790a6af9c7f47d454225cab9dc145270e48f62, 1215febd644c3e16f77e0f1799d89544dd57a754, 590cc4d782487632a52f37c2171bee1eeea29627 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 7754ade02d0fb1caf20392baf4e02937378fd136, < f3790a6af9c7f47d454225cab9dc145270e48f62
Fixed in
  • f3790a6af9c7f47d454225cab9dc145270e48f62
LinuxLinuxAffected
  • ≥ 2ed9638cfbf9d49bdef9b0f5ee547236c2c2f500, < 1215febd644c3e16f77e0f1799d89544dd57a754
Fixed in
  • 1215febd644c3e16f77e0f1799d89544dd57a754
LinuxLinuxAffected
  • ≥ b6a57912854e7ea36f3b270032661140cc4209cd, < 590cc4d782487632a52f37c2171bee1eeea29627
Fixed in
  • 590cc4d782487632a52f37c2171bee1eeea29627
LinuxLinuxAffected
  • ≥ 968e84f5c0dca4960580d174500e4bbf0c45dc15, < 95b3f23d632490b5eb285b9fcf7284f2ac8f9872
Fixed in
  • 95b3f23d632490b5eb285b9fcf7284f2ac8f9872
LinuxLinuxAffected
  • ≥ ce2a731c179df8869e1969a1b2b5b9e4e1c25f8b, < 80c1e18473f63fd7c6a2bc9ad6f3d0a6cc4fb500
Fixed in
  • 80c1e18473f63fd7c6a2bc9ad6f3d0a6cc4fb500
LinuxLinuxAffected
  • ≥ b6a57912854e7ea36f3b270032661140cc4209cd, < 7a89ad762fad53d56b7002d7ffc923a4b7f4006f
Fixed in
  • 7a89ad762fad53d56b7002d7ffc923a4b7f4006f

Description

In the Linux kernel, the following vulnerability has been resolved: HID: logitech-dj: Fix maxfield check in DJ short report validation Commit b6a57912854e ("HID: logitech-dj: Prevent REPORT_ID_DJ_SHORT related user initiated OOB write") added validation for the DJ short output report, but the error path dereferences rep->field[0] even when rep->maxfield is zero. Commit 8b9a097eb2fc ("HID: logitech-dj: fix wrong detection of bad DJ_SHORT output report") made the check conditional on rep being present, but a crafted descriptor can still create report ID 0x20 with only padding output items. hid-core registers the report, ignores the padding field, and leaves rep->maxfield as zero. In that case the validation enters the rep->maxfield < 1 branch and then dereferences rep->field[0]->report_count while printing the error message, causing a NULL pointer dereference during probe. This is reproducible with uhid by emulating a Logitech receiver with a padding-only DJ short output report: BUG: KASAN: null-ptr-deref in logi_dj_probe+0xb1/0x754 [hid_logitech_dj] Read of size 4 at addr 0000000000000028 by task kworker/4:1/129 ... Call Trace: logi_dj_probe+0xb1/0x754 [hid_logitech_dj] hid_device_probe+0x329/0x3f0 [hid] really_probe+0x162/0x570 __device_attach+0x137/0x2c0 bus_probe_device+0x38/0xc0 device_add+0xa56/0xce0 hid_add_device+0x19c/0x280 [hid] uhid_device_add_worker+0x2c/0xb0 [uhid] Reject the zero-field report before printing the field report_count.

References

Community reviews

Loading reviews…