Input: evdev - fix information leak in evdev_pass_values()
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 06a286b320236508d02ab2ccc9496352748652a8, 7d17e9454a9af3ec7aebb88b41a9deedd5b19a6b, 7e55ca1080f09d9f7112c7f20ac31f682c1f2374; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 06a286b320236508d02ab2ccc9496352748652a8, 7d17e9454a9af3ec7aebb88b41a9deedd5b19a6b, 7e55ca1080f09d9f7112c7f20ac31f682c1f2374; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.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: Input: evdev - fix information leak in evdev_pass_values() In evdev_pass_values(), the input_event structure is allocated on the kernel stack and populated field-by-field. However, it is never fully initialized. On architectures where struct input_event contains explicit or implicit padding (such as the 32-bit __pad field on SPARC64), these padding bytes are left uninitialized. When this event structure is subsequently passed to the client buffer and later copied to userspace, the uninitialized padding bytes leak kernel stack memory, potentially exposing sensitive information. Similar issues exist in __evdev_queue_syn_dropped and __pass_event. Fix this by explicitly zeroing the entire event structure with memset() before populating its fields. This ensures all padding bytes are cleared before the data crosses the security boundary.
- Published
- Aug 22, 2026
- Updated
- Oct 14, 2026
- EPSS
- 0.1% · 6th 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
- 2.6.24affected
- 6addb1d6de1968b84852f54561cc9a999909b5a9 and later · before d2e3839419ac4047835762c4d7712bda1101b57eaffected · git
- 6addb1d6de1968b84852f54561cc9a999909b5a9 and later · before c6d5fa46c1ee25d068fc730fd377f0f54188d290affected · git
- 6addb1d6de1968b84852f54561cc9a999909b5a9 and later · before e748811d9b80a3e101110ff4b3c612e5fca54d98affected · git
- 6addb1d6de1968b84852f54561cc9a999909b5a9 and later · before 06a286b320236508d02ab2ccc9496352748652a8affected · git
- 6addb1d6de1968b84852f54561cc9a999909b5a9 and later · before 7d17e9454a9af3ec7aebb88b41a9deedd5b19a6baffected · git
- 6addb1d6de1968b84852f54561cc9a999909b5a9 and later · before bd3c4108a56de34380edab670065e86283cb3029affected · git
- 6addb1d6de1968b84852f54561cc9a999909b5a9 and later · before 7e55ca1080f09d9f7112c7f20ac31f682c1f2374affected · git
- 6addb1d6de1968b84852f54561cc9a999909b5a9 and later · before 90f305f2c7a30257c683e13f4bf7c798eea992a0affected · git
- before 2.6.24not 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 | 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.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.9-1 | 7.1.9-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-74671Aug 22, 2026 · ima: fix out-of-bounds read in xattr_verify()0Monitor
- ← EarlierCVE-2026-74672Aug 22, 2026 · mm/vmalloc: acquire init_mm lock on huge vmap to avoid ptdump UAF0Monitor
- Later →CVE-2026-74674Aug 22, 2026 · mm: fix incorrect flush address in direct page table reclaim31Monitor
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 | 06a286b320236508d02ab2ccc9496352748652a8 | Vendor (CNA) |
| Linux Linux | 7d17e9454a9af3ec7aebb88b41a9deedd5b19a6b | Vendor (CNA) |
| Linux Linux | 7e55ca1080f09d9f7112c7f20ac31f682c1f2374 | Vendor (CNA) |
| Linux Linux | 90f305f2c7a30257c683e13f4bf7c798eea992a0 | Vendor (CNA) |
| Linux Linux | bd3c4108a56de34380edab670065e86283cb3029 | Vendor (CNA) |
| Linux Linux | c6d5fa46c1ee25d068fc730fd377f0f54188d290 | Vendor (CNA) |
| Linux Linux | d2e3839419ac4047835762c4d7712bda1101b57e | Vendor (CNA) |
| Linux Linux | e748811d9b80a3e101110ff4b3c612e5fca54d98 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | 6.6.152.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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0893 · Aug 24, 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/7d17e9454a9af3ec7aebb88b41a9deedd5b19a6b
- git.kernel.org/stable/c/7e55ca1080f09d9f7112c7f20ac31f682c1f2374
- git.kernel.org/stable/c/90f305f2c7a30257c683e13f4bf7c798eea992a0
- git.kernel.org/stable/c/bd3c4108a56de34380edab670065e86283cb3029
- git.kernel.org/stable/c/c6d5fa46c1ee25d068fc730fd377f0f54188d290
- git.kernel.org/stable/c/d2e3839419ac4047835762c4d7712bda1101b57e
- git.kernel.org/stable/c/e748811d9b80a3e101110ff4b3c612e5fca54d98
Vendor advisories and official records. Exploit/PoC links are deliberately left out.