CVE-2025-38335

  1. OpenCVE
  2. Vulnerabilities (CVE)
  3. CVE-2025-38335
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.
CVSS

No CVSS.

References
Link Resource
https://git.kernel.org/stable/c/a7b79db25846459de63ca8974268f0c41c734c4b
https://git.kernel.org/stable/c/ec8f5da79b425deef5aebacdd4fe645620cd4f0b
https://git.kernel.org/stable/c/f4a8f561d08e39f7833d4a278ebfb12a41eef15f
https://git.kernel.org/stable/c/fa53beab4740c4e5fe969f218a379f9558be33dc
Configurations

No configuration.

History

01 Aug 2025, 09:15

Type Values Removed Values Added
References
  • () https://git.kernel.org/stable/c/a7b79db25846459de63ca8974268f0c41c734c4b -
  • () https://git.kernel.org/stable/c/fa53beab4740c4e5fe969f218a379f9558be33dc -
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: Entrada: gpio-keys - corrige un fallo de suspensión mientras es atómico con PREEMPT_RT Al habilitar PREEMPT_RT, la devolución de llamada gpio_keys_irq_timer() se ejecuta en un contexto de irq duro, pero input_event() toma un spin_lock, que no está permitido allí ya que se convierte en un rt_spin_lock(). [ 4054.289999] ERROR: función de suspensión llamada desde un contexto no válido en 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 Teniendo en cuenta que gpio_keys_irq_isr() puede ejecutarse en cualquier contexto, por ejemplo, puede ser Enhebrado, parece que no tiene sentido solicitar que el temporizador ISR se ejecute en un contexto de IRQ estricto. Reduzca la velocidad del temporizador hr para que no use dicho contexto.

10 Jul 2025, 09:15

Type Values Removed Values Added
New CVE
Information

Published : 2025-07-10 09:15

Updated : 2025-08-01 09:15

NVD link : CVE-2025-38335

Mitre link : CVE-2025-38335

CVE.ORG link : CVE-2025-38335

JSON object : View

Products Affected

No product.

CWE

No CWE.