CVE-2026-98860: HID: bpf: cast size to ssize_t when checking hid_bpf_hw_request
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.15% (FIRST EPSS).
- Fixed version: Linux Linux 3afefbfe55c2a8a0c4bdf6f4cc1f773da120027c, 6.12.113, 6.18.56.
Low priority for now. Upgrade to Linux Linux 3afefbfe55c2a8a0c4bdf6f4cc1f773da120027c, 6.12.113, 6.18.56 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: bpf: cast size to ssize_t when checking hid_bpf_hw_request As reported by Sashiko: If a transport driver encounters a hardware error and returns a negative error code such as -EPIPE, ret is implicitly promoted to size_t when compared against size. This causes the negative error code to evaluate as a large positive number, making the (ret > size) condition true. This silently converts the hardware error into a success return value and copies the unmodified buffer back, which could leave BPF programs operating on uninitialized or stale data. Fix this by casting size into ssize_t to return the actual negative error code.
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 4th 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
- eb57dae20fdf6f3069cdc07821fa3bb46de381d7, 7.0affected
- d6efaa50af62fb0790dd1fd4e7e5506b46312510 and later · before 8b85ef0f561039e249c3f883c5280a1449c6dbeeaffected · git
- 73c5b5aea1c443239c8cb4191b4af7a4bd6fd7b1 and later · before 97be6396817bd3b11d06239010d27902940bfaa9affected · git
- 2b658c1c442ec1cd9eec5ead98d68662c40fe645 and later · before f9f808227554b2c116fd07dd2328ecd74ea3f411affected · git
- 2b658c1c442ec1cd9eec5ead98d68662c40fe645 and later · before 3afefbfe55c2a8a0c4bdf6f4cc1f773da120027caffected · git
- 6.12.78 and later · before 6.12.113affected · semver
- 6.18.20 and later · before 6.18.56affected · semver
- 6.19.10 and later · before 6.20affected · semver
- before 7.0not affected · semver
- 6.12.113 and later · up to and including 6.12.*not 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-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-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-98858Oct 18, 2026 · io_uring: fix task_work add use-after-free with SQPOLL0Monitor
- ← EarlierCVE-2026-98859Oct 18, 2026 · HID: multitouch: stop the release timer from being rearmed on remove0Monitor
- Later →CVE-2026-98861Oct 18, 2026 · fprobe: Use guard(rcu_sched_notrace) and check rcu_is_watching()0Monitor
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 | 3afefbfe55c2a8a0c4bdf6f4cc1f773da120027c | Vendor (CNA) |
| Linux Linux | 6.12.113 | Vendor (CNA) |
| Linux Linux | 6.18.56 | Vendor (CNA) |
| Linux Linux | 6.20 | Vendor (CNA) |
| Linux Linux | 8b85ef0f561039e249c3f883c5280a1449c6dbee | Vendor (CNA) |
| Linux Linux | 97be6396817bd3b11d06239010d27902940bfaa9 | Vendor (CNA) |
| Linux Linux | f9f808227554b2c116fd07dd2328ecd74ea3f411 | Vendor (CNA) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-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.
- Published
- Fix recordedsame day
- TodayNov 10, 2026+22 d
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
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.