CVE-2026-68294High· 8.8▾ TwilightIn 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 …
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 48.4 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.2%
Last analysed / modified upstream
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).
Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 7814f6a3415cad38aa8d6dfc573df778260d66aaLinux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 2d22b94a154ccb9755dddfff802fe3e2b1adbab5Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 8d351fe0654a20c9f95a61b05d24ebe6d4be3fbbLinux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 4b95e1f0d6e6342c427cb341ee18a894b146b789Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < f488116df769bdaf89c93371350e49e12133e70fLinux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 8150c48fb978e01689f94ed80148f8a7499ae571Linux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 659b9b4f194bb56b9903cc95e786ef1d438baa7dLinux >= bdabad3e363d825ddf9679dd431cca0b2c30f881 < 3b536db8fb32da9e9c62f2bb45e2e319331f0426Linux 4.7Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets