CVE-2026-80918: HID: core: fix number/pointer type confusion on long items
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.18% (FIRST EPSS).
- Fixed version: Linux Linux 1fa1591efd417e39e5e164bebea8ca7a3837c469, 28abce951343fcec26e397610868efa4e1395c3f, 634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 1fa1591efd417e39e5e164bebea8ca7a3837c469, 28abce951343fcec26e397610868efa4e1395c3f, 634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996; 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: core: fix number/pointer type confusion on long items When fetch_item() is called by hid_scan_report() on an item with HID_ITEM_TAG_LONG, it stores a pointer to the item data in item->data.longdata instead of storing a value directly in item->data.{u8/u16/u32}. When item_udata() or item_sdata() encounters such an item, it incorrectly assumes that the item is in short format, and therefore returns the lower part of a kernel pointer reinterpreted as a number. When a HID device is connected whose descriptor contains a HID_GLOBAL_ITEM_TAG_REPORT_SIZE encoded in long format with size=4, this causes the lower half of a kernel pointer to be printed into dmesg as a number, like this: hid (null): invalid report_size 107953555 To fix it, let item_udata() and item_sdata() verify that the item is in short format. Note that this bug only affects hid_scan_report(), while the main parsing pass hid_parse_collections() will always bail out when encountering a long item. Sidenote: There are currently no users of data.longdata; maybe we should just remove any parsing of long-format descriptors as a follow-up.
- Published
- Sep 9, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th 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.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.
—
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
- 3.12affected
- 3dc8fc083dbfeede7b63a0c07581192e97711365 and later · before bed7fe3a936b6bdd84671385951397ca673cf6e7affected · git
- 3dc8fc083dbfeede7b63a0c07581192e97711365 and later · before aec2c2ec87d4ec1f098979f68cd81b29f031c8cbaffected · git
- 3dc8fc083dbfeede7b63a0c07581192e97711365 and later · before 634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996affected · git
- 3dc8fc083dbfeede7b63a0c07581192e97711365 and later · before abec577de5fc16cd5caae42f97cdcd0983c06d66affected · git
- 3dc8fc083dbfeede7b63a0c07581192e97711365 and later · before dd8035dec26e98204d6e4a6e0cee5c4d329b3d7eaffected · git
- 3dc8fc083dbfeede7b63a0c07581192e97711365 and later · before 1fa1591efd417e39e5e164bebea8ca7a3837c469affected · git
- 3dc8fc083dbfeede7b63a0c07581192e97711365 and later · before e60159f5ea60254a5c3de4ea4f2f939f0171031baffected · git
- 3dc8fc083dbfeede7b63a0c07581192e97711365 and later · before e542edada3f79387c0ac2a528cebf01f4ef47df8affected · git
- 3dc8fc083dbfeede7b63a0c07581192e97711365 and later · before 28abce951343fcec26e397610868efa4e1395c3faffected · git
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 | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.107-1 | 6.12.107-1 |
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-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
Published before and after this one in the same product
- ← EarlierCVE-2026-80916Sep 9, 2026 · kcov: fix data corruption and race conditions on PREEMPT_RT0Monitor
- ← EarlierCVE-2026-80917Sep 9, 2026 · PCI: host-generic: Fix NULL pointer dereference on 32-bit CAM systems0Monitor
- Later →CVE-2026-80920Sep 9, 2026 · io_uring: defer eventfd signaling when queued from a wakeup handler0Monitor
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 | 1fa1591efd417e39e5e164bebea8ca7a3837c469 | Vendor (CNA) |
| Linux Linux | 28abce951343fcec26e397610868efa4e1395c3f | Vendor (CNA) |
| Linux Linux | 634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996 | Vendor (CNA) |
| Linux Linux | abec577de5fc16cd5caae42f97cdcd0983c06d66 | Vendor (CNA) |
| Linux Linux | aec2c2ec87d4ec1f098979f68cd81b29f031c8cb | Vendor (CNA) |
| Linux Linux | bed7fe3a936b6bdd84671385951397ca673cf6e7 | Vendor (CNA) |
| Linux Linux | dd8035dec26e98204d6e4a6e0cee5c4d329b3d7e | Vendor (CNA) |
| Linux Linux | e542edada3f79387c0ac2a528cebf01f4ef47df8 | Vendor (CNA) |
| Linux Linux | e60159f5ea60254a5c3de4ea4f2f939f0171031b | 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.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-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).
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 (8 more)Show less
- git.kernel.org/stable/c/28abce951343fcec26e397610868efa4e1395c3f
- git.kernel.org/stable/c/634f498ea5d5e8e01f8d9414d4f45eeaf9ee1996
- git.kernel.org/stable/c/abec577de5fc16cd5caae42f97cdcd0983c06d66
- git.kernel.org/stable/c/aec2c2ec87d4ec1f098979f68cd81b29f031c8cb
- git.kernel.org/stable/c/bed7fe3a936b6bdd84671385951397ca673cf6e7
- git.kernel.org/stable/c/dd8035dec26e98204d6e4a6e0cee5c4d329b3d7e
- git.kernel.org/stable/c/e542edada3f79387c0ac2a528cebf01f4ef47df8
- git.kernel.org/stable/c/e60159f5ea60254a5c3de4ea4f2f939f0171031b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.