CVE-2026-68137

CVE CVE-2026-68137EUVD EUVD-2026-55518Published 2026-08-10T11:59:00.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: net/x25: fix use-after-free in x25_kill_by_neigh() x25_kill_by_neigh() walks the global X.25 socket list looking for sockets attached to a terminating neighbour. x25_list_lock protects list membership while the lookup is in progress, but it does not pin a socket's lifetime after the lock is dropped. The function currently drops x25_list_lock before calling lock_sock(s). A concurrent close can run x25_release(), remove the same socket from x25_list, and drop the last socket reference in that window. The neighbour teardown path can then lock or inspect a freed struct sock/struct x25_sock. Take sock_hold(s) while x25_list_lock still proves that the list entry is live, then drop the temporary reference after the socket has been locked, rechecked, and released. Recheck x25_sk(s)->neighbour after lock_sock(), because another path may have disconnected the socket before this path acquired the socket lock. Restart the list walk after each disconnect because the list lock was dropped and the previous iterator state may no longer be valid. A QEMU/KASAN run against origin/master reproduced a slab-use-after-free in x25_kill_by_neigh().

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux 7781607938c8371d4c2b243527430241c62e39c2 <9aabda553184346f74810e2ee1d96920b4612e3f; 858642789ada1b48630f322e59416ca9fca3e6b7; patch: 6.18.42; patch: 6.6.148; 5.15.33 <5.16; 671529db75e6be777bb1c76aa07c2bdd2992be6d; 7781607938c8371d4c2b243527430241c62e39c2 <3f4fe26c20c30bd5a2e2583e80685def0b27858c; 4.14.276 <4.15; patch: 6.12.101; 4.9.311 <4.10; 5.18; 4.19.238 <4.20; patch: 7.2-rc5; 5.16.19 <5.17; 7781607938c8371d4c2b243527430241c62e39c2 <610678d4be94b619c751572e8a58de705592cd07; 5.17.2 <5.18; 5c94b6205e87411dbe9dc1ca088eb36b8837fb47; dffc859d1d9560da594e4282091781b8d2715f00; 9acf05b4e7b55fdb712ef7b331dbce5bcd391d0f; 5.10.110 <5.11; 7781607938c8371d4c2b243527430241c62e39c2 <5499e0602d2faafd42c580d25f615903c3fbe11b; patch: 0; 409570a619c1cda2e0fde6018a256b9e3d3ba0ee; 7781607938c8371d4c2b243527430241c62e39c2 <ec6d91a1bf2ebd767d3d43f6d249ee0ed3f4558a; patch: 7.1.6; 5.4.189 <5.5; 4a279d7ee1c65411b4055ecd428b8aa2b1711c1f; 4c240c5a105557e4546d0836e694868f22fd09b0

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.