Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-74523: qede: sync udp_tunnel ports outside qede_lock in the recovery path

HighCVSS 7.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.50% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 19e505ee8bb9e0f0355eda9e9f614fb25fed0070, 451c9075d6c53f2438d110addbeeeea6fac18567, 4626df3f63c9185efba5750fe76ac01ab3351bae; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 19e505ee8bb9e0f0355eda9e9f614fb25fed0070, 451c9075d6c53f2438d110addbeeeea6fac18567, 4626df3f63c9185efba5750fe76ac01ab3351bae; azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 6.6.152.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: qede: sync udp_tunnel ports outside qede_lock in the recovery path A TX timeout on a qede NIC that has VXLAN/GENEVE tunnel ports configured wedges the rtnetlink control plane of the whole machine: NETDEV WATCHDOG: ens6f1 (qede): transmit queue 2 timed out 10226 ms [qede_tx_timeout:586(ens6f1)]TX timeout on queue 2! [qede_recovery_handler:2665(ens6f0)]Starting a recovery process The recovery path deadlocks on the driver's own mutex: qede_sp_task rtnl_lock() mutex_lock(&edev->qede_lock) <- taken qede_recovery_handler qede_load udp_tunnel_nic_reset_ntf __udp_tunnel_nic_device_sync info->sync_table == qede_udp_tunnel_sync mutex_lock(&edev->qede_lock) <- same task: deadlock The mutex is not recursive, so the kworker blocks on itself with rtnl_lock held, and neither lock is ever released. Every task that calls rtnl_lock() afterwards (ip, ovs-vswitchd, lldpad, IPv6 addrconf, sshd) blocks forever while the node still answers ping. In a vmcore from an affected production node rtnl_mutex.owner decodes to the very kworker blocked at the innermost mutex_lock() above. Re-sync the tunnel ports from qede_sp_task() after the internal lock is dropped, still under rtnl_lock as the udp_tunnel API requires. This mirrors qede_open(), which calls udp_tunnel_nic_reset_ntf() under rtnl without the internal lock. qede_recovery_handler() now returns whether it has successfully reloaded an open device, and the caller re-syncs the ports only in that case. This keeps the old gating exactly: a device that was down or a failed recovery returns false, as those paths never reached the udp_tunnel_nic_reset_ntf() call before either. This was the only user of the qede_lock()/qede_unlock() helpers, so remove them.

Published
Aug 15, 2026
Updated
Oct 16, 2026
EPSS
0.5% · 43th percentile
CWE
—

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-74523

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.9affected
    • 8cd160a29415f1789d473b1dc07fcc9d02a02b87 and later · before 19e505ee8bb9e0f0355eda9e9f614fb25fed0070affected · git
    • 8cd160a29415f1789d473b1dc07fcc9d02a02b87 and later · before c4c1e5d6bc2b900b2328d6fff93dc8146b858d69affected · git
    • 8cd160a29415f1789d473b1dc07fcc9d02a02b87 and later · before 8e1bdf57de91247e57816482966265ada573cc74affected · git
    • 8cd160a29415f1789d473b1dc07fcc9d02a02b87 and later · before e382a4efeeae6555b95d9ff336cf3094ee7d336baffected · git
    • 8cd160a29415f1789d473b1dc07fcc9d02a02b87 and later · before 4626df3f63c9185efba5750fe76ac01ab3351baeaffected · git
    • 8cd160a29415f1789d473b1dc07fcc9d02a02b87 and later · before e51becb8f3377a377171ed5bf0082b96e22e6292affected · git
    • 8cd160a29415f1789d473b1dc07fcc9d02a02b87 and later · before 6f1ef8170d3d8ad9319aa01347945dcdf5cc4f27affected · git
    • 8cd160a29415f1789d473b1dc07fcc9d02a02b87 and later · before 451c9075d6c53f2438d110addbeeeea6fac18567affected · git
    • before 5.9not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.187-16.1.187-1
Debian:12linux-6.12before 6.12.107-1~deb12u16.12.107-1~deb12u1
Debian:13linuxbefore 6.12.105-16.12.105-1
Debian:14linuxbefore 7.1.8-17.1.8-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-74520Aug 15, 2026 · iommu/iommufd: Fix IOPF group ownership UAF
    35Monitor
  • ← EarlierCVE-2026-74521Aug 15, 2026 · ksmbd: use memcmp() to compare ClientGUIDs
    36Monitor
  • Later →CVE-2026-74527Aug 15, 2026 · octeontx2-af: Block VFs from clobbering special CGX PKIND state
    35Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux19e505ee8bb9e0f0355eda9e9f614fb25fed0070Vendor (CNA)
Linux Linux451c9075d6c53f2438d110addbeeeea6fac18567Vendor (CNA)
Linux Linux4626df3f63c9185efba5750fe76ac01ab3351baeVendor (CNA)
Linux Linux6f1ef8170d3d8ad9319aa01347945dcdf5cc4f27Vendor (CNA)
Linux Linux8e1bdf57de91247e57816482966265ada573cc74Vendor (CNA)
Linux Linuxc4c1e5d6bc2b900b2328d6fff93dc8146b858d69Vendor (CNA)
Linux Linuxe382a4efeeae6555b95d9ff336cf3094ee7d336bVendor (CNA)
Linux Linuxe51becb8f3377a377171ed5bf0082b96e22e6292Vendor (CNA)
azl3 kernel 6.6.150.1-1 on Azure Linux 3.06.6.152.1-1 · Release NotesMicrosoft (MSRC)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.107-1~deb12u1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records