VulnerabilityPublished 27 May 2026Updated 6 Nov 2026

CVE-2026-46026: Linux kernel · net: qrtr: ns: Limit the maximum number of lookups

Affects Linux kernelSource CVE Database V5

Compare

Not known to be exploited · fixed in bd69e0e8a7643ba5385f19f479e8e3da71f8d495 : update Linux kernel when convenient.

Data as of 6 Nov 2026, 16:34 UTC

Severity

Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation: No evidence of active exploitation and no public proof of concept
Automatable: Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact: Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch

Available – fixed in bd69e0e8a7643ba5385f19f479e8e3da71f8d495, 5640227d9a21c6a8be249a10677b832e7f40dc55, 20855cef7e659ef84ac73251256fa530819b2346 +5

Exploitation evidence

Disclosed: evidence found.
CVE published 27 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < bd69e0e8a7643ba5385f19f479e8e3da71f8d495	Fixed in bd69e0e8a7643ba5385f19f479e8e3da71f8d495
LinuxLinux	Affected ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 5640227d9a21c6a8be249a10677b832e7f40dc55	Fixed in 5640227d9a21c6a8be249a10677b832e7f40dc55
LinuxLinux	Affected ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 20855cef7e659ef84ac73251256fa530819b2346	Fixed in 20855cef7e659ef84ac73251256fa530819b2346
LinuxLinux	Affected ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 91cb30b6bb1880ba0748ca059bef50b8ac13793d	Fixed in 91cb30b6bb1880ba0748ca059bef50b8ac13793d
LinuxLinux	Affected ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 76adf8f69b0bb3ab20be7c58f5d555027332d113	Fixed in 76adf8f69b0bb3ab20be7c58f5d555027332d113
LinuxLinux	Affected ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 6e3675251fcea06caecc61eb76462467558adfa6	Fixed in 6e3675251fcea06caecc61eb76462467558adfa6

Description

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 NEW_LOOKUP 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.

References

Community reviews

Loading reviews…