CVE-2026-43491: Linux kernel · net: qrtr: ns: Limit the maximum server registration per node
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e6f6cd501fb54060940a6eb3f4103eeb5e426ae7 : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:04 UTC
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 e6f6cd501fb54060940a6eb3f4103eeb5e426ae7, d5ee2ff98322337951c56398e79d51815acbf955, b48fc702b20233b809f01053232c3cd5083c97b4 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 19 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.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
Description
In the Linux kernel, the following vulnerability has been resolved: net: qrtr: ns: Limit the maximum server registration per node Current code does no bound checking on the number of servers added per node. A malicious client can flood NEW_SERVER messages and exhaust memory. Fix this issue by limiting the maximum number of server registrations to 256 per node. If the NEW_SERVER message is received for an old port, then don't restrict it as it will get replaced. While at it, also rate limit the error messages in the failure path of qrtr_ns_worker(). Note that the limit of 256 is chosen based on the current platform requirements. If requirement changes in the future, this limit can be increased.
References
- git.kernel.org/stable/c/b48fc702b20233b809f01053232c3cd5083c97b4 (opens in a new tab)
- git.kernel.org/stable/c/991c431077b19176d3fe3bb54054c063776a8cdc (opens in a new tab)
- git.kernel.org/stable/c/94914731ca0b99899dceadd80d2df00584a688ca (opens in a new tab)
- git.kernel.org/stable/c/e6f6cd501fb54060940a6eb3f4103eeb5e426ae7 (opens in a new tab)
- git.kernel.org/stable/c/3efaad55cad1ded429e3a873bfece389058a526b (opens in a new tab)
- git.kernel.org/stable/c/35fb4a0c077c5d1049c2628b769e0a1b1e65df0d (opens in a new tab)
- git.kernel.org/stable/c/868202aa2adae427060a42d5bd663b4d782ec02c (opens in a new tab)
- git.kernel.org/stable/c/d5ee2ff98322337951c56398e79d51815acbf955 (opens in a new tab)