Skip to main content
VulnerabilityPublished Updated

CVE-2026-43491: Linux kernel · net: qrtr: ns: Limit the maximum server registration per node

Affects Linux kernelSource CVE Database V5

0
Compare

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

Data as of 6 Nov 2026, 16:04 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 e6f6cd501fb54060940a6eb3f4103eeb5e426ae7, d5ee2ff98322337951c56398e79d51815acbf955, b48fc702b20233b809f01053232c3cd5083c97b4 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 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, < e6f6cd501fb54060940a6eb3f4103eeb5e426ae7
Fixed in
  • e6f6cd501fb54060940a6eb3f4103eeb5e426ae7
LinuxLinuxAffected
  • ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < d5ee2ff98322337951c56398e79d51815acbf955
Fixed in
  • d5ee2ff98322337951c56398e79d51815acbf955
LinuxLinuxAffected
  • ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < b48fc702b20233b809f01053232c3cd5083c97b4
Fixed in
  • b48fc702b20233b809f01053232c3cd5083c97b4
LinuxLinuxAffected
  • ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 94914731ca0b99899dceadd80d2df00584a688ca
Fixed in
  • 94914731ca0b99899dceadd80d2df00584a688ca
LinuxLinuxAffected
  • ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 868202aa2adae427060a42d5bd663b4d782ec02c
Fixed in
  • 868202aa2adae427060a42d5bd663b4d782ec02c
LinuxLinuxAffected
  • ≥ 0c2204a4ad710d95d348ea006f14ba926e842ffd, < 991c431077b19176d3fe3bb54054c063776a8cdc
Fixed in
  • 991c431077b19176d3fe3bb54054c063776a8cdc

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

Community reviews

Loading reviews…