CVE-2025-38335: Input: gpio-keys - fix a sleep while atomic with PREEMPT_RT
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.13% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 664e5a6f541ff226621487d1280d2ec28e86be28, a7b79db25846459de63ca8974268f0c41c734c4b, a8f01e51109f77229e426b57c5d19251b462c6aa; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1.
Low priority for now. Upgrade to Linux Linux 664e5a6f541ff226621487d1280d2ec28e86be28, a7b79db25846459de63ca8974268f0c41c734c4b, a8f01e51109f77229e426b57c5d19251b462c6aa; azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 6.6.104.2-1; cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 5.15.200.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 10, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-667
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux11.0
- linux linux kernel5.13 and later · before 5.15.190
- linux linux kernel5.16 and later · before 6.1.148
- linux linux kernel6.2 and later · before 6.6.101
- linux linux kernel6.7 and later · before 6.12.41
- linux linux kernel6.13 and later · before 6.15.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.13affected
- 019002f20cb5b9f78d39360aff244265d035e08a and later · before 664e5a6f541ff226621487d1280d2ec28e86be28affected · git
- 019002f20cb5b9f78d39360aff244265d035e08a and later · before a8f01e51109f77229e426b57c5d19251b462c6aaaffected · git
- 019002f20cb5b9f78d39360aff244265d035e08a and later · before fa53beab4740c4e5fe969f218a379f9558be33dcaffected · git
- 019002f20cb5b9f78d39360aff244265d035e08a and later · before a7b79db25846459de63ca8974268f0c41c734c4baffected · git
- 019002f20cb5b9f78d39360aff244265d035e08a and later · before ec8f5da79b425deef5aebacdd4fe645620cd4f0baffected · git
- 019002f20cb5b9f78d39360aff244265d035e08a and later · before f4a8f561d08e39f7833d4a278ebfb12a41eef15faffected · git
- before 5.13not affected · semver
- 5.15.190 and later · up to and including 5.15.*not affected · semver
- 6.1.148 and later · up to and including 6.1.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.148-1 | 6.1.148-1 |
| Debian:13 | linux | before 6.12.41-1 | 6.12.41-1 |
| Debian:14 | linux | before 6.16.3-1 | 6.16.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-38333Jul 10, 2025 · f2fs: fix to bail out in get_new_segment()22Monitor
- ← EarlierCVE-2025-38334Jul 10, 2025 · x86/sgx: Prevent attempts to reclaim poisoned pages22Monitor
- Later →CVE-2025-38336Jul 10, 2025 · ata: pata_via: Force PIO for ATAPI devices on VT6415/VT633022Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 664e5a6f541ff226621487d1280d2ec28e86be28 | Vendor (CNA) |
| Linux Linux | a7b79db25846459de63ca8974268f0c41c734c4b | Vendor (CNA) |
| Linux Linux | a8f01e51109f77229e426b57c5d19251b462c6aa | Vendor (CNA) |
| Linux Linux | ec8f5da79b425deef5aebacdd4fe645620cd4f0b | Vendor (CNA) |
| Linux Linux | f4a8f561d08e39f7833d4a278ebfb12a41eef15f | Vendor (CNA) |
| Linux Linux | fa53beab4740c4e5fe969f218a379f9558be33dc | Vendor (CNA) |
| azl3 kernel 6.6.96.2-2 on Azure Linux 3.0 | 6.6.104.2-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0 | 5.15.200.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.148-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-667 · Improper LockingCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/a7b79db25846459de63ca8974268f0c41c734c4b
- git.kernel.org/stable/c/a8f01e51109f77229e426b57c5d19251b462c6aa
- git.kernel.org/stable/c/ec8f5da79b425deef5aebacdd4fe645620cd4f0b
- git.kernel.org/stable/c/f4a8f561d08e39f7833d4a278ebfb12a41eef15f
- git.kernel.org/stable/c/fa53beab4740c4e5fe969f218a379f9558be33dc
- lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.