Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2026-64427

Published Jul 25, 2026 EPSS 0.18% (7th pctl)

Overview

CVE-2026-64427 is a known-severity vulnerability. It was published on July 25, 2026.

Technical 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:

B

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Ref git.kernel.org/stable/c/1215febd644c3e16f77e0f1799d89544dd57a754 Ref git.kernel.org/stable/c/2b70bebc709489d29a31ac2935aeffb8d5228395 Ref git.kernel.org/stable/c/590cc4d782487632a52f37c2171bee1eeea29627 Ref git.kernel.org/stable/c/6f7f22a8d244c2e586b8eb61c7585784b62aea01 Ref git.kernel.org/stable/c/7a89ad762fad53d56b7002d7ffc923a4b7f4006f Ref git.kernel.org/stable/c/80c1e18473f63fd7c6a2bc9ad6f3d0a6cc4fb500 Ref git.kernel.org/stable/c/95b3f23d632490b5eb285b9fcf7284f2ac8f9872 Ref git.kernel.org/stable/c/f3790a6af9c7f47d454225cab9dc145270e48f62

Frequently Asked Questions

What is CVE-2026-64427?

CVE-2026-64427 is a known-severity vulnerability. It was published on July 25, 2026.

How severe is CVE-2026-64427?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-64427?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-64427?

CyberStrike's AI-powered security agents can automatically detect CVE-2026-64427 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.

How CyberStrike Helps

Autonomous Discovery

AI agents map your attack surface to find vulnerabilities like this one.
Continuous Pentesting

Automated penetration testing that runs continuously, not just quarterly.
Code Review

AI-driven PR review catches vulnerable dependencies before they ship.
HackBrowser

Browser-based exploitation validates findings with real proof-of-concept.
Browse by year 2026 2025 2024 2023 2022 2021 2020 2019 2018 2017 2016 2015 2014 2013 2012 2011 2010 2009 2008 2007 2006 2005 2004 2003 2002 2001 2000 1999