Breaking: Ruby2Shell - Ruby Memory Corruption Flaws Expose Applications to Remote Code Execution
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2026-80739

kernel: net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock

Overview

Published
3 Sep 2026
Modified
30 Oct 2026
Low CVE
0 Registry packages
347 OS packages
11 Linux distributions
Yes Fix available

Description

In the Linux kernel, the following vulnerability has been resolved:

net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock

In case __mlx5e_add_fdb_flow() fails in lower levels, the flow is deleted via mlx5e_tc_del_flow(), and mlx5e_tc_del_flow() is acquiring ESW devcom lock without condition. In addition, in case of peer_flow, __mlx5e_add_fdb_flow() is called while holding ESW devcom comp lock. This results in an AA deadlock.

To fix this, introduce a new PEER flag that is set on flows created as peer flows (the duplicate flows on peer devices), and check it in mlx5e_tc_del_flow() before acquiring ESW devcom lock.

Lockdep splat:

WARNING: possible recursive locking detected

Possible unsafe locking scenario: CPU0 ---- lock(&comp->lock_key#2); lock(&comp->lock_key#2); *** DEADLOCK *** Call Trace: <TASK> dump_stack_lvl+0x69/0xa0 print_deadlock_bug.cold+0xbd/0xca __lock_acquire+0x1671/0x2ec0 lock_acquire+0x10e/0x2e0 down_read+0x95/0x430 mlx5_devcom_for_each_peer_begin+0x4e/0xe0 [mlx5_core] mlx5e_tc_del_flow+0x11d/0xa70 [mlx5_core] mlx5e_flow_put+0x99/0x100 [mlx5_core] __mlx5e_add_fdb_flow+0x409/0xf00 [mlx5_core] mlx5e_configure_flower+0x2a86/0x4100 [mlx5_core] mlx5e_rep_setup_tc_cls_flower+0x12f/0x1b0 [mlx5_core] mlx5e_rep_setup_tc_cb+0x153/0x750 [mlx5_core] tc_setup_cb_add+0x1dc/0x470 fl_change+0x2f4d/0x626d [cls_flower] tc_new_tfilter+0x79b/0x2310 rtnetlink_rcv_msg+0x778/0xad0 do_syscall_64+0x70/0x960 entry_SYSCALL_64_after_hwframe+0x4b/0x53 </TASK>

Source: OX vulnerability database

Severity

5.5 · LOW

CVSS 3.1 base score, scored by redhat.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 82 fixes

Azure Linux 1 release · 1 package

fixed 1
kernel
Azure Linux fixes for CVE-2026-80739
ReleasePackageFixed in
3.0 kernel 0:6.6.152.1-1.azl3

Oracle Linux 1 release · 1 package

fixed 1
kernel-uek
Oracle Linux fixes for CVE-2026-80739
ReleasePackageFixed in
9 kernel-uek +34 6.12.0-207.111.5.1.el9uek

Photon OS 1 release · 1 package

fixed 1
bpftool
Photon OS fixes for CVE-2026-80739
ReleasePackageFixed in
5.0 bpftool +10 6.12.107-1.ph5

Red Hat 3 releases · 1 package

affected 3
bpftool
Red Hat fixes for CVE-2026-80739
ReleasePackageFixed in
7 bpftool +27 affected
8 bpftool +47 affected
9 bpftool +108 affected

SUSE Linux Enterprise 2 releases · 5 packages

fixed 7
kernel-livepatch-6-4-0-150700-7-78-rt kernel-livepatch-6-4-0-150700-53-84-default cluster-md-kmp-default kernel-default-base kernel-64kb
SUSE Linux Enterprise fixes for CVE-2026-80739
ReleasePackageFixed inAdvisory
15.7 kernel-livepatch-6-4-0-150700-7-78-rt 1-150700.1.3.1 SUSE-SU-2026:4640-1
15.7 kernel-livepatch-6-4-0-150700-53-84-default 1-150700.15.3.1 SUSE-SU-2026:4706-1
15.7 cluster-md-kmp-default +20 6.4.0-150700.53.84.1 SUSE-SU-2026:4706-1
15.7 kernel-default-base 6.4.0-150700.53.84.1.150700.17.47.1 SUSE-SU-2026:4706-1
16.0 cluster-md-kmp-default +2 6.12.0-160000.38.1 SUSE-SU-2026:23897-1
16.0 kernel-64kb +23 6.12.0-160000.38.1 SUSE-SU-2026:23902-1

1 more row

SUSE Linux Enterprise Micro 3 releases · 5 packages

fixed 9
kernel-default kernel-devel-rt kernel-default-base podman kernel-64kb
SUSE Linux Enterprise Micro fixes for CVE-2026-80739
ReleasePackageFixed inAdvisory
6.0 kernel-default +5 6.4.0-159998.53.1 SUSE-SU-2026:24315-1
6.0 kernel-devel-rt +3 6.4.0-159998.53.1 SUSE-SU-2026:24316-1
6.0 kernel-default-base 6.4.0-159998.53.1.159998.21.38 SUSE-SU-2026:24315-1
6.1 kernel-default +6 6.4.0-159998.53.1 SUSE-SU-2026:24181-1
6.1 kernel-devel-rt +4 6.4.0-159998.53.1 SUSE-SU-2026:24182-1
6.1 kernel-default-base 6.4.0-159998.53.1.159998.21.38 SUSE-SU-2026:24181-1

3 more rows

amazon linux 1 release · 3 packages

fixed 3
kernel-livepatch-6-12-110-135-201 bpftool6-12 bpftool6-18
amazon linux fixes for CVE-2026-80739
ReleasePackageFixed in
2023 kernel-livepatch-6-12-110-135-201 +1 1:1.0-0.amzn2023
2023 bpftool6-12 +16 1:6.12.110-135.201.amzn2023
2023 bpftool6-18 +17 1:6.18.48-107.148.amzn2023

debian 4 releases · 2 packages

affected 1 fixed 4
linux linux-6-12
debian fixes for CVE-2026-80739
ReleasePackageFixed in
11 linux affected
12 linux 6.1.192-1
12 linux-6-12 6.12.107-1~deb12u1
13 linux 6.12.105-1
14 linux 7.1.9-1

echo 1 release · 1 package

fixed 1
linux
echo fixes for CVE-2026-80739
ReleasePackageFixed in
linux 1

openSUSE Leap 2 releases · 2 packages

fixed 4
cluster-md-kmp-64kb kernel-default-base
openSUSE Leap fixes for CVE-2026-80739
ReleasePackageFixed inAdvisory
16.0 cluster-md-kmp-64kb +74 6.12.0-160000.38.1 openSUSE-SU-2026:21910-1
16.0 kernel-default-base 6.12.0-160000.38.1.160000.2.22 openSUSE-SU-2026:21910-1
16.1 cluster-md-kmp-64kb +74 6.12.0-160100.9.1 openSUSE-SU-2026:22309-1
16.1 kernel-default-base 6.12.0-160100.9.1.160100.3.14 openSUSE-SU-2026:22309-1

ubuntu 5 releases · 35 packages

affected 5 fixed 42
linux-aws-5-4 linux linux-oracle-6-8 linux-ibm-6-8 linux-aws-6-8 linux-azure-fde-6-8 +29
ubuntu fixes for CVE-2026-80739
ReleasePackageFixed in
18.04-ESM linux-aws-5-4 +6 affected
20.04-ESM linux +21 affected
22.04 linux +17 affected
22.04 linux-oracle-6-8 6.8.0-1067.71~22.04.1
22.04 linux-ibm-6-8 6.8.0-1069.70~22.04.1
22.04 linux-aws-6-8 6.8.0-1069.74~22.04.1

41 more rows

References

Show all 28 references

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.