CVE-2025-21928
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
Mitigation details
CVE-2025-21928 NameCVE-2025-21928 DescriptionIn 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β¦
CVE-2025-21928
| Name | CVE-2025-21928 |
| Description | 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. |
| Source | CVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
| References | DLA-4178-1, DLA-4193-1, DSA-5900-1 |
Vulnerable and fixed packages
The table below lists information on source packages.
| Source Package | Release | Version | Status |
|---|---|---|---|
| linux (PTS) | bullseye | 5.10.223-1 | vulnerable |
| bullseye (security) | 5.10.257-1 | fixed | |
| bookworm | 6.1.170-3 | fixed | |
| bookworm (security) | 6.1.174-1 | fixed | |
| trixie | 6.12.86-1 | fixed | |
| trixie (security) | 6.12.90-2 | fixed | |
| forky | 7.0.9-1 | fixed | |
| sid | 7.0.10-1 | fixed | |
| linux-6.1 (PTS) | bullseye (security) | 6.1.174-1~deb11u1 | fixed |
The information below is based on the following data on fixed versions.
| Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
|---|---|---|---|---|---|---|
| linux | source | bullseye | 5.10.237-1 | DLA-4178-1 | ||
| linux | source | bookworm | 6.1.133-1 | DSA-5900-1 | ||
| linux | source | (unstable) | 6.12.19-1 | |||
| linux-6.1 | source | bullseye | 6.1.137-1~deb11u1 | DLA-4193-1 |
Notes
https://git.kernel.org/linus/07583a0010696a17fb0942e0b499a62785c5fc9f (6.14-rc6)
Apply commands
https://git.kernel.org/linus/07583a0010696a17fb0942e0b499a62785c5fc9f (6.14-rc6)
OS impact
| OS | Version | Status | Fixed in |
|---|---|---|---|
| rhel | 9 | fixed | |
| rocky | 8 | fixed | |
| sles | affected | | |
| rocky | 9 | fixed | |
| debian | bookworm | fixed | 6.1.133-1 |
| debian | bullseye | fixed | 5.10.237-1 |
| debian | forky | fixed | 6.12.19-1 |
| debian | sid | fixed | 6.12.19-1 |
| debian | trixie | fixed | 6.12.19-1 |
| almalinux | 8 | fixed | kernel-rt-4.18.0-553.66.1.rt7.407.el8_10.x86_64.rpm |
| almalinux | 9 | fixed | kernel-64k-debug-devel-matched-5.14.0-570.32.1.el9_6.aarch64.rpm |
References
- https://access.redhat.com/errata/RHSA-2025:12746
- https://errata.rockylinux.org/RLSA-2025:12753
- https://errata.rockylinux.org/RLSA-2025:12752
- https://www.suse.com/security/cve/CVE-2025-21928.html
- https://errata.rockylinux.org/RLSA-2025:12746
- https://security-tracker.debian.org/tracker/CVE-2025-21928
- https://access.redhat.com/errata/RHSA-2025:12752
- https://bugzilla.redhat.com/2356592
- https://bugzilla.redhat.com/2360099
- https://bugzilla.redhat.com/2366848
- https://bugzilla.redhat.com/2373380
- https://bugzilla.redhat.com/2373383
- https://bugzilla.redhat.com/2373630
- https://errata.almalinux.org/8/ALSA-2025-12752.html
- https://access.redhat.com/errata/RHSA-2025:12753
- https://errata.almalinux.org/8/ALSA-2025-12753.html
- https://bugzilla.redhat.com/2348516
- https://bugzilla.redhat.com/2356594
- https://bugzilla.redhat.com/2356624
- https://bugzilla.redhat.com/2363378
- https://bugzilla.redhat.com/2375531
- https://errata.almalinux.org/9/ALSA-2025-12746.html
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.