{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.1.187-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.105-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "7.1.9-1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:12",
        "name": "linux-6.12"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.12.107-1~deb12u1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  vxlan: do not arm the ageing timer on a device that is down  vxlan_changelink() arms vxlan-\u003eage_timer whenever the requested ageing interval differs from the configured one:  \tif (conf.age_interval != vxlan-\u003ecfg.age_interval) \t\tmod_timer(\u0026vxlan-\u003eage_timer, jiffies);  There is no netif_running() test, so the timer is armed even on a device that was never brought up.  The only synchronous cancel in the driver is the timer_delete_sync() in vxlan_stop(), which is .ndo_stop. netif_close_many() drops devices without IFF_UP before __dev_close_many() runs, so that cancel is skipped for such a device.  vxlan_setup() sets dev-\u003eneeds_free_netdev = true and age_timer is a member of struct vxlan_dev, so free_netdev() releases the allocation the timer lives in while it is still queued on a timer_base. expire_timers() unlinks the entry before it loads timer-\u003efunction, so the timer core writes through the freed object's list pointers:    BUG: KASAN: slab-use-after-free in __run_timers+0x208/0x654   Write of size 8 at addr ffff00001adace68 by task true/192    __asan_store8+0x84/0xac    __run_timers+0x208/0x654    run_timer_softirq+0x154/0x18c   Allocated by task 189:    alloc_netdev_mqs+0x64/0x720    rtnl_create_link+0x4ac/0x520    rtnl_newlink+0x758/0xd00   Freed by task 191:    netdev_release+0x40/0x58    netdev_run_todo+0x4a4/0x8c0    rtnl_dellink+0x200/0x4e8  The rtnl operations involved are netns-scoped, so an unprivileged user can perform them in a new user and network namespace.  Arming the timer on a down device never had an effect: vxlan_cleanup() returns early on !netif_running(), and vxlan_open() arms the timer for any non-zero interval once the device is brought up.  Add the missing test.  Discovered by XBOW, triaged by Baul Lee \u003cbaul.lee@xbow.com\u003e",
  "id": "DEBIAN-CVE-2026-74615",
  "modified": "2026-09-19T21:47:34.550709923Z",
  "published": "2026-08-22T16:16:34.143Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-74615"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-74615"
  ]
}