Skip to content
Noroxi
CVE-2025-40263· NVD / CVE Program· CNA Linux

Input: cros_ec_keyb - fix an invalid memory access

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.19% (FIRST EPSS).
  • Fixed version: Linux Linux 2d251c15c27e2dd16d6318425d2f7260cbd47d39, 6d81068685154535af06163eb585d6d9663ec7ec, 9cf59f4724a9ee06ebb06c76b8678ac322e850b7.

Low priority for now. Upgrade to Linux Linux 2d251c15c27e2dd16d6318425d2f7260cbd47d39, 6d81068685154535af06163eb585d6d9663ec7ec, 9cf59f4724a9ee06ebb06c76b8678ac322e850b7 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: 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.

—No exploit Fix available
Published
Dec 4, 2025
Updated
Oct 18, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

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.

Follow CVE-2025-40263

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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

    • 5.19affected
    • ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 and later · before d74864291cb8bd784d44d1d02e87109cf88666bbaffected · git
    • ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 and later · before 9cf59f4724a9ee06ebb06c76b8678ac322e850b7affected · git
    • ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 and later · before 6d81068685154535af06163eb585d6d9663ec7ecaffected · git
    • ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 and later · before 2d251c15c27e2dd16d6318425d2f7260cbd47d39affected · git
    • ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 and later · before e08969c4d65ac31297fcb4d31d4808c789152f68affected · git
    • before 5.19not affected · semver
    • 6.1.159 and later · up to and including 6.1.*not affected · semver
    • 6.6.118 and later · up to and including 6.6.*not affected · semver
    • 6.12.60 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.

EcosystemPackageAffected rangeFix
Debian:11linux-6.1before 6.1.159-1~deb11u16.1.159-1~deb11u1
Debian:12linuxbefore 6.1.159-16.1.159-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.10-16.17.10-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40261Dec 4, 2025 · nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl()
    39Monitor
  • ← EarlierCVE-2025-40262Dec 4, 2025 · Input: imx_sc_key - fix memory corruption on unload
    31Monitor
  • Later →CVE-2025-40264Dec 4, 2025 · be2net: pass wrb_params in case of OS2BMC
    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 / packageFixed versionSource
Linux Linux2d251c15c27e2dd16d6318425d2f7260cbd47d39Vendor (CNA)
Linux Linux6d81068685154535af06163eb585d6d9663ec7ecVendor (CNA)
Linux Linux9cf59f4724a9ee06ebb06c76b8678ac322e850b7Vendor (CNA)
Linux Linuxd74864291cb8bd784d44d1d02e87109cf88666bbVendor (CNA)
Linux Linuxe08969c4d65ac31297fcb4d31d4808c789152f68Vendor (CNA)
debian:linux6.1.159-1 · Debian:12Package registry (OSV)
debian:linux-6.16.1.159-1~deb11u1 · Debian:11Package 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.

EPSS, last 120 days

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 researchers

Finders, 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records