{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.180-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.100-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "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:  ipv4: fib: Don't ignore error route in local/main tables.  When CONFIG_IP_MULTIPLE_TABLES is enabled but no rule is added, fib_lookup() performs route lookup directly on two tables.  Since the first lookup does not properly bail out, the result of an error route in the merged local/main table could be overwritten by another route in the default table:    # unshare -n   # ip link set lo up   # ip route add 192.168.0.0/24 dev lo table 253   # ip route add unreachable 192.168.0.0/24   # ip route get 192.168.0.1   192.168.0.1 dev lo table default uid 0       cache \u003clocal\u003e  Once a random rule is added, the error route is respected:    # ip rule add table 0   # ip rule del table 0   # ip route get 192.168.0.1   RTNETLINK answers: No route to host  Let's fix the inconsistent behaviour.",
  "id": "DEBIAN-CVE-2026-72421",
  "modified": "2026-09-14T16:47:31.967016479Z",
  "published": "2026-08-15T06:22:15.867Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-72421"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-72421"
  ]
}