CVE-2026-99440 in Linux
Summary
by MITRE • 11/19/2026
In the Linux kernel, the following vulnerability has been resolved:
media: rc: Ensure that rc_unregister_device() does not free input device
During or after rc_unregister_device(), IR may still be reported which results in a input event being reported. This could result in a null pointer deref in rc_keydown() or a use-after-free of the input device if the pointer was read before it is set to NULL.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 11/20/2026
The Linux kernel's remote control subsystem contains a race condition vulnerability within the rc_unregister_device function that can lead to critical memory safety issues during device teardown operations. This flaw arises from an improper synchronization between the unregistration process and ongoing input event reporting mechanisms. Specifically, when the rc_unregister_device routine is invoked to dismantle a remote controller interface, it initiates the release of associated resources including the underlying input device structure. However, there exists a window where infrared signal processing may still be active or pending completion after this function has begun execution but before all references are safely nullified and cleaned up.
The technical core of this vulnerability lies in the timing sequence between resource deallocation and event propagation. During normal operation, when an IR receiver detects a signal it translates that into input events via rc_keydown which accesses pointers to various structures including the input device pointer. If rc_unregister_device proceeds with freeing or nullifying these resources while concurrent threads are still attempting to report key presses through this same pathway, two distinct failure modes emerge depending on execution order. In one scenario if a thread reads the input device pointer after it has been set to NULL but before proper synchronization completes, dereferencing that pointer results in a null pointer exception causing kernel panic or system instability.
In another more dangerous scenario involving use-after-free conditions, code may access memory regions associated with the input device structure after they have already been freed and potentially reallocated for other purposes by the kernel allocator. This allows an attacker who can trigger remote control events during unregistration to read arbitrary kernel memory contents or write data to unintended locations effectively bypassing standard isolation boundaries within the operating system. Such exploitation could lead to privilege escalation, information disclosure of sensitive kernel structures, or complete denial of service through system crashes requiring manual intervention to restore functionality.
This vulnerability maps directly to CWE-416 which describes use-after-free errors where software continues to use memory after it has been freed leading to undefined behavior and potential security breaches. Additionally the scenario involving access to null pointers aligns with CWE-476 concerning NULL pointer dereferences that cause crashes or unexpected termination of processes. From an adversarial perspective this flaw relates to ATT&CK technique T1059 which covers command and script interpretation as attackers might leverage such kernel-level instabilities to execute arbitrary code within the privileged context of the operating system core components.
The operational impact extends beyond immediate stability concerns affecting systems that utilize infrared remote control interfaces particularly in embedded devices set-top boxes media centers and automotive infotainment systems where hardware removal or software updates frequently trigger device unregistration sequences. Users experiencing this vulnerability may observe sudden system freezes blue screens kernel oops messages or unpredictable behavior when interacting with physical controls during configuration changes driver reloads or hot-plug events involving IR receivers.
Mitigation strategies primarily involve applying vendor-provided patches that address the synchronization logic within rc_unregister_device to ensure all pending input events are fully processed and discarded before any memory structures are released. System administrators should prioritize updating kernel packages containing fixes for this specific media remote control subsystem issue especially in environments where hardware configuration changes occur regularly or remotely managed devices undergo routine maintenance cycles implementing strict access controls limiting who can trigger device unregistration procedures also reduces exposure surface by preventing unauthorized actors from initiating the vulnerable sequence under controlled conditions monitoring system logs for signs of input event anomalies during teardown operations provides early detection capabilities while comprehensive testing using fuzzing tools targeting IR subsystem interfaces helps identify similar race conditions across related components ensuring robust defense-in-depth posture against memory corruption vulnerabilities.