{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.5-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  ipv6: ioam: fix type confusion of dst_entry  IOAM uses a dummy dst_entry(null_dst) to mark that the destination should not be changed after the transformation. This dst is stored in the IOAM lwt state and may be passed to dst_cache_set_ip6().  However, the IPv6 dst cache path eventually calls rt6_get_cookie(), which treats the dst_entry as part of a struct rt6_info. Since the null_dst was embedded directly as a struct dst_entry in struct ioam6_lwt, this resulted in an invalid cast and rt6_get_cookie() reading fields from the wrong object.  In practice, the wrong cookie is not used while dst-\u003eobsolete is zero, but rt6_get_cookie() may also access per-cpu value when rt-\u003esernum is zero. In this case, rt-\u003esernum aliases ioam6_lwt::cache::reset_ts, which can become zero, making this a potential invalid pointer access.  Fix this by embedding a full struct rt6_info for the dummy IPv6 route and passing its dst member to the dst APIs.",
  "id": "DEBIAN-CVE-2026-72429",
  "modified": "2026-09-14T16:47:45.508612079Z",
  "published": "2026-08-15T06:22:16.770Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-72429"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-72429"
  ]
}