dbcve.org
Linux KernelOperating system · Linux

CVE-2026-52983

HIGH · 7.5 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.18.33 / 7.0.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click Patch available 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In the Linux kernel, the following vulnerability has been resolved: net: airoha: fix BQL imbalance in TX path Fix a possible BQL imbalance in airoha_dev_xmit(), where inflight packets are accounted only for the AIROHA_NUM_TX_RING netdev TX queues. The queue index is computed as: qid = skb_get_queue_mapping(skb) % ARRAY_SIZE(qdma->q_tx) txq = netdev_get_tx_queue(dev, qid); However, airoha_qdma_tx_napi_poll() accounts completions across all netdev TX queues (num_tx_queues), leading to inconsistent BQL accounting. Also reset all netdev TX queues in the ndo_stop callback.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The airoha network driver in the Linux kernel has a BQL (Byte Queue Limits) accounting imbalance where the TX submission path only accounts for AIROHA_NUM_TX_RING queues, but the completion handler (airoha_qdma_tx_napi_poll) accounts across ALL netdev TX queues (num_tx_queues). This mismatch causes inconsistent BQL state tracking, potentially leading to queue deadlocks or network performance degradation.

MitigationApply the kernel patch to align BQL accounting between TX submission and completion paths, and ensure all netdev TX queues are properly reset in the ndo_stop callback. Update to the patched kernel version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 6.12.91, < 6.18.33>= 6.19, < 7.0.10= 7.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check kernel version against affected ranges
    Run 'uname -r' to get the running kernel version and compare it to: >= 6.12.91 and < 6.18.33; OR >= 6.19 and < 7.0.10; OR exactly 7.1
    Affected if Kernel version falls within any of the affected version ranges
  2. Identify airoha network driver presence
    Check for airoha network devices or modules: run 'ls /sys/class/net/' to list network interfaces, then check 'ethtool -i <interface>' on each to identify the driver, or run 'lsmod | grep airoha' to find loaded modules
    Affected if An airoha network driver module is loaded or an airoha network interface exists
  3. Verify TX queue configuration
    For identified airoha interfaces, run 'ip link show <interface>' or check '/sys/class/net/<interface>/queues/' directory to confirm multiple TX queues are configured
    Affected if The interface has multiple TX queues (more than AIROHA_NUM_TX_RING value, typically 4-8 queues)
  4. Check BQL state for the interface
    Run 'cat /sys/class/net/<interface>/tx_queue_len' or use 'tc qdisc show' to inspect Byte Queue Limit configuration and queue lengths
    Affected if BQL queues show abnormal backlog or the tx_queue_len value is non-zero with stuck packets

User is affected if running a vulnerable kernel version AND the airoha network driver is actively managing network interfaces with multiple TX queues.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.18.33 / 7.0.10 or later
Fixed in 6.18.337.0.10
Vendor patch git.kernel.org →
Interim mitigation

Apply the kernel patch to align BQL accounting between TX submission and completion paths, and ensure all netdev TX queues are properly reset in the ndo_stop callback. Update to the patched kernel version.

Recommended fix High confidence

Kernel 6.18.33+ (6.18.y LTS) or 7.0.10+ (7.0.y LTS) or 7.2+

  1. Identify the current running kernel version using 'uname -r'
  2. Check if the current version is affected: it is affected if >= 6.12.91 and < 6.18.33, OR >= 6.19 and < 7.0.10, OR exactly 7.1
  3. For affected systems, upgrade the Linux kernel to version 6.18.33 or later in the 6.18.y stable tree, OR version 7.0.10 or later in the 7.0.y stable tree, OR any version 7.2 or later
  4. After kernel upgrade, reboot the system to load the fixed kernel
  5. Verify the fix is applied by checking the kernel version post-reboot
Caveat Kernel upgrades may require reboot and could introduce regressions in other drivers; ensure compatibility with system hardware before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Linux Kernel Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-52983 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-52983 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data