CyberSecBulletin
CVE-2026-68294NVD status: Received

Linux: Missing Authorization

Published Updated By the CyberSecBulletin desk

CVE-2026-68294 is a high-severity missing authorization vulnerability in Linux, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 7814f6a3415cad38aa8d6dfc573df778260d66aa, 2d22b94a154ccb9755dddfff802fe3e2b1adbab5, 8d351fe0654a20c9f95a61b05d24ebe6d4be3fbb as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.15% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Linux to 7814f6a3415cad38aa8d6dfc573df778260d66aa or 2d22b94a154ccb9755dddfff802fe3e2b1adbab5 or 8d351fe0654a20c9f95a61b05d24ebe6d4be3fbb or 4b95e1f0d6e6342c427cb341ee18a894b146b789, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
LinuxLinuxbdabad3e363d825ddf9679dd431cca0b2c30f881 up to, but not including, 7814f6a3415cad38aa8d6dfc573df778260d66aa; bdabad3e363d825ddf9679dd431cca0b2c30f881 up to, but not including, 2d22b94a154ccb9755dddfff802fe3e2b1adbab5; bdabad3e363d825ddf9679dd431cca0b2c30f881 up to, but not including, 8d351fe0654a20c9f95a61b05d24ebe6d4be3fbb; bdabad3e363d825ddf9679dd431cca0b2c30f881 up to, but not including, 4b95e1f0d6e6342c427cb341ee18a894b146b789; bdabad3e363d825ddf9679dd431cca0b2c30f881 up to, but not including, f488116df769bdaf89c93371350e49e12133e70f; bdabad3e363d825ddf9679dd431cca0b2c30f881 up to, but not including, 8150c48fb978e01689f94ed80148f8a7499ae571; bdabad3e363d825ddf9679dd431cca0b2c30f881 up to, but not including, 659b9b4f194bb56b9903cc95e786ef1d438baa7d; bdabad3e363d825ddf9679dd431cca0b2c30f881 up to, but not including, 3b536db8fb32da9e9c62f2bb45e2e319331f0426; and 1 more ranges7814f6a3415cad38aa8d6dfc573df778260d66aa, 2d22b94a154ccb9755dddfff802fe3e2b1adbab5, 8d351fe0654a20c9f95a61b05d24ebe6d4be3fbb, 4b95e1f0d6e6342c427cb341ee18a894b146b789, f488116df769bdaf89c93371350e49e12133e70f, 8150c48fb978e01689f94ed80148f8a7499ae571

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA.

Official 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).

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Missing Authorization vulnerabilities (CWE-862)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Recent Missing Authorization vulnerabilities

Spotted an error? Tell us.