CVE-2026-46026: net: qrtr: ns: Limit the maximum number of lookups
In the Linux kernel, the following vulnerability has been resolved:
net: qrtr: ns: Limit the maximum number of lookups
Current code does no bound checking on the number of lookups a client can perform. Though the code restricts the lookups to local clients, there is still a possibility of a malicious local client sending a flood of NEWLOOKUP messages over the same socket.
Fix this issue by limiting the maximum number of lookups to 64 globally. Since the nameserver allows only atmost one local observer, this global lookup count will ensure that the lookups stay within the limit.
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 6.6.141.1-1 - Configuration
Limit the maximum number of lookups globally to 64 in the net: qrtr: ns code path to prevent unbounded lookup message handling over the same socket.
Linux kernel (net: qrtr: ns) Maximum number of lookups (global) = 64
Event History
Frequently Asked Questions
Who can exploit this issue?
Systems are exposed when a local client can communicate with the QRTR nameserver. The issue is limited to local clients; the provided data does not indicate remote network exploitation.
What does an attacker need to do?
An attacker needs local access and the ability to send a flood of NEW_LOOKUP messages over the same socket. No user interaction is required, and the impact is denial of service through resource exhaustion.
What mitigation does the fix introduce?
The fix imposes a global maximum of 64 lookups. Because the nameserver permits at most one local observer, this global cap is intended to keep lookup activity within the supported limit.