UBUNTU-CVE-2026-19742 (CVE-2026-19742)

Vulnerability from osv_ubuntu – Published: 2026-10-26 17:17 – Updated: 2026-10-28 17:32 – Source website
VLAI
Details

The IPv6 stack derived the long-lived secret key used to compute RFC 7217 stable interface identifiers (gen_stable_iid() in subsys/net/ip/ipv6.c) and RFC 8981 temporary interface identifiers (gen_temporary_iid() in subsys/net/ip/ipv6_pe.c) with sys_rand_get(). That API is documented as not cryptographically secure, while both RFCs require this key to be an unpredictable random value of at least 128 bits — the unpredictability of every generated IID rests entirely on it. Depending on the platform, sys_rand_get() resolves either to a hardware entropy device or, on boards whose entropy driver sets CONFIG_ENTROPY_NEEDS_PRNG, to the non-cryptographic xoshiro128++ generator in subsys/random/random_xoshiro128.c, which keeps a single global 128-bit state shared with every other sys_rand_get() consumer. Many of those consumers put their output directly on the wire (ephemeral source ports, DNS query IDs, CoAP message IDs and tokens, DHCPv6 transaction IDs, WebSocket masking keys), and the xoshiro state transition is invertible, so an observer of a device's traffic can recover the generator state and reconstruct the IID secret key. Additionally, with the entropy-device backend sys_rand_get() silently falls back to k_cycle_get_32() samples when the entropy driver fails, and returns no error, so the key could be derived from the cycle counter without the caller noticing. With the key known, stable IIDs become directly computable for any prefix (the remaining HMAC inputs — prefix, interface index, interface name, DAD counter — are guessable), and temporary IIDs become linkable after a cheap search over the mixed-in k_uptime_get_32() value. This defeats the properties both features exist to provide: an attacker can track a device across networks and prefixes, and can predict its address inside a /64 without scanning, removing the usual barrier to directly targeting the host. There is no memory-safety, integrity, or availability impact. The fix generates the key with sys_csrand_get() and aborts IID generation with -EIO when no cryptographic randomness is available, instead of silently deriving addresses from a predictable key. Both CONFIG_NET_IPV6_IID_STABLE and CONFIG_NET_IPV6_PE are experimental and disabled by default; builds using CONFIG_TEST_RANDOM_GENERATOR remain predictable by design, as sys_csrand_get() is deliberately routed back to the test generator there.

Upstream
Impacted products
Ecosystem Package Version
Ubuntu:16.04:LTS zephyr
pkg:deb/ubuntu/zephyr@3.1.2-1build1?arch=source&distro=xenial
Affected: All versions (ecosystem)
3.1.2-13.1.2-1build1
Ubuntu:18.04:LTS zephyr
pkg:deb/ubuntu/zephyr@3.1.2-1build2?arch=source&distro=bionic
Affected: All versions (ecosystem)
3.1.2-1build13.1.2-1build2
Ubuntu:20.04:LTS zephyr
pkg:deb/ubuntu/zephyr@3.1.2-1build3?arch=source&distro=focal
Affected: All versions (ecosystem)
3.1.2-1build3
Ubuntu:22.04:LTS zephyr
pkg:deb/ubuntu/zephyr@3.1.2-1build3?arch=source&distro=jammy
Affected: All versions (ecosystem)
3.1.2-1build3
Ubuntu:24.04:LTS zephyr
pkg:deb/ubuntu/zephyr@3.1.2-1.1build1?arch=source&distro=noble
Affected: All versions (ecosystem)
3.1.2-1.13.1.2-1.1build1
Ubuntu:26.10 zephyr
pkg:deb/ubuntu/zephyr@3.1.2-4?arch=source&distro=stonking
Affected: All versions (ecosystem)
3.1.2-4
Ubuntu:26.04:LTS zephyr
pkg:deb/ubuntu/zephyr@3.1.2-4?arch=source&distro=resolute
Affected: All versions (ecosystem)
3.1.2-1.1build13.1.2-4

