Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-40263Input: cros_ec_keyb - fix an invalid memory access

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.

Timeline

  1. ID reserved

    By Linux

  2. · 8 months later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (12 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 – < d74864291cb8bd784d44d1d02e87109cf88666bb
    • affected ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 – < 9cf59f4724a9ee06ebb06c76b8678ac322e850b7
    • affected ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 – < 6d81068685154535af06163eb585d6d9663ec7ec
    • affected ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 – < 2d251c15c27e2dd16d6318425d2f7260cbd47d39
    • affected ca1eadbfcd36bec73f2a2111c28e8c7e9e8ae6c0 – < e08969c4d65ac31297fcb4d31d4808c789152f68
  • Linux · Linux

    • affected 5.19
    • unaffected < 5.19
    • unaffected 6.1.159 – ≤ 6.1.*
    • unaffected 6.6.118 – ≤ 6.6.*
    • unaffected 6.12.60 – ≤ 6.12.*
    • unaffected 6.17.10 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-40263 badge
[![CVE-2025-40263](https://cveledger.app/badge/CVE-2025-40263.svg)](https://cveledger.app/cve/CVE-2025-40263)

Record last updated .