CVE-2026-46003: net: qrtr: ns: Limit the total number of nodes

Published May 27, 2026
·
Updated

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

net: qrtr: ns: Limit the total number of nodes

Currently, the nameserver doesn't limit the number of nodes it handles. This can be an attack vector if a malicious client starts registering random nodes, leading to memory exhaustion.

Hence, limit the maximum number of nodes to 64. Note that, limit of 64 is chosen based on the current platform requirements. If requirement changes in the future, this limit can be increased.

Affected Software

6 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=5.7<6.6.140
Linux Linux kernel>=6.7<6.12.86
Linux Linux kernel>=6.13<6.18.27
Linux Linux kernel>=6.19<7.0.4
Microsoft azl3 kernel 6.6.139.1-1<6.6.141.1-1
6.6.141.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.141.1-1
  2. Configuration

    Set the Linux kernel QRTR nameservice (net: qrtr: ns) limit for the total number of nodes to 64 to prevent memory exhaustion from malicious clients registering random nodes.

    Linux kernel (net: qrtr: ns) Maximum total number of nodes = 64

Event History

May 27, 2026
CVE Published
via MITRE·12:55 PM
Data Sourced
via MITRE·12:55 PM
Description
Data Sourced
via NVD·02:17 PM
RemedyDescriptionSeverityAffected Software
May 28, 2026
Data Sourced
via Microsoft·08:12 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:12 AM
Affected Software
Updated
via Microsoft·08:12 AM
DescriptionSeverity

Frequently Asked Questions

1

Who is realistically exposed to this issue?

Systems running a Linux kernel with the QRTR nameserver exposed to local clients are relevant. An attacker needs local access with low privileges; no user interaction is required.

2

What does exploitation require and what is the impact?

The attacker registers random QRTR nodes until the nameserver's memory is exhausted, causing a denial of service. The affected nameserver previously had no total node limit; the resolved behavior caps it at 64 nodes.

3

What can defenders do to mitigate or detect this issue?

The provided remediation is the kernel change that limits the QRTR nameserver to 64 total nodes. If that change is not present, monitor for unexpected or rapidly growing QRTR node registrations as an indication of attempted exhaustion.

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