CVE-2026-74615

CVE CVE-2026-74615EUVD EUVD-2026-64552Veröffentlicht 2026-08-22T15:32:00.000ZZuletzt geändert 2026-08-25T05:40:42.000ZCVSS 8.8

Was das Advisory beschreibt

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->age_timer whenever the requested ageing interval differs from the configured one: if (conf.age_interval != vxlan->cfg.age_interval) mod_timer(&vxlan->age_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->needs_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->function, 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 <baul.lee@xbow.com>

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux patch: 5.10.265; 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 <6b095e99b9e67ea31f0c4b00260e010898253519; 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 <be44d79d14d7f9ae7c8ffb7272142005341b5123; patch: 7.2; patch: 6.18.45; patch: 0; patch: 6.12.104; patch: 5.15.216; 5.0; 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 <9dc561f0522c35bdd66e0646a748814a138ec4ca; 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 <b37971686ec59fb027fa4910ba16805e68fddb97; 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 <26c179d47403d2f919ee914cc02c31d896b59fee; 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 <46bb297ad77680e009244f067f27d51cf5b8c7cf; patch: 6.6.152; 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 <619dd29045e439d0b0f8c6d4fec1af447a050680; patch: 6.1.183; patch: 7.1.9; 40051c4dcad5b374156ad9cceae8d15c0ef1cb95 <6b4119af544996a545cf84b16f1dbce829ba0de8

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.