cve.bz

CVE-2026-97962 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Move representor vnic reporter to eswitch devlink port The representor vnic devlink health reporter is created and destroyed along the representor netdev (un)load path, which is not serialized by the devlink instance lock. Destroying the reporter from there triggers a devl_assert_locked() splat on driver unbind: WARNING: net/devlink/core.c:259 at devl_assert_locked+0x54/0x70, CPU#2: bash/3758 Modules linked in: mlx5_vdpa vringh vdpa mlx5_ib mlx5_fwctl mlx5_core ... CPU: 2 UID: 0 PID: 3758 Comm: bash Tainted: G W 6.19.0+ #1 PREEMPT Tainted: [W]=WARN Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), ... RIP: 0010:devl_assert_locked+0x54/0x70 Call Trace: <TASK> devl_health_reporter_destroy+0x3a/0x1b0 mlx5e_vport_rep_unload+0x12d/0x2b0 [mlx5_core] mlx5_eswitch_unregister_vport_reps+0x1b8/0x220 [mlx5_core] ? __esw_offloads_unload_rep+0x190/0x190 [mlx5_core] ? kernfs_remove_by_name_ns+0xc3/0xf0 device_release_driver_internal+0x3b2/0x560 unbind_store+0xce/0xf0 Move the reporter's lifecycle to the eswitch devlink port (un)register paths, which are already serialized by the devlink instance lock, and store the handle on mlx5_devlink_port. Use the port's mlx5_vport as the reporter priv since the diagnose callback only needs a device handle and a vport number, and mlx5_vport carries both and is initialized before any representor driver probes.
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 6th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Linux Linux: fixed in 6.6.160
  • Linux Linux: fixed in 6.12.114
  • Linux Linux: fixed in 6.18.53
  • Linux Linux: fixed in 7.2.7
  • Linux Linux: fixed in 7.3
  • Debian, Ubuntu, openSUSE, Azure Linux, Alpaquita: fixed package versions per release

Ask an AI about this CVE

Show the promptExplain CVE-2026-97962 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-97962?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-97962?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-97962 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux6.4 and later

Fixed in

ProductRelease lineFixed in
Linux6.66.6.160
Linux6.126.12.114
Linux6.186.18.53
Linux7.27.2.7
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12linux-6.126.12.115-2~deb12u1DEBIAN-CVE-2026-97962
Debian13linux6.12.115-2DEBIAN-CVE-2026-97962
Debian14linux7.2.7-1DEBIAN-CVE-2026-97962
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-97962
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-97962
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-97962
Ubuntu22.04:LTSlinux-riscv, linux-aws-6.2, linux-aws-6.5 and 40 moreno fix listedUBUNTU-CVE-2026-97962
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 44 moreno fix listedUBUNTU-CVE-2026-97962
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-97962 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-97962 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-97962 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-97962 USN-8959-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-97962 USN-9020-1
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-97962
Ubuntu26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-97962 USN-8959-1
15 more for Ubuntu in the JSON and on Ubuntu's page.
openSUSETumbleweedkernel-source7.2.9-1.1openSUSE-SU-2026:12074-1
Azure Linux3kernel6.6.161.1-1AZL-104487
Alpaquita25linux-lts6.12.115-r0BELL-CVE-2026-97962
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-97962

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A moderate-impact flaw exists in the Linux kernel mlx5 network driver as shipped in Red Hat Enterprise Linux 8, 9, and 10, Red Hat In-Vehicle OS 2, and the RHEL CoreOS 9 kernel used by OpenShift Container Platform 4. The mlx5e representor vnic devlink health reporter is created and destroyed along the representor netdev (un)load path, which is not serialized by the devlink instance lock. Consequently, when a local user with administrative privileges unbinds the mlx5 driver, destruction of the health reporter triggers a kernel assertion failure (a devl_assert_locked() WARNING). This kernel warning may cause system instability or a denial of service, particularly on systems where panic_on_warn is enabled. Confidentiality and integrity are not impacted; Red Hat rates this flaw Moderate severity (CVSS 3.1 score 5.5, AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). Fixes for the affected streams are currently deferred to a future routine update because the issue manifests as a kernel warning that requires privileged local access to trigger and affects only availability, so it does not warrant an immediate out-of-band kernel update; the residual risk is limited to local denial of service on hosts where an administrative user unbinds the mlx5 driver. Red Hat Enterprise Linux 7, the RHEL 8.4, 8.6, and 8.8 update streams, the RHEL 9.2 update stream, and OpenShift Container Platform versions built on RHEL CoreOS 8 are not affected because the vulnerable code, the mlx5e representor vnic devlink health reporter, is not present in those versions.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtNot affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Not affected
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-97962.

References

Check your stackJSON