CVE-2026-64427

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

July 25, 2026

Last Modified

August 19, 2026

References (8)

Vendor Advisories for CVE-2026-64427(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions)7.1.4-1—

Data Freshness Timeline

(refreshed 6× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:04 UTCGHSA enrichment
  3. 2026-08-28 21:42 UTCEPSS rescore
  4. 2026-08-26 14:47 UTCEPSS rescore
  5. 2026-08-25 13:49 UTCEPSS rescore
  6. 2026-08-25 10:31 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-22 13:59 UTCGHSA enrichment
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 17:27 UTCGHSA enrichment
  12. 2026-08-19 17:21 UTCNVD update
  13. 2026-08-19 17:04 UTCEPSS rescore
  14. 2026-08-19 16:57 UTCGHSA enrichment
  15. 2026-08-19 16:43 UTCMITRE cvelistV5
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 05:43 UTCGHSA enrichment
  18. 2026-08-17 05:25 UTCNVD update
  19. 2026-08-17 05:17 UTCGHSA enrichment
  20. 2026-08-17 05:05 UTCMITRE cvelistV5
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-15 01:30 UTCEPSS rescore
  23. 2026-08-14 11:37 UTCGHSA enrichment
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-12 13:51 UTCEPSS rescore
Show 36 more
  1. 2026-08-11 15:06 UTCGHSA enrichment
  2. 2026-08-11 00:00 UTCEPSS rescore
  3. 2026-08-09 19:20 UTCGHSA enrichment
  4. 2026-08-09 19:19 UTCNVD update
  5. 2026-08-09 18:41 UTCGHSA enrichment
  6. 2026-08-09 18:41 UTCMITRE cvelistV5
  7. 2026-08-09 09:33 UTCGHSA enrichment
  8. 2026-08-08 16:37 UTCEPSS rescore
  9. 2026-08-06 13:47 UTCEPSS rescore
  10. 2026-08-06 13:01 UTCGHSA enrichment
  11. 2026-08-05 19:17 UTCEPSS rescore
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-04 15:10 UTCEPSS rescore
  14. 2026-08-04 10:39 UTCEPSS rescore
  15. 2026-08-03 16:30 UTCGHSA enrichment
  16. 2026-08-03 10:36 UTCEPSS rescore
  17. 2026-08-02 02:27 UTCEPSS rescore
  18. 2026-08-01 04:16 UTCEPSS rescore
  19. 2026-07-31 19:59 UTCEG score recompute
  20. 2026-07-31 19:58 UTCGHSA enrichment
  21. 2026-07-30 16:28 UTCEPSS rescore
  22. 2026-07-30 01:30 UTCEPSS rescore
  23. 2026-07-30 01:30 UTCEPSS rescore
  24. 2026-07-28 23:26 UTCEG score recompute
  25. 2026-07-28 23:25 UTCGHSA enrichment
  26. 2026-07-28 15:37 UTCEPSS rescore
  27. 2026-07-27 14:14 UTCEPSS rescore
  28. 2026-07-26 14:54 UTCEPSS rescore
  29. 2026-07-26 14:54 UTCEPSS rescore
  30. 2026-07-26 02:47 UTCEG score recompute
  31. 2026-07-26 02:47 UTCGHSA enrichment
  32. 2026-07-25 14:18 UTCEPSS rescore
  33. 2026-07-25 14:18 UTCEPSS rescore
  34. 2026-07-25 10:39 UTCNVD update
  35. 2026-07-25 09:29 UTCEG score recompute
  36. 2026-07-25 09:21 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64427?
CVE-2026-64427 is a publicly disclosed vulnerability published on July 25, 2026. 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 REPORTIDDJ_SHORT related user initiated OOB write") added validation for the DJ short output report, but the error…
When was CVE-2026-64427 disclosed?
CVE-2026-64427 was first published in the National Vulnerability Database on July 25, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64427 actively exploited?
CVE-2026-64427 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.7% of all scored CVEs.
How do I remediate CVE-2026-64427?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64427, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64427

Explore →

Is Your Infrastructure Affected by CVE-2026-64427?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs