{"id":"CVE-2026-68294","title":"net: qrtr: restrict socket creation to the initial network namespace","summary":"In the Linux kernel, the following vulnerability has been resolved:\n\nnet: qrtr: restrict socket creation to the initial network namespace\n\nQRTR keeps its entire port and node state in module-global variables\nthat are not partitioned per …","severity":"high","cvss":8.8,"cvssVector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","cvssSource":"cna","vendor":"Linux","product":"Linux","affected":["Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 7814f6a3415cad38aa8d6dfc573df778260d66aa","Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 2d22b94a154ccb9755dddfff802fe3e2b1adbab5","Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 8d351fe0654a20c9f95a61b05d24ebe6d4be3fbb","Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 4b95e1f0d6e6342c427cb341ee18a894b146b789","Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < f488116df769bdaf89c93371350e49e12133e70f","Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 8150c48fb978e01689f94ed80148f8a7499ae571","Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 659b9b4f194bb56b9903cc95e786ef1d438baa7d","Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 3b536db8fb32da9e9c62f2bb45e2e319331f0426","Linux 4.7"],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"total","timestamp":"2026-10-16T15:46:44.239269Z"},"published":"2026-08-10","updated":"2026-10-16","sourceUpdated":"2026-10-16T15:53:06.763Z","source":"CVEORG","sourceUrl":"https://www.cve.org/CVERecord?id=CVE-2026-68294","references":[{"url":"https://git.kernel.org/stable/c/7814f6a3415cad38aa8d6dfc573df778260d66aa"},{"url":"https://git.kernel.org/stable/c/2d22b94a154ccb9755dddfff802fe3e2b1adbab5"},{"url":"https://git.kernel.org/stable/c/8d351fe0654a20c9f95a61b05d24ebe6d4be3fbb"},{"url":"https://git.kernel.org/stable/c/4b95e1f0d6e6342c427cb341ee18a894b146b789"},{"url":"https://git.kernel.org/stable/c/f488116df769bdaf89c93371350e49e12133e70f"},{"url":"https://git.kernel.org/stable/c/8150c48fb978e01689f94ed80148f8a7499ae571"},{"url":"https://git.kernel.org/stable/c/659b9b4f194bb56b9903cc95e786ef1d438baa7d"},{"url":"https://git.kernel.org/stable/c/3b536db8fb32da9e9c62f2bb45e2e319331f0426"}],"tags":["cve.org"],"epss":0.00169,"epssPercentile":0.05792,"ingestedAt":"2026-10-16T17:24:46.855Z","slug":"CVE-2026-68294","body":"## Overview\n\nIn the Linux kernel, the following vulnerability has been resolved:\n\nnet: qrtr: restrict socket creation to the initial network namespace\n\nQRTR keeps its entire port and node state in module-global variables\nthat are not partitioned per network namespace: qrtr_local_nid is a\nsingle global node id (always 1) and qrtr_ports is a single global\nxarray. qrtr_port_lookup() and qrtr_local_enqueue() operate on that\nglobal state with no network-namespace check, and qrtr_create() places\nno restriction on the namespace a socket is created in.\n\nAs a result an unprivileged process that creates an AF_QIPCRTR socket\nin a separate network namespace, e.g. via\nunshare(CLONE_NEWUSER | CLONE_NEWNET), can send QRTR datagrams -\nincluding control-plane messages such as QRTR_TYPE_NEW_SERVER - to QRTR\nsockets owned by another namespace, and vice versa. The receiving\nsocket sees such a message as coming from node id 1, indistinguishable\nfrom a legitimate local client, breaking the isolation that network\nnamespaces are expected to provide.\n\nQRTR is a transport to global hardware endpoints (the modem and other\nremote processors) and has no per-namespace semantics; its in-kernel\nname service already creates its socket in init_net only. Confine the\nsocket family to the initial network namespace, as other\nnon-namespace-aware socket families do (see llc_ui_create() and the\nieee802154 socket code).\n\n## Affected\n\n- `Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 7814f6a3415cad38aa8d6dfc573df778260d66aa`\n- `Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 2d22b94a154ccb9755dddfff802fe3e2b1adbab5`\n- `Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 8d351fe0654a20c9f95a61b05d24ebe6d4be3fbb`\n- `Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 4b95e1f0d6e6342c427cb341ee18a894b146b789`\n- `Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < f488116df769bdaf89c93371350e49e12133e70f`\n- `Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 8150c48fb978e01689f94ed80148f8a7499ae571`\n- `Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 659b9b4f194bb56b9903cc95e786ef1d438baa7d`\n- `Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 3b536db8fb32da9e9c62f2bb45e2e319331f0426`\n- `Linux 4.7`\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.","depth":"twilight","depthScore":48,"depthScoreParts":{"impact":48.4,"likelihood":0,"exploitation":0,"ransomware":0},"changes":[]}