Answer in brief
CVE-2025-38335 records a Medium severity (CVSS 5.5) vulnerability in Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:* | Not reported | Not reported |
| cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=019002f20cb5b9f78d39360aff244265d035e08a <664e5a6f541ff226621487d1280d2ec28e86be28 || >=019002f20cb5b9f78d39360aff244265d035e08a <a8f01e51109f77229e426b57c5d19251b462c6aa || >=019002f20cb5b9f78d39360aff244265d035e08a <fa53beab4740c4e5fe969f218a379f9558be33dc || >=019002f20cb5b9f78d39360aff244265d035e08a <a7b79db25846459de63ca8974268f0c41c734c4b || >=019002f20cb5b9f78d39360aff244265d035e08a <ec8f5da79b425deef5aebacdd4fe645620cd4f0b || >=019002f20cb5b9f78d39360aff244265d035e08a <f4a8f561d08e39f7833d4a278ebfb12a41eef15f | 664e5a6f541ff226621487d1280d2ec28e86be28, a8f01e51109f77229e426b57c5d19251b462c6aa, fa53beab4740c4e5fe969f218a379f9558be33dc, a7b79db25846459de63ca8974268f0c41c734c4b, ec8f5da79b425deef5aebacdd4fe645620cd4f0b, f4a8f561d08e39f7833d4a278ebfb12a41eef15f |
| Linux/Linuxgeneric | 5.13 | Not reported |
Published upstream
Jul 10, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.