CVE-2025-40263

Input: cros_ec_keyb - fix an invalid memory access

N/A
Published: December 4, 2025 at 04:08 PM UTC
Updated: October 18, 2026 at 06:10 PM UTC
2 products affected across 2 vendorsLinux KernelRUGGEDCOM RST2428P Firmware

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: cros_ec_keyb - fix an invalid memory access If cros_ec_keyb_register_matrix() isn't called (due to `buttons_switches_only`) in cros_ec_keyb_probe(), `ckdev->idev` remains NULL. An invalid memory access is observed in cros_ec_keyb_process() when receiving an EC_MKBP_EVENT_KEY_MATRIX event in cros_ec_keyb_work() in such case. Unable to handle kernel read from unreadable memory at virtual address 0000000000000028 ... x3 : 0000000000000000 x2 : 0000000000000000 x1 : 0000000000000000 x0 : 0000000000000000 Call trace: input_event cros_ec_keyb_work blocking_notifier_call_chain ec_irq_thread It's still unknown about why the kernel receives such malformed event, in any cases, the kernel shouldn't access `ckdev->idev` and friends if the driver doesn't intend to initialize them.

Affected

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

5.19ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0
Vendor states this is fixed in 2d251c15c27e2dd16d6318425d2f7260cbd47d39 (fixed)
Vendor states this is fixed in 6d81068685154535af06163eb585d6d9663ec7ec (fixed)
Vendor states this is fixed in 9cf59f4724a9ee06ebb06c76b8678ac322e850b7 (fixed)
Vendor states this is fixed in d74864291cb8bd784d44d1d02e87109cf88666bb (fixed)
Vendor states this is fixed in e08969c4d65ac31297fcb4d31d4808c789152f68 (fixed)
Vendor states this is fixed in 5.19 (unaffected)
Vendor states this is fixed in 6.1.159 (unaffected)
Vendor states this is fixed in 6.12.60 (unaffected)
Vendor states this is fixed in 6.17.10 (unaffected)
Vendor states this is fixed in 6.18 (unaffected)
Vendor states this is fixed in 6.6.118 (unaffected)
v < V4.0
Affected range stops below V4.0, so it looks safe — our inference, not a vendor statement

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

StatusDEFERRED

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