CVE-2026-74673

Input: evdev - fix information leak in evdev_pass_values()

N/A
Published: August 22, 2026 at 03:32 PM UTC
Updated: October 14, 2026 at 01:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.246addb1d6de1968b84852f54561cc9a999909b5a9
Vendor states this is fixed in 06a286b320236508d02ab2ccc9496352748652a8 (fixed)
Vendor states this is fixed in 7d17e9454a9af3ec7aebb88b41a9deedd5b19a6b (fixed)
Vendor states this is fixed in 7e55ca1080f09d9f7112c7f20ac31f682c1f2374 (fixed)
Vendor states this is fixed in 90f305f2c7a30257c683e13f4bf7c798eea992a0 (fixed)
Vendor states this is fixed in bd3c4108a56de34380edab670065e86283cb3029 (fixed)
Vendor states this is fixed in c6d5fa46c1ee25d068fc730fd377f0f54188d290 (fixed)
Vendor states this is fixed in d2e3839419ac4047835762c4d7712bda1101b57e (fixed)
Vendor states this is fixed in e748811d9b80a3e101110ff4b3c612e5fca54d98 (fixed)
Vendor states this is fixed in 2.6.24 (unaffected)
Vendor states this is fixed in 5.10.265 (unaffected)
Vendor states this is fixed in 5.15.216 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.104 (unaffected)
Vendor states this is fixed in 6.18.45 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.9 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card