CVE-2026-98015 json
net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put
published last mo. modified 23d ago also EUVD-2026-86668
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 7%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put
In mlx5_eswitch_termtbl_put(), the zero-ref cleanup check reads tt->ref_count after termtbl_mutex has been released. Two concurrent callers on the same mlx5_termtbl_handle race: one decrements ref_count to zero, removes the hash entry, and calls kfree(tt) while the other has already dropped the mutex and is about to evaluate if (!tt->ref_count), producing a use-after-free.
Fix this by capturing the result of the decrement into a stack-local last variable before dropping the mutex. The cleanup decision is now made entirely under termtbl_mutex, and tt is not touched after kfree.
Patch / fix
- Linux Linux 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.111, 6.18.53, 7.2.7, 7.3
- linux Debian 12 6.1.190-1
- linux Debian 13 6.12.111-1
- linux Debian 14 7.2.7-1
- linux-6.12 Debian 12 6.12.111-1~deb12u1
debian advisories DEBIAN-CVE-2026-98015
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 24.04 LTS 6.8.0-149.149
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 24.04 LTS 6.8.0-1069.74
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1073.81
ubuntu advisories UBUNTU-CVE-2026-98015
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-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
- kernel-syms-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
- kernel-source-rt Real Time Module 15 SP7 6.4.0-150700.7.81.1
- kernel-rt SLE Micro 5.4 5.14.21-150400.15.192.2
- kernel-source-rt SLE Micro 5.4 5.14.21-150400.15.192.2
- kernel-rt SLE Micro 5.5 5.14.21-150500.13.167.2
- kernel-source-rt SLE Micro 5.5 5.14.21-150500.13.167.2
- kernel-64kb SLES 15 SP4-LTSS, SLE High Performance Computing 15 SP4-LTSS, SLE High Performance Computing 15 SP4-ESPOS 5.14.21-150400.24.246.1
suse advisories SUSE-SU-2026:4940-1SUSE-SU-2026:4939-1SUSE-SU-2026:4938-1SUSE-SU-2026:4937-1SUSE-SU-2026:4936-1SUSE-SU-2026:4935-1
- kernel-rt openSUSE Leap 16.0 6.12.0-160000.40.1
- dtb-aarch64 openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-64kb openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-syms openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-azure openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-obs-qa openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-source openSUSE Leap 16.0 6.12.0-160000.40.1
- kernel-default openSUSE Leap 16.0 6.12.0-160000.40.1
opensuse advisories openSUSE-SU-2026:22167-1openSUSE-SU-2026:12074-1
- kernel Azure Linux 3.0 6.6.158.1-1
azure linux advisories AZL-104298
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/e3ee194a790896fa92fea20b5385a354be2f2c12 commit
- git.kernel.org/stable/c/b1398c9dfb5d3d4faaf6905ff7d98110a5d2c797 commit
- git.kernel.org/stable/c/92f581cac93a71723456ac79ef54d9f60a251b42 commit
- git.kernel.org/stable/c/a5833fdf53350b8b95a558fcf0056ddb1c0fe154 commit
- git.kernel.org/stable/c/304ea40ef4561671503c36e47da44a0a31b71e36 commit
- git.kernel.org/stable/c/e393789e92310d7c66f57c876101779c90816a12 commit
- git.kernel.org/stable/c/18b2969073879b9cce24e1a78b118bdad54518d1 commit
- git.kernel.org/stable/c/7ee07f601f8f507c9faf25c68a49396ab8950596 commit
Is CVE-2026-98015 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-98015 updated cvss 4.7
kernel: net/mlx5: E-Switch: fix use-after-free in mlx5_eswitch_termtbl_put
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: workaround, no fix planned “Out of support scope”
-
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-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: workaround, no fix available
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.18% chance of exploitation in the next 30 days, higher than 7% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/e3ee194a790896fa92fea20b5385a354be2f2c12
- git.kernel.org /stable/c/b1398c9dfb5d3d4faaf6905ff7d98110a5d2c797
- git.kernel.org /stable/c/92f581cac93a71723456ac79ef54d9f60a251b42
- git.kernel.org /stable/c/a5833fdf53350b8b95a558fcf0056ddb1c0fe154
- git.kernel.org /stable/c/304ea40ef4561671503c36e47da44a0a31b71e36
- git.kernel.org /stable/c/e393789e92310d7c66f57c876101779c90816a12
- git.kernel.org /stable/c/18b2969073879b9cce24e1a78b118bdad54518d1
- git.kernel.org /stable/c/7ee07f601f8f507c9faf25c68a49396ab8950596
Sources
- CVE List CVE-2026-98015
- NVD CVE-2026-98015
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.