Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: fix BQL reset on SQ re-activation mlx5e_queue_start() deactivates and… (CVE-2026-74698)

0
Medium
Published: 08/22/2026 (08/22/2026, 18:30:29 UTC)
Source: GCVE Database

Description

A vulnerability in the Linux kernel's mlx5e network driver related to the handling of Byte Queue Limits (BQL) during Send Queue (SQ) re-activation has been resolved. The issue involved improper resetting of BQL counters when restarting transmission queues, which could lead to a kernel BUG triggered by an overcharge in the dynamic queue limits. The fix ensures BQL counters are reset only when no bytes are in flight on the SQ, preventing the kernel crash.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/23/2026, 00:38:14 UTC

Technical Analysis

The vulnerability in the Linux kernel's mlx5e network driver occurs because mlx5e_queue_start() deactivates and reactivates all channels but closes only the queue being restarted. Subsequently, mlx5e_activate_txqsq() unconditionally calls netdev_tx_reset_queue(), zeroing BQL counters for channels that still have in-flight TX Work Queue Elements (WQEs). This causes the next completion to overcharge and trigger a kernel BUG at lib/dynamic_queue_limits.c in dql_completed(). The patch fixes this by resetting BQL only when the SQ has no bytes in flight (sq->cc == sq->pc), allowing outstanding WQEs to complete and rebalance the dynamic queue limits without causing a crash.

Potential Impact

This vulnerability can cause a kernel crash (BUG_ON) in the mlx5e network driver due to improper handling of BQL counters during SQ re-activation. While no direct exploitation or remote code execution is indicated, the kernel crash can lead to denial of service on affected systems running the vulnerable driver.

Mitigation Recommendations

A fix has been implemented in the Linux kernel to address this issue by modifying the BQL reset logic during SQ re-activation. Users should apply the official kernel updates that include this patch. Since this is a kernel-level fix, upgrading to a patched kernel version is the recommended remediation. Patch status is not explicitly stated in the provided data; therefore, check the vendor or kernel mailing list advisories for the exact fixed versions and apply updates accordingly.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-qrj3-pxvx-pgch
Osv Schema Version
1.4.0
Aliases
["CVE-2026-74698"]
Ecosystems
[]
Database Specific Severity
null
Cvss Version
null

Threat ID: 6a8a27f0acd9273b499bc744

Added to database: 08/22/2026, 22:51:28 UTC

Last enriched: 08/23/2026, 00:38:14 UTC

Last updated: 08/23/2026, 02:11:58 UTC

Views: 2

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses