{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40263 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40263 is a vulnerability in Linux, published on 4 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-40263 and fix it if it is affected.\n\nWhat it is: CVE-2025-40263 is a vulnerability in Linux, published on 4 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-40263 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-40263/ (Markdown: https://insights.sbomify.com/CVE-2025-40263/index.md)","id":"CVE-2025-40263","markdown":"https://insights.sbomify.com/CVE-2025-40263/index.md","name":"CVE-2025-40263","record":{"aliases":["BELL-CVE-2025-40263","DEBIAN-CVE-2025-40263","GHSA-r3v3-c3jq-3938","ROOT-OS-DEBIAN-12-CVE-2025-40263","ROOT-OS-DEBIAN-13-CVE-2025-40263","ROOT-OS-UBUNTU-2204-CVE-2025-40263","ROOT-OS-UBUNTU-2404-CVE-2025-40263","UBUNTU-CVE-2025-40263"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A null pointer dereference in the Chrome OS EC keyboard driver causes a kernel crash when processing specific events without proper initialization.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nInput: cros_ec_keyb - fix an invalid memory access\n\nIf cros_ec_keyb_register_matrix() isn't called (due to\n`buttons_switches_only`) in cros_ec_keyb_probe(), `ckdev-\u003eidev` remains\nNULL.  An invalid memory access is observed in cros_ec_keyb_process()\nwhen receiving an EC_MKBP_EVENT_KEY_MATRIX event in cros_ec_keyb_work()\nin such case.\n\n  Unable to handle kernel read from unreadable memory at virtual address 0000000000000028\n  ...\n  x3 : 0000000000000000 x2 : 0000000000000000\n  x1 : 0000000000000000 x0 : 0000000000000000\n  Call trace:\n  input_event\n  cros_ec_keyb_work\n  blocking_notifier_call_chain\n  ec_irq_thread\n\nIt's still unknown about why the kernel receives such malformed event,\nin any cases, the kernel shouldn't access `ckdev-\u003eidev` and friends if\nthe driver doesn't intend to initialize them.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Input: cros_ec_keyb - fix an invalid memory access","id":"CVE-2025-40263","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"be2net: pass wrb_params in case of OS2BMC","id":"CVE-2025-40264"},"packages":[],"prev":{"headline":"Input: imx_sc_key - fix memory corruption on unload","id":"CVE-2025-40262"},"products":["Linux"],"published":"2025-12-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-06-02","vendors":["Linux"]},"summary":"A null pointer dereference in the Chrome OS EC keyboard driver causes a kernel crash when processing specific events without proper initialization.","url":"https://insights.sbomify.com/CVE-2025-40263/"}