CVE-2026-98945 json
HID: steam: Rearrange teardown sequence
published 19d ago modified 17d ago also EUVD-2026-108919
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
HID: steam: Rearrange teardown sequence
This fixes a narrow window during the teardown sequence where callbacks could still be scheduled during cleanup that would then have a dangling pointer to the now-freed steam struct.
This also puts work canceling for rumble and mode switch in steam_unregister, as that shouldn't persist while the client hdev is open.
Patch / fix
- Linux Linux 7.3
- linux Debian 13 6.12.113-1
- linux Debian 14 7.2.11-1
debian advisories DEBIAN-CVE-2026-98945
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-43.43
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1017.18
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1017.19
- linux-gke Ubuntu 24.04 LTS 6.8.0-1068.77
- linux-gke Ubuntu 26.04 LTS 7.0.0-1010.11
ubuntu advisories UBUNTU-CVE-2026-98945
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel Azure Linux 3.0 6.6.161.1-1
azure linux advisories AZL-110744
Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT
- git.kernel.org/stable/c/d2587923d50c8b141ce0ccb284c714cf6054d6a7 commit
- git.kernel.org/stable/c/81a8209c09f9be7eef860ca6cc154749a6b4d243 commit
- git.kernel.org/stable/c/86724f4bcf6049c3a322f7a7b1f968210059c46a commit
- git.kernel.org/stable/c/b5ea938ff776306798d3a11485c2475034f92131 commit
- git.kernel.org/stable/c/ddce9641ce924ed91ec8304577e463823a29ffaf commit
Is CVE-2026-98945 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98945 updated cvss 5.3
kernel: kernel: Denial of service via use-after-free in Steam HID driver teardown
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/d2587923d50c8b141ce0ccb284c714cf6054d6a7
- git.kernel.org /stable/c/81a8209c09f9be7eef860ca6cc154749a6b4d243
- git.kernel.org /stable/c/86724f4bcf6049c3a322f7a7b1f968210059c46a
- git.kernel.org /stable/c/b5ea938ff776306798d3a11485c2475034f92131
- git.kernel.org /stable/c/ddce9641ce924ed91ec8304577e463823a29ffaf
Sources
- CVE List CVE-2026-98945
- NVD CVE-2026-98945
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.