LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21928: HID: intel-ish-hid: Fix use-after-free issue in ishtp_hid_remove()

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.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-21928 is a Linux kernel memory-safety flaw in the Intel ISH HID driver. A vulnerable system can crash after the driver is removed because the kernel may reuse data after it has been freed. The issue is high severity, but the supplied sources do not show active exploitation.

Executive priority

Treat as a high-priority kernel maintenance item, especially for managed Linux endpoint fleets. It is not currently supported as an emergency exploitation event by the supplied evidence, but kernel memory corruption with high CVSS impact warrants timely patching.

Technical view

The flaw is a CWE-416 use-after-free in ishtp_hid_remove(). driver_data was freed while HID devices were being destroyed, but hid_destroy_device() can still use it through hid_ishtp_set_feature() while powering off a sensor. Stable kernel patches defer freeing driver_data until after device destruction.

Likely exposure

Exposure is most likely on Linux systems using the intel-ish-hid Intel Sensor Hub HID driver with affected kernel builds. Debian LTS advisories and multiple Linux stable commits indicate distro and stable-kernel remediation is relevant. The bundle does not prove every Linux deployment is exposed.

Exploitation context

CVSS marks this local, low-complexity, low-privilege, no-user-interaction, high-impact. The public description emphasizes random crashes after driver removal. KEV is false, and the supplied sources do not cite in-the-wild exploitation or public exploit availability.

Researcher notes

The source evidence supports a narrow driver lifecycle bug, not a general remote Linux compromise. Focus validation on affected kernel lineage, presence of intel-ish-hid, and whether downstream distro packages include one of the stable fixes. Evidence on practical exploitability beyond crash potential is incomplete.

Mitigation direction

  • Update to a vendor or stable Linux kernel containing the referenced fixes.
  • Apply relevant Debian LTS kernel updates where Debian systems are in scope.
  • Prioritize systems with Intel ISH HID hardware or loaded intel-ish-hid components.
  • If patching is delayed, check distro guidance for temporary driver handling.
  • Avoid ad hoc kernel workarounds without vendor validation.

Validation and detection

  • Inventory Linux kernel versions and packages across affected fleets.
  • Check whether intel-ish-hid or related Intel ISH HID support is present.
  • Map running kernels to vendor advisories or the referenced stable commits.
  • Review kernel logs for crashes after driver removal events.
  • Confirm patched kernels are booted, not merely installed.
Prepared
Confidence
high
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-416: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-21928 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2025-21928Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6, 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6, 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6, 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6, 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6, 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6, 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6, 0b28cb4bcb17dcb5fe0763fc3e1a94398b8f6cf6unaffected
LinuxLinux4.9, 0, 5.4.291, 5.10.235, 5.15.179, 6.1.131, 6.6.83, 6.12.19, 6.13.7, 6.14affected
Weakness

CWE details

CWE-416

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-416 · source CWE mapping

Use After Free

Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs