# CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT

Status: published. Published: 2025-07-10. Updated: 2026-11-05.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ 019002f20cb5b9f78d39360aff244265d035e08a; < 664e5a6f541ff226621487d1280d2ec28e86be28 (affected, git); ≥ 019002f20cb5b9f78d39360aff244265d035e08a; < a8f01e51109f77229e426b57c5d19251b462c6aa (affected, git); ≥ 019002f20cb5b9f78d39360aff244265d035e08a; < fa53beab4740c4e5fe969f218a379f9558be33dc (affected, git); ≥ 019002f20cb5b9f78d39360aff244265d035e08a; < a7b79db25846459de63ca8974268f0c41c734c4b (affected, git); ≥ 019002f20cb5b9f78d39360aff244265d035e08a; < ec8f5da79b425deef5aebacdd4fe645620cd4f0b (affected, git); ≥ 019002f20cb5b9f78d39360aff244265d035e08a; < f4a8f561d08e39f7833d4a278ebfb12a41eef15f (affected, git). Source: CNA: Linux
- Linux / Linux: 5.13 (affected); ≥ 0; < 5.13 (unaffected, semver); ≥ 5.15.190; ≤ 5.15.* (unaffected, semver); ≥ 6.1.148; ≤ 6.1.* (unaffected, semver); ≥ 6.6.101; ≤ 6.6.* (unaffected, semver); ≥ 6.12.41; ≤ 6.12.* (unaffected, semver); ≥ 6.15.4; ≤ 6.15.* (unaffected, semver); ≥ 6.16; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.14% as of 2026-11-05; percentile 3.31%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/664e5a6f541ff226621487d1280d2ec28e86be28 (CNA: Linux)

- https://git.kernel.org/stable/c/a8f01e51109f77229e426b57c5d19251b462c6aa (CNA: Linux)

- https://git.kernel.org/stable/c/fa53beab4740c4e5fe969f218a379f9558be33dc (CNA: Linux)

- https://git.kernel.org/stable/c/a7b79db25846459de63ca8974268f0c41c734c4b (CNA: Linux)

- https://git.kernel.org/stable/c/ec8f5da79b425deef5aebacdd4fe645620cd4f0b (CNA: Linux)

- https://git.kernel.org/stable/c/f4a8f561d08e39f7833d4a278ebfb12a41eef15f (CNA: Linux)

- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html (ADP: CVE)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2025-38335; retrieved 2026-11-05; source updated 2026-11-05

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2025-38335; retrieved 2026-11-05; source updated Not reported

Revision: 71af1acdf1bb8145439f72ae0f6693140220fb6ec1064bad39248056786a75da

Canonical: https://y2.dev/cve/CVE-2025-38335

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.