CVE-2026-98205
Input: evdev - zero absinfo before partial copy in EVIOCSABS
No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 448cd1664a573e69f54bfd32f3bb7220212b6cf5, < c0aebb57b73c7d06ad21731099afe119b113c403Upgrade to: c0aebb57b73c7d06ad21731099afe119b113c403Affected: ≥ 448cd1664a573e69f54bfd32f3bb7220212b6cf5, < 89b6ffa4bc10c436fa9aecc73be105124cd58a35Upgrade to: 89b6ffa4bc10c436fa9aecc73be105124cd58a35Affected: ≥ 448cd1664a573e69f54bfd32f3bb7220212b6cf5, < e834e134a32b6a5c600fa539bb49146f617743abUpgrade to: e834e134a32b6a5c600fa539bb49146f617743abAffected: ≥ 448cd1664a573e69f54bfd32f3bb7220212b6cf5, < af5f7130cbf39e6e12336d0b7a5f6e76e4e1526bUpgrade to: af5f7130cbf39e6e12336d0b7a5f6e76e4e1526b + 4 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: Input: evdev - zero absinfo before partial copy in EVIOCSABS The EVIOCSABS handler copies at most the user supplied ioctl size into an uninitialized on-stack struct input_absinfo: if (copy_from_user(&abs, p, min_t(size_t, size, sizeof(struct input_absinfo)))) The size comes from _IOC_SIZE() of the ioctl command and is therefore fully controlled by userspace. A short size leaves the trailing part of the structure holding whatever was on the kernel stack, and the whole structure is then stored into the device: dev->absinfo[t] = abs; EVIOCGABS hands that back to userspace, disclosing the stale stack bytes. Only the resolution field is currently cleared, which covers the legacy struct layout but not an arbitrarily short size. Zero the structure before the copy so any part not supplied by the caller reads back as zero. The existing resolution fixup is kept, since it also handles a size that partially overlaps that field.
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/30b853a3d71f16bd0aa66b604bc37dd1254a19b3
- git.kernel.org/stable/c/3dfe48d5307a1ba22c58231d04257737015569ca
- git.kernel.org/stable/c/71e5619db11dd6429101bd967230d0321ec5ea26
And 5 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI