CVE-2025-38335 Details
Description
In the Linux kernel, the following vulnerability has been resolved: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT When enabling PREEMPT_RT, the gpio_keys_irq_timer() callback runs in hard irq context, but the input_event() takes a spin_lock, which isn't allowed there as it is converted to a rt_spin_lock(). [ 4054.289999] BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 [ 4054.290028] in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 0, name: swapper/0 ... [ 4054.290195] __might_resched+0x13c/0x1f4 [ 4054.290209] rt_spin_lock+0x54/0x11c [ 4054.290219] input_event+0x48/0x80 [ 4054.290230] gpio_keys_irq_timer+0x4c/0x78 [ 4054.290243] __hrtimer_run_queues+0x1a4/0x438 [ 4054.290257] hrtimer_interrupt+0xe4/0x240 [ 4054.290269] arch_timer_handler_phys+0x2c/0x44 [ 4054.290283] handle_percpu_devid_irq+0x8c/0x14c [ 4054.290297] handle_irq_desc+0x40/0x58 [ 4054.290307] generic_handle_domain_irq+0x1c/0x28 [ 4054.290316] gic_handle_irq+0x44/0xcc Considering the gpio_keys_irq_isr() can run in any context, e.g. it can be threaded, it seems there's no point in requesting the timer isr to run in hard irq context. Relax the hrtimer not to use the hard context.
A vulnerability has been identified in the Linux kernel's GPIO keys input handling when PREEMPT RT is enabled. The issue arises because the 'gpio_keys_irq_timer()' callback operates in a hard interrupt context, while the 'input_event()' function requires a spin lock that is not compatible with this context, leading to a potential deadlock. This vulnerability can cause the system to hang, as indicated by a kernel warning about sleeping functions being called from an invalid context.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/664e5a6f541ff226621487d1280d2ec28e86be28 | kernel.org | Patch |
| https://git.kernel.org/stable/c/a7b79db25846459de63ca8974268f0c41c734c4b | kernel.org | Patch |
| https://git.kernel.org/stable/c/a8f01e51109f77229e426b57c5d19251b462c6aa | kernel.org | Patch |
| https://git.kernel.org/stable/c/ec8f5da79b425deef5aebacdd4fe645620cd4f0b | kernel.org | Patch |
| https://git.kernel.org/stable/c/f4a8f561d08e39f7833d4a278ebfb12a41eef15f | kernel.org | Patch |
| https://git.kernel.org/stable/c/fa53beab4740c4e5fe969f218a379f9558be33dc | kernel.org | Patch |
| https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html | CVE | Third Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 5.13, < 5.15.190 >= 5.16, < 6.1.148 >= 6.2, < 6.6.101 >= 6.7, < 6.12.41 >= 6.13, < 6.15.4 |
CPE
Remediation
| |
| debian debian linux | 11.0 |
CPE
Remediation
| |
Change History
10 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | CVE |
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Nov 5, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 16, 2025 | Initial Analysis | [email protected] |
| Nov 3, 2025 | CVE Modified | CVE |
| Aug 28, 2025 | CVE Modified | kernel.org |
| Aug 15, 2025 | CVE Modified | kernel.org |
| Aug 1, 2025 | CVE Modified | kernel.org |
| Jul 10, 2025 | New CVE Received | kernel.org |