CVE-2026-97985

CVE CVE-2026-97985EUVD EUVD-2026-86639Published 2026-09-25T10:23:20.000Z

What the advisory describes

In the Linux kernel, the following vulnerability has been resolved: af_unix: Update last skb marker in manage_oob(). Fahad Alharbi reported that blocking recv(MSG_PEEK) could hog CPU due to OOB skb. In the following cases, manage_oob() skips OOB skb(s) and returns NULL for the last recv(MSG_PEEK): socketpair(AF_UNIX, SOCK_STREAM, 0, sk); 1) skb -> OOB skb -> NULL send(sk[0], "ab", 2, MSG_OOB); recv(sk[1], buf, 0, MSG_PEEK); 2) skb -> consumed OOB skb -> NULL send(sk[0], "ab", 2, MSG_OOB); recv(sk[1], buf, 1, MSG_OOB); recv(sk[1], buf, 0, MSG_PEEK); 3) consumed OOB skb -> OOB skb -> NULL send(sk[0], "a", 1, MSG_OOB); recv(sk[1], buf, 0, MSG_OOB); send(sk[0], "b", 1, MSG_OOB); recv(sk[1], buf, 1, MSG_PEEK); Then, @copied is 0 in unix_stream_read_generic() (zero-length buffer, or non-OOB skb is not yet consumed), and unix_stream_data_wait() is called. However, it returns immediately because @last is not updated in unix_stream_read_generic(), and the thread busy-waits for a new skb. Let's update @last in manage_oob(). For MSG_PEEK, @last is updated with the skipped OOB, and for the non-peek case, @last matches the returned value (when !copied) because OOB is unlinked. Note that manage_oob() is inlined and no stack canary is added.

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 22dd70eb2c3d754862964377a75abafd3167346b <f1816b3d7ce80dcf086bb68ff5ae6e09520ca1fa; 022d81a709cd553bbe2db8675f8e824f4aee6284; patch: 6.12.111; 6.8.8 <6.9; patch: 6.18.53; 22dd70eb2c3d754862964377a75abafd3167346b <fc62a26493a98a0424d9dae2eb92a1daa1321f65; ae3f9e1221b31b18dbd4c4b85d08574996bbd973; 22dd70eb2c3d754862964377a75abafd3167346b <0630bfc773d85ac44da05b2c5a037dbbd39301ab; ba0db4638525b8b054b3d546b45f7e473f477027; patch: 0; 16dc252e7007547a7b72a2c21022ef81fb45e6a3; 6.9; patch: 7.3-rc3; 6.1.88 <6.2; 6.6.29 <6.7; patch: 7.2.7; 5.15.157 <5.16; 22dd70eb2c3d754862964377a75abafd3167346b <94fd4debd2e3a69cf93e766c8b328a810c228119

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

Does this concern one of your customers?

This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.

Try it for 28 days

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.