Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 664e5a6f541ff226621487d1280d2ec28e86be28, Kernel 5.15.190, Kernel 6.1.148 and 8 more.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=019002f20cb5b9f78d39360aff244265d035e08a <664e5a6f541ff226621487d1280d2ec28e86be28, >=5.13 <5.15.190, >=5.16 <6.1.148, >=6.13 <6.15.4, >=6.2 <6.6.101, >=6.7 <6.12.41, >=019002f20cb5b9f78d39360aff244265d035e08a <fa53beab4740c4e5fe969f218a379f9558be33dc, >=019002f20cb5b9f78d39360aff244265d035e08a <f4a8f561d08e39f7833d4a278ebfb12a41eef15f, >=019002f20cb5b9f78d39360aff244265d035e08a <ec8f5da79b425deef5aebacdd4fe645620cd4f0b, >=019002f20cb5b9f78d39360aff244265d035e08a <a8f01e51109f77229e426b57c5d19251b462c6aa, >=019002f20cb5b9f78d39360aff244265d035e08a <a7b79db25846459de63ca8974268f0c41c734c4b, =5.13 | 664e5a6f541ff226621487d1280d2ec28e86be28, 5.15.190, 6.1.148, 6.15.4, 6.6.101, 6.12.41, fa53beab4740c4e5fe969f218a379f9558be33dc, f4a8f561d08e39f7833d4a278ebfb12a41eef15f, ec8f5da79b425deef5aebacdd4fe645620cd4f0b, a8f01e51109f77229e426b57c5d19251b462c6aa, a7b79db25846459de63ca8974268f0c41c734c4b |
| debian | debian_linux | =11.0 | |
| linux-kernel: Kernel | >=6.7.0 <6.12.41, >=6.2.0 <6.6.101, >=6.13.0 <6.15.4, >=5.16.0 <6.1.148, >=5.13.0 <5.15.190 | 6.12.41, 6.6.101, 6.15.4, 6.1.148, 5.15.190 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket