Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ed29887286aba96d1930f4ddb9f235f6b421073c : 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
CISA SSVC
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 ed29887286aba96d1930f4ddb9f235f6b421073c, b703ee903b24974aca4bde99c7d25d66309d35dd, 823310645065bd49666e84af689fa95192819f55 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < ed29887286aba96d1930f4ddb9f235f6b421073c
Fixed in
  • ed29887286aba96d1930f4ddb9f235f6b421073c
LinuxLinuxAffected
  • ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < b703ee903b24974aca4bde99c7d25d66309d35dd
Fixed in
  • b703ee903b24974aca4bde99c7d25d66309d35dd
LinuxLinuxAffected
  • ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 823310645065bd49666e84af689fa95192819f55
Fixed in
  • 823310645065bd49666e84af689fa95192819f55
LinuxLinuxAffected
  • ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 8022876894d09ae485b499058c3357da683bcc5d
Fixed in
  • 8022876894d09ae485b499058c3357da683bcc5d
LinuxLinuxAffected
  • ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 4665a29c08e1b36bc9db4814f9dde3d23e8fd1b0
Fixed in
  • 4665a29c08e1b36bc9db4814f9dde3d23e8fd1b0
LinuxLinuxAffected
  • ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 27d5e84e810b0849d08b9aec68e48570461ce313
Fixed in
  • 27d5e84e810b0849d08b9aec68e48570461ce313

Description

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.

References

Community reviews

Loading reviews…