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-68294net: qrtr: restrict socket creation to the initial network namespace

Description

In the Linux kernel, the following vulnerability has been resolved: net: qrtr: restrict socket creation to the initial network namespace QRTR keeps its entire port and node state in module-global variables that are not partitioned per network namespace: qrtr_local_nid is a single global node id (always 1) and qrtr_ports is a single global xarray. qrtr_port_lookup() and qrtr_local_enqueue() operate on that global state with no network-namespace check, and qrtr_create() places no restriction on the namespace a socket is created in. As a result an unprivileged process that creates an AF_QIPCRTR socket in a separate network namespace, e.g. via unshare(CLONE_NEWUSER | CLONE_NEWNET), can send QRTR datagrams - including control-plane messages such as QRTR_TYPE_NEW_SERVER - to QRTR sockets owned by another namespace, and vice versa. The receiving socket sees such a message as coming from node id 1, indistinguishable from a legitimate local client, breaking the isolation that network namespaces are expected to provide. QRTR is a transport to global hardware endpoints (the modem and other remote processors) and has no per-namespace semantics; its in-kernel name service already creates its socket in init_net only. Confine the socket family to the initial network namespace, as other non-namespace-aware socket families do (see llc_ui_create() and the ieee802154 socket code).

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 2 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-68294, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVDNVD · Received3.1High8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected bdabad3e363d825ddf9679dd431cca0b2c30f881 – < 7814f6a3415cad38aa8d6dfc573df778260d66aa
    • affected bdabad3e363d825ddf9679dd431cca0b2c30f881 – < 2d22b94a154ccb9755dddfff802fe3e2b1adbab5
    • affected bdabad3e363d825ddf9679dd431cca0b2c30f881 – < 8d351fe0654a20c9f95a61b05d24ebe6d4be3fbb
    • affected bdabad3e363d825ddf9679dd431cca0b2c30f881 – < 4b95e1f0d6e6342c427cb341ee18a894b146b789
    • affected bdabad3e363d825ddf9679dd431cca0b2c30f881 – < f488116df769bdaf89c93371350e49e12133e70f
    • affected bdabad3e363d825ddf9679dd431cca0b2c30f881 – < 8150c48fb978e01689f94ed80148f8a7499ae571
    • affected bdabad3e363d825ddf9679dd431cca0b2c30f881 – < 659b9b4f194bb56b9903cc95e786ef1d438baa7d
    • affected bdabad3e363d825ddf9679dd431cca0b2c30f881 – < 3b536db8fb32da9e9c62f2bb45e2e319331f0426
  • Linux · Linux

    • affected 4.7
    • unaffected < 4.7
    • unaffected 5.10.265 – ≤ 5.10.*
    • unaffected 5.15.216 – ≤ 5.15.*
    • unaffected 6.1.183 – ≤ 6.1.*
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .