CVE-2026-52983: net: airoha: fix BQL imbalance in TX path

Published Jun 24, 2026
·
Updated

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

net: airoha: fix BQL imbalance in TX path

Fix a possible BQL imbalance in airohadevxmit(), where inflight packets are accounted only for the AIROHANUMTXRING netdev TX queues. The queue index is computed as:

qid = skbgetqueuemapping(skb) % ARRAYSIZE(qdma->qtx) txq = netdevgettxqueue(dev, qid);

However, airohaqdmatxnapipoll() accounts completions across all netdev TX queues (numtxqueues), leading to inconsistent BQL accounting.

Also reset all netdev TX queues in the ndostop callback.

Affected Software

7 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=6.12.91<6.18.33
Linux Linux kernel>=6.19<7.0.10
Linux Linux kernel=7.1-rc1
debian/linux<6.12.115-2
6.12.115-2
debian/linux<7.0.10-1
7.0.10-1
debian/linux<=6.12.107-1
6.1.176-16.1.190-16.12.115-27.2.12-17.2.15-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Update the TX path so BQL accounting is consistent: completions in airoha_qdma_tx_napi_poll() must account across all netdev TX queues (num_tx_queues), while packet accounting uses the computed queue index qid = skb_get_queue_mapping(skb) % ARRAY_SIZE(qdma->q_tx) and selects txq = netdev_get_tx_queue(dev, qid).

    Linux kernel net: airoha TX path BQL accounting (netdev TX queues) = Account completions across all num_tx_queues instead of only AIROHA_NUM_TX_RING; compute qid as skb_get_queue_mapping(skb) % ARRAY_SIZE(qdma->q_tx) and use it to select txq via netdev_get_tx_queue(dev, qid)
  2. Operational

    Reset all netdev TX queues in the ndo_stop callback.

Event History

Jun 24, 2026
CVE Published
via MITRE·04:28 PM
Data Sourced
via MITRE·04:28 PM
DescriptionSeverity
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via OSV·05:17 PM
DescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What level of access does an attacker need to exploit this issue?

The provided severity vector indicates network reachability, low attack complexity, no required privileges, and no user interaction.

2

What is the expected security impact?

The severity vector indicates a high availability impact, with no stated confidentiality or integrity impact.

3

Which systems are most relevant for triage?

Prioritize Linux systems using the Airoha network driver and its TX path, where BQL accounting can become inconsistent across netdev TX queues.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203