HID: picolcd: clamp eeprom debugfs read to bytes actually received
Noroxi assessment
Priority: Monitor (action score 0/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.22% (FIRST EPSS).
- Fixed version: Linux Linux 1a02056c2bf7ef9b5fd05ee6913aeeadb703c443, 471f4a939c66d1d44aece2321807abf609fc9098, 4daf432c94a42e7be6aa10b012b33af5ed9bc118; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 1a02056c2bf7ef9b5fd05ee6913aeeadb703c443, 471f4a939c66d1d44aece2321807abf609fc9098, 4daf432c94a42e7be6aa10b012b33af5ed9bc118; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 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: picolcd: clamp eeprom debugfs read to bytes actually received picolcd_debug_eeprom_read() trusts resp->raw_data[2] -- a length byte supplied by the device in its REPORT_EE_DATA reply -- clamped only to the caller's read() count: ret = resp->raw_data[2]; if (ret > s) ret = s; if (copy_to_user(u, resp->raw_data+3, ret)) It never checks resp->raw_size, the number of bytes picolcd_raw_event() actually copied into the 64-byte raw_data[] of the kmalloc'd struct picolcd_pending. A device (or a spoofed picoLCD) returning a length byte of 0xff, read with a count >= 255, makes copy_to_user() read past raw_data[] into adjacent slab memory and return it to userspace through the debugfs "eeprom" file: BUG: KASAN: slab-out-of-bounds in _copy_to_user Read of size 255 ... picolcd_debug_eeprom_read+0x214/0x2f0 [hid_picolcd] The debug-dump path in the same file already validates the device length byte against the received size before trusting it; this read does not. The file is created S_IRUSR (root-only) and a crafted device is needed, so it is neither unprivileged- nor remotely-triggerable. Clamp the copy length to resp->raw_size - 3 (the payload actually received, minus the 3-byte header), floored at 0 for short replies.
- Published
- Sep 11, 2026
- Updated
- Sep 14, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
—
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
- 2.6.35affected
- 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba and later · before 1a02056c2bf7ef9b5fd05ee6913aeeadb703c443affected · git
- 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba and later · before 65daa322f1021d8206f8032c4cd4c0cb2d26c7c3affected · git
- 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba and later · before 8dc662af019158690c470edd2e2857657f700abbaffected · git
- 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba and later · before 4daf432c94a42e7be6aa10b012b33af5ed9bc118affected · git
- 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba and later · before a3e6e8d7198a9f3861861520a38b673684a1062baffected · git
- 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba and later · before 471f4a939c66d1d44aece2321807abf609fc9098affected · git
- 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba and later · before 699a3c8b56e168ca19d12722f3f5ef1d6f4b1d84affected · git
- 9bbf2b98ba11d00bd73e3254e15cfe17ccaff6ba and later · before e9c667395ac1f8024f623250b32bae4c7af9caa0affected · git
- before 2.6.35not 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:12 | linux | all versions | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-72421ipv4: fib: Don't ignore error route in local/main tables.40Plan
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
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 | 1a02056c2bf7ef9b5fd05ee6913aeeadb703c443 | Vendor (CNA) |
| Linux Linux | 471f4a939c66d1d44aece2321807abf609fc9098 | Vendor (CNA) |
| Linux Linux | 4daf432c94a42e7be6aa10b012b33af5ed9bc118 | Vendor (CNA) |
| Linux Linux | 65daa322f1021d8206f8032c4cd4c0cb2d26c7c3 | Vendor (CNA) |
| Linux Linux | 699a3c8b56e168ca19d12722f3f5ef1d6f4b1d84 | Vendor (CNA) |
| Linux Linux | 8dc662af019158690c470edd2e2857657f700abb | Vendor (CNA) |
| Linux Linux | a3e6e8d7198a9f3861861520a38b673684a1062b | Vendor (CNA) |
| Linux Linux | e9c667395ac1f8024f623250b32bae4c7af9caa0 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1085 · Sep 14, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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/471f4a939c66d1d44aece2321807abf609fc9098
- git.kernel.org/stable/c/4daf432c94a42e7be6aa10b012b33af5ed9bc118
- git.kernel.org/stable/c/65daa322f1021d8206f8032c4cd4c0cb2d26c7c3
- git.kernel.org/stable/c/699a3c8b56e168ca19d12722f3f5ef1d6f4b1d84
- git.kernel.org/stable/c/8dc662af019158690c470edd2e2857657f700abb
- git.kernel.org/stable/c/a3e6e8d7198a9f3861861520a38b673684a1062b
- git.kernel.org/stable/c/e9c667395ac1f8024f623250b32bae4c7af9caa0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.