Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Apr 1, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 14th percentile

Report tools

JSON

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.

Follow CVE-2025-21928

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux 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.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-55.25.1.el10_06.12.0-55.25.1.el10_0
AlmaLinux:10kernel-docbefore 6.12.0-55.25.1.el10_06.12.0-55.25.1.el10_0
AlmaLinux:8bpftoolbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.66.1.el8_104.18.0-553.66.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.66.1.rt7.407.el8_104.18.0-553.66.1.rt7.407.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-21922Apr 1, 2025 · ppp: Fix KMSAN uninit-value warning with bpf
    22Monitor
  • ← EarlierCVE-2025-21923Apr 1, 2025 · HID: hid-steam: Fix use-after-free when detaching device
    31Monitor
  • 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 / packageFixed versionSource
Linux Linux01b18a330cda61cc21423a7d1af92cf31ded8f60Vendor (CNA)
Linux Linux07583a0010696a17fb0942e0b499a62785c5fc9fVendor (CNA)
Linux Linux0c1fb475ef999d6c22fc3f963fdf20cb3ed1b03dVendor (CNA)
Linux Linux560f4d1299342504a6ab8a47f575b5e6b8345adaVendor (CNA)
Linux Linuxcf1a6015d2f6b1f0afaa0fd6a0124ff2c7943394Vendor (CNA)
Linux Linuxd3faae7f42181865c799d88c5054176f38ae4625Vendor (CNA)
Linux Linuxdea6a349bcaf243fff95dfd0428a26be6a0fb44eVendor (CNA)
Linux Linuxeb0695d87a81e7c1f0509b7d8ee7c65fbc26aec9Vendor (CNA)
azl3 kernel 6.6.82.1-1 on Azure Linux 3.06.6.85.1-2 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.176.3-3 on CBL Mariner 2.05.15.180.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-570.32.1.el9_6 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-abi-stablelists6.12.0-55.25.1.el10_0 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-doc6.12.0-55.25.1.el10_0 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.133-1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-55.25.1.el10_0 · Red Hat:enterprise_linux:10.0Package 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.

Finders, 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 Free

CVSS 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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records