Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 18 days later

    Published

  3. · 6 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-43491, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 0c2204a4ad710d95d348ea006f14ba926e842ffd – < b48fc702b20233b809f01053232c3cd5083c97b4
    • affected 0c2204a4ad710d95d348ea006f14ba926e842ffd – < 991c431077b19176d3fe3bb54054c063776a8cdc
    • affected 0c2204a4ad710d95d348ea006f14ba926e842ffd – < 94914731ca0b99899dceadd80d2df00584a688ca
    • affected 0c2204a4ad710d95d348ea006f14ba926e842ffd – < e6f6cd501fb54060940a6eb3f4103eeb5e426ae7
    • affected 0c2204a4ad710d95d348ea006f14ba926e842ffd – < 3efaad55cad1ded429e3a873bfece389058a526b
    • affected 0c2204a4ad710d95d348ea006f14ba926e842ffd – < 35fb4a0c077c5d1049c2628b769e0a1b1e65df0d
    • affected 0c2204a4ad710d95d348ea006f14ba926e842ffd – < 868202aa2adae427060a42d5bd663b4d782ec02c
    • affected 0c2204a4ad710d95d348ea006f14ba926e842ffd – < d5ee2ff98322337951c56398e79d51815acbf955
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.140 – ≤ 6.6.*
    • unaffected 6.12.86 – ≤ 6.12.*
    • unaffected 6.18.27 – ≤ 6.18.*
    • unaffected 7.0.4 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-43491 badge
[![CVE-2026-43491](https://cveledger.app/badge/CVE-2026-43491.svg)](https://cveledger.app/cve/CVE-2026-43491)

Record last updated .