CVE-2026-64427: HID: logitech-dj: Fix maxfield check in DJ short report validation
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 1215febd644c3e16f77e0f1799d89544dd57a754, 2b70bebc709489d29a31ac2935aeffb8d5228395, 590cc4d782487632a52f37c2171bee1eeea29627.
Low priority for now. Upgrade to Linux Linux 1215febd644c3e16f77e0f1799d89544dd57a754, 2b70bebc709489d29a31ac2935aeffb8d5228395, 590cc4d782487632a52f37c2171bee1eeea29627 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 25, 2026
- Updated
- Sep 4, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel7.1 and later · before 7.1.4
- linux linux kernel7.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 7.1affected
- 7754ade02d0fb1caf20392baf4e02937378fd136 and later · before f3790a6af9c7f47d454225cab9dc145270e48f62affected · git
- 2ed9638cfbf9d49bdef9b0f5ee547236c2c2f500 and later · before 1215febd644c3e16f77e0f1799d89544dd57a754affected · git
- eeb5ad388595ca2b6624689198a057847f3a3e19 and later · before 6f7f22a8d244c2e586b8eb61c7585784b62aea01affected · git
- 968e84f5c0dca4960580d174500e4bbf0c45dc15 and later · before 95b3f23d632490b5eb285b9fcf7284f2ac8f9872affected · git
- ce2a731c179df8869e1969a1b2b5b9e4e1c25f8b and later · before 80c1e18473f63fd7c6a2bc9ad6f3d0a6cc4fb500affected · git
- bc3bba4656ad280267ea78cf845ab6b1d95b9fcd and later · before 2b70bebc709489d29a31ac2935aeffb8d5228395affected · git
- b6a57912854e7ea36f3b270032661140cc4209cd and later · before 7a89ad762fad53d56b7002d7ffc923a4b7f4006faffected · git
- b6a57912854e7ea36f3b270032661140cc4209cd and later · before 590cc4d782487632a52f37c2171bee1eeea29627affected · git
- before 7.1not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64424Jul 25, 2026 · netpoll: fix a use-after-free on shutdown path31Monitor
- ← EarlierCVE-2026-64426Jul 25, 2026 · io_uring/nop: fix file reference leak with IOSQE_FIXED_FILE22Monitor
- Later →CVE-2026-64428Jul 25, 2026 · gpio: sch: use raw_spinlock_t in the irq startup path22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1215febd644c3e16f77e0f1799d89544dd57a754 | Vendor (CNA) |
| Linux Linux | 2b70bebc709489d29a31ac2935aeffb8d5228395 | Vendor (CNA) |
| Linux Linux | 590cc4d782487632a52f37c2171bee1eeea29627 | Vendor (CNA) |
| Linux Linux | 6f7f22a8d244c2e586b8eb61c7585784b62aea01 | Vendor (CNA) |
| Linux Linux | 7a89ad762fad53d56b7002d7ffc923a4b7f4006f | Vendor (CNA) |
| Linux Linux | 80c1e18473f63fd7c6a2bc9ad6f3d0a6cc4fb500 | Vendor (CNA) |
| Linux Linux | 95b3f23d632490b5eb285b9fcf7284f2ac8f9872 | Vendor (CNA) |
| Linux Linux | f3790a6af9c7f47d454225cab9dc145270e48f62 | Vendor (CNA) |
| debian:linux | 7.1.4-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/2b70bebc709489d29a31ac2935aeffb8d5228395
- git.kernel.org/stable/c/590cc4d782487632a52f37c2171bee1eeea29627
- git.kernel.org/stable/c/6f7f22a8d244c2e586b8eb61c7585784b62aea01
- git.kernel.org/stable/c/7a89ad762fad53d56b7002d7ffc923a4b7f4006f
- git.kernel.org/stable/c/80c1e18473f63fd7c6a2bc9ad6f3d0a6cc4fb500
- git.kernel.org/stable/c/95b3f23d632490b5eb285b9fcf7284f2ac8f9872
- git.kernel.org/stable/c/f3790a6af9c7f47d454225cab9dc145270e48f62
Vendor advisories and official records. Exploit/PoC links are deliberately left out.