Skip to main content
VulnerabilityPublished Updated

CVE-2026-80739: Linux kernel · net/mlx5e: TC, Check if flow is PEER before acquiring devcom lock

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-80739· Medium

Not known to be exploited · fixed in ff9e7d5e3500be389ce7a0e46db3a77149830bc9 : update Linux kernel when convenient.

Data as of 30 Oct 2026, 19:33 UTC

Severity
Medium

Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in ff9e7d5e3500be389ce7a0e46db3a77149830bc9, ead5145d290a918b7c3c3141a64b3f827a9e1b6b, 7165fe321c61ec138850c02f030f274797761f5f +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 04de7dda7394fa9c2b0fc9cec65661d9b4f0d04d, < ff9e7d5e3500be389ce7a0e46db3a77149830bc9
Fixed in
  • ff9e7d5e3500be389ce7a0e46db3a77149830bc9
LinuxLinuxAffected
  • ≥ 04de7dda7394fa9c2b0fc9cec65661d9b4f0d04d, < ead5145d290a918b7c3c3141a64b3f827a9e1b6b
Fixed in
  • ead5145d290a918b7c3c3141a64b3f827a9e1b6b
LinuxLinuxAffected
  • ≥ 04de7dda7394fa9c2b0fc9cec65661d9b4f0d04d, < 7165fe321c61ec138850c02f030f274797761f5f
Fixed in
  • 7165fe321c61ec138850c02f030f274797761f5f
LinuxLinuxAffected
  • ≥ 04de7dda7394fa9c2b0fc9cec65661d9b4f0d04d, < 607adbda01053abf5f93e322fe39325da8828cb8
Fixed in
  • 607adbda01053abf5f93e322fe39325da8828cb8
LinuxLinuxAffected
  • ≥ 04de7dda7394fa9c2b0fc9cec65661d9b4f0d04d, < 585df8643081e6f616579bc52cd49ac823a57c82
Fixed in
  • 585df8643081e6f616579bc52cd49ac823a57c82
LinuxLinuxAffected
  • ≥ 04de7dda7394fa9c2b0fc9cec65661d9b4f0d04d, < 6ddfba2ea98db21b001e0e5c472499156224650c
Fixed in
  • 6ddfba2ea98db21b001e0e5c472499156224650c

AI-suggested

A fix has been implemented that introduces a PEER flag to prevent acquiring the ESW devcom lock when deleting peer flows, thereby avoiding the deadlock. Users should apply the updated Linux kernel version containing this fix once available. No alternative mitigations are described.

Description

A deadlock vulnerability exists in the Linux kernel's mlx5e network driver related to flow deletion and locking. When __mlx5e_add_fdb_flow() fails, mlx5e_tc_del_flow() unconditionally acquires the ESW devcom lock, which can cause an AA deadlock if the flow is a peer flow. The issue is fixed by introducing a PEER flag to avoid acquiring the lock in such cases.

References

Community reviews

Loading reviews…