CVE-2025-21928: HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove()
Noroxi assessment
Priority: Monitor (action score 31/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.23% (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 01b18a330cda61cc21423a7d1af92cf31ded8f60, 07583a0010696a17fb0942e0b499a62785c5fc9f, 0c1fb475ef999d6c22fc3f963fdf20cb3ed1b03d; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.85.1-2; cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 5.15.180.1-1.
Low priority for now. Upgrade to Linux Linux 01b18a330cda61cc21423a7d1af92cf31ded8f60, 07583a0010696a17fb0942e0b499a62785c5fc9f, 0c1fb475ef999d6c22fc3f963fdf20cb3ed1b03d; azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 6.6.85.1-2; cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 5.15.180.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: HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove() The system can experience a random crash a few minutes after the driver is removed. This issue occurs due to improper handling of memory freeing in the ishtp_hid_remove() function. The function currently frees the `driver_data` directly within the loop that destroys the HID devices, which can lead to accessing freed memory. Specifically, `hid_destroy_device()` uses `driver_data` when it calls `hid_ishtp_set_feature()` to power off the sensor, so freeing `driver_data` beforehand can result in accessing invalid memory. This patch resolves the issue by storing the `driver_data` in a temporary variable before calling `hid_destroy_device()`, and then freeing the `driver_data` after the device is destroyed.
- BDU:2025-11776
- ALSA-2025:12662
- ALSA-2025:12746
- ALSA-2025:12752
- ALSA-2025:12753
- RHSA-2025:12662
- RHSA-2025:12746
- RHSA-2025:12752
- RHSA-2025:12753
- RHSA-2025:13029
- RHSA-2025:13030
- RHSA-2025:13061
- RHSA-2025:13120
- RHSA-2025:13135
- RHSA-2025:13633
- RHSA-2025:13776
- RHSA-2025:13781
- RHSA-2025:14136
- RHSA-2025:14746
- RHSA-2025:14748
- Published
- Apr 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- CWE-416
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.9 and later · before 5.4.291
- linux linux kernel5.5 and later · before 5.10.235
- linux linux kernel5.11 and later · before 5.15.179
- linux linux kernel5.16 and later · before 6.1.131
- linux linux kernel6.2 and later · before 6.6.83
- linux linux kernel6.7 and later · before 6.12.19
- linux linux kernel6.13 and later · before 6.13.7
- linux linux kernel6.14
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
- 4.9affected
- 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6 and later · before 0c1fb475ef999d6c22fc3f963fdf20cb3ed1b03daffected · git
- 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6 and later · before d3faae7f42181865c799d88c5054176f38ae4625affected · git
- 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6 and later · before 01b18a330cda61cc21423a7d1af92cf31ded8f60affected · git
- 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6 and later · before cf1a6015d2f6b1f0afaa0fd6a0124ff2c7943394affected · git
- 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6 and later · before 560f4d1299342504a6ab8a47f575b5e6b8345adaaffected · git
- 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6 and later · before dea6a349bcaf243fff95dfd0428a26be6a0fb44eaffected · git
- 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6 and later · before eb0695d87a81e7c1f0509b7d8ee7c65fbc26aec9affected · git
- 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6 and later · before 07583a0010696a17fb0942e0b499a62785c5fc9faffected · git
- before 4.9not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | kernel-abi-stablelists | before 6.12.0-55.25.1.el10_0 | 6.12.0-55.25.1.el10_0 |
| AlmaLinux:10 | kernel-doc | before 6.12.0-55.25.1.el10_0 | 6.12.0-55.25.1.el10_0 |
| AlmaLinux:8 | bpftool | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.66.1.el8_10 | 4.18.0-553.66.1.el8_10 |
| AlmaLinux:8 | kernel-rt | before 4.18.0-553.66.1.rt7.407.el8_10 | 4.18.0-553.66.1.rt7.407.el8_10 |
| AlmaLinux:8 | kernel-rt-core | before 4.18.0-553.66.1.rt7.407.el8_10 | 4.18.0-553.66.1.rt7.407.el8_10 |
| AlmaLinux:8 | kernel-rt-debug | before 4.18.0-553.66.1.rt7.407.el8_10 | 4.18.0-553.66.1.rt7.407.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-core | before 4.18.0-553.66.1.rt7.407.el8_10 | 4.18.0-553.66.1.rt7.407.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-devel | before 4.18.0-553.66.1.rt7.407.el8_10 | 4.18.0-553.66.1.rt7.407.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules | before 4.18.0-553.66.1.rt7.407.el8_10 | 4.18.0-553.66.1.rt7.407.el8_10 |
| AlmaLinux:8 | kernel-rt-debug-modules-extra | before 4.18.0-553.66.1.rt7.407.el8_10 | 4.18.0-553.66.1.rt7.407.el8_10 |
+96
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-21922Apr 1, 2025 · ppp: Fix KMSAN uninit-value warning with bpf22Monitor
- ← EarlierCVE-2025-21923Apr 1, 2025 · HID: hid-steam: Fix use-after-free when detaching device31Monitor
- Later →CVE-2025-21929Apr 1, 2025 · HID: intel-ish-hid: Fix use-after-free issue in hid_ishtp_cl_remove()31Monitor
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 | 01b18a330cda61cc21423a7d1af92cf31ded8f60 | Vendor (CNA) |
| Linux Linux | 07583a0010696a17fb0942e0b499a62785c5fc9f | Vendor (CNA) |
| Linux Linux | 0c1fb475ef999d6c22fc3f963fdf20cb3ed1b03d | Vendor (CNA) |
| Linux Linux | 560f4d1299342504a6ab8a47f575b5e6b8345ada | Vendor (CNA) |
| Linux Linux | cf1a6015d2f6b1f0afaa0fd6a0124ff2c7943394 | Vendor (CNA) |
| Linux Linux | d3faae7f42181865c799d88c5054176f38ae4625 | Vendor (CNA) |
| Linux Linux | dea6a349bcaf243fff95dfd0428a26be6a0fb44e | Vendor (CNA) |
| Linux Linux | eb0695d87a81e7c1f0509b7d8ee7c65fbc26aec9 | Vendor (CNA) |
| azl3 kernel 6.6.82.1-1 on Azure Linux 3.0 | 6.6.85.1-2 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.0 | 5.15.180.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| almalinux:kernel | 5.14.0-570.32.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k | 5.14.0-570.32.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-core | 5.14.0-570.32.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug | 5.14.0-570.32.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-core | 5.14.0-570.32.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel | 5.14.0-570.32.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-devel-matched | 5.14.0-570.32.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules | 5.14.0-570.32.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-core | 5.14.0-570.32.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-64k-debug-modules-extra | 5.14.0-570.32.1.el9_6 · AlmaLinux:9 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 6.12.0-55.25.1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| almalinux:kernel-doc | 6.12.0-55.25.1.el10_0 · AlmaLinux:10 | Package registry (OSV) |
| debian:linux | 6.1.133-1 · Debian:12 | Package registry (OSV) |
| red hat:kernel-64k-debug-debuginfo | 0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel | 0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debug-devel-matched | 0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-debuginfo | 0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-devel | 0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-64k-devel-matched | 0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
| red hat:kernel-debug-debuginfo | 0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0 | Package registry (OSV) |
+7
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.
No history yet (it accumulates with the daily EPSS job).
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-416 · Use After FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.
The bug in code
The whole CWE-416 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
free(dev->buf);
/* ... another thread is still running ... */
process(dev->buf);Fixed
lock(&dev->lock);
free(dev->buf);
dev->buf = NULL;
unlock(&dev->lock);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (9 more)Show less
- git.kernel.org/stable/c/07583a0010696a17fb0942e0b499a62785c5fc9f
- git.kernel.org/stable/c/0c1fb475ef999d6c22fc3f963fdf20cb3ed1b03d
- git.kernel.org/stable/c/560f4d1299342504a6ab8a47f575b5e6b8345ada
- git.kernel.org/stable/c/cf1a6015d2f6b1f0afaa0fd6a0124ff2c7943394
- git.kernel.org/stable/c/d3faae7f42181865c799d88c5054176f38ae4625
- git.kernel.org/stable/c/dea6a349bcaf243fff95dfd0428a26be6a0fb44e
- git.kernel.org/stable/c/eb0695d87a81e7c1f0509b7d8ee7c65fbc26aec9
- lists.debian.org/debian-lts-announce/2025/05/msg00030.html
- lists.debian.org/debian-lts-announce/2025/05/msg00045.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.