CVE-2026-99438: Linux kernel · media: rc: mce_kbd: Fix inconsistent locking of keylock
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in 29ee25fa9beb3232808e6d0b3e8ebfb0427cb820 : update Linux kernel when convenient.
Data as of 19 Nov 2026, 14:49 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in 29ee25fa9beb3232808e6d0b3e8ebfb0427cb820, 15c53a8b50a9595fbd14befe8eb0455616e648a5, 7df669eab2abcb141f43cab1e558c401a1093b37 +1
Exploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade Linux kernel to 29ee25fa9beb3232808e6d0b3e8ebfb0427cb820, 15c53a8b50a9595fbd14befe8eb0455616e648a5, 7df669eab2abcb141f43cab1e558c401a1093b37 or 0e18282783cc426207127c1214b40967a18ef939.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- git.kernel.org/stable/c/15c53a8b50a9595fbd14befe8eb0455616e648a5 (opens in a new tab)
- git.kernel.org/stable/c/0e18282783cc426207127c1214b40967a18ef939 (opens in a new tab)
- git.kernel.org/stable/c/7df669eab2abcb141f43cab1e558c401a1093b37 (opens in a new tab)
- git.kernel.org/stable/c/29ee25fa9beb3232808e6d0b3e8ebfb0427cb820 (opens in a new tab)