{
  "affected": [
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1build1"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1build1"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1build1"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1build1"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1build1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:16.04:LTS",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build1?arch=source\u0026distro=xenial"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1",
        "3.1.2-1build1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1build2"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1build2"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1build2"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1build2"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1build2"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:18.04:LTS",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build2?arch=source\u0026distro=bionic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1build1",
        "3.1.2-1build2"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1build3"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:20.04:LTS",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build3?arch=source\u0026distro=focal"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1build3"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1build3"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1build3"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:22.04:LTS",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-1build3?arch=source\u0026distro=jammy"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1build3"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-1.1build1"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-1.1build1"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-1.1build1"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-1.1build1"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-1.1build1"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:24.04:LTS",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-1.1build1?arch=source\u0026distro=noble"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1.1",
        "3.1.2-1.1build1"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-4"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-4"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-4"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-4"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-4"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:26.10",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-4?arch=source\u0026distro=stonking"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-4"
      ]
    },
    {
      "ecosystem_specific": {
        "binaries": [
          {
            "binary_name": "libzephyr4",
            "binary_version": "3.1.2-4"
          },
          {
            "binary_name": "libzephyr4-krb5",
            "binary_version": "3.1.2-4"
          },
          {
            "binary_name": "zephyr-clients",
            "binary_version": "3.1.2-4"
          },
          {
            "binary_name": "zephyr-server",
            "binary_version": "3.1.2-4"
          },
          {
            "binary_name": "zephyr-server-krb5",
            "binary_version": "3.1.2-4"
          }
        ]
      },
      "package": {
        "ecosystem": "Ubuntu:26.04:LTS",
        "name": "zephyr",
        "purl": "pkg:deb/ubuntu/zephyr@3.1.2-4?arch=source\u0026distro=resolute"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.1.2-1.1build1",
        "3.1.2-4"
      ]
    }
  ],
  "aliases": [],
  "details": "The IPv6 stack derived the long-lived secret key used to compute RFC 7217 stable interface identifiers (gen_stable_iid() in subsys/net/ip/ipv6.c) and RFC 8981 temporary interface identifiers (gen_temporary_iid() in subsys/net/ip/ipv6_pe.c) with sys_rand_get(). That API is documented as not cryptographically secure, while both RFCs require this key to be an unpredictable random value of at least 128 bits \u2014 the unpredictability of every generated IID rests entirely on it. Depending on the platform, sys_rand_get() resolves either to a hardware entropy device or, on boards whose entropy driver sets CONFIG_ENTROPY_NEEDS_PRNG, to the non-cryptographic xoshiro128++ generator in subsys/random/random_xoshiro128.c, which keeps a single global 128-bit state shared with every other sys_rand_get() consumer. Many of those consumers put their output directly on the wire (ephemeral source ports, DNS query IDs, CoAP message IDs and tokens, DHCPv6 transaction IDs, WebSocket masking keys), and the xoshiro state transition is invertible, so an observer of a device\u0027s traffic can recover the generator state and reconstruct the IID secret key. Additionally, with the entropy-device backend sys_rand_get() silently falls back to k_cycle_get_32() samples when the entropy driver fails, and returns no error, so the key could be derived from the cycle counter without the caller noticing. With the key known, stable IIDs become directly computable for any prefix (the remaining HMAC inputs \u2014 prefix, interface index, interface name, DAD counter \u2014 are guessable), and temporary IIDs become linkable after a cheap search over the mixed-in k_uptime_get_32() value. This defeats the properties both features exist to provide: an attacker can track a device across networks and prefixes, and can predict its address inside a /64 without scanning, removing the usual barrier to directly targeting the host. There is no memory-safety, integrity, or availability impact. The fix generates the key with sys_csrand_get() and aborts IID generation with -EIO when no cryptographic randomness is available, instead of silently deriving addresses from a predictable key. Both CONFIG_NET_IPV6_IID_STABLE and CONFIG_NET_IPV6_PE are experimental and disabled by default; builds using CONFIG_TEST_RANDOM_GENERATOR remain predictable by design, as sys_csrand_get() is deliberately routed back to the test generator there.",
  "id": "UBUNTU-CVE-2026-19742",
  "modified": "2026-10-28T17:32:48Z",
  "published": "2026-10-26T17:17:00Z",
  "references": [
    {
      "type": "REPORT",
      "url": "https://ubuntu.com/security/CVE-2026-19742"
    },
    {
      "type": "REPORT",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-19742"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/zephyrproject-rtos/zephyr"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/cveproject/cvelistv5/tree/main/cves/2026/19xxx/cve-2026-19742.json"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/zephyrproject-rtos/zephyr/commit/253315829d3cb5906c660d8418d8408d40bd266f"
    },
    {
      "type": "REPORT",
      "url": "https://github.com/zephyrproject-rtos/zephyr/security/advisories/ghsa-xfm2-gr93-8mx9"
    },
    {
      "type": "REPORT",
      "url": "https://nvd.nist.gov/vuln/detail/cve-2026-19742"
    }
  ],
  "related": [],
  "schema_version": "1.7.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "medium",
      "type": "Ubuntu"
    }
  ],
  "upstream": [
    "CVE-2026-19742"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.