CVE-2026-97985af_unix: Update last skb marker in manage_oob().
- —Not scoredno CVSS score yet
- 0.17%Exploitation in 30 daysEPSS · top 94% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
Published
- 26 days later
· 26 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.17% · top 94% of all CVEs (14 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected 022d81a709cd553bbe2db8675f8e824f4aee6284 – < bd91dc313afe21e9d6b31ca6a47606a33ca5e35c
- affected 22dd70eb2c3d754862964377a75abafd3167346b – < 0630bfc773d85ac44da05b2c5a037dbbd39301ab
- affected 22dd70eb2c3d754862964377a75abafd3167346b – < f1816b3d7ce80dcf086bb68ff5ae6e09520ca1fa
- affected 22dd70eb2c3d754862964377a75abafd3167346b – < fc62a26493a98a0424d9dae2eb92a1daa1321f65
- affected 22dd70eb2c3d754862964377a75abafd3167346b – < 94fd4debd2e3a69cf93e766c8b328a810c228119
- affected ae3f9e1221b31b18dbd4c4b85d08574996bbd973
- affected ba0db4638525b8b054b3d546b45f7e473f477027
- affected 16dc252e7007547a7b72a2c21022ef81fb45e6a3
- affected 6.6.29 – < 6.6.160
- affected 5.15.157 – < 5.16
- affected 6.1.88 – < 6.2
- affected 6.8.8 – < 6.9
- affected 6.9
- unaffected < 6.9
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.53 – ≤ 6.18.*
- unaffected 7.2.7 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References5
- https://git.kernel.org/stable/c/bd91dc313afe21e9d6b31ca6a47606a33ca5e35c (opens in a new tab)
- https://git.kernel.org/stable/c/0630bfc773d85ac44da05b2c5a037dbbd39301ab (opens in a new tab)
- https://git.kernel.org/stable/c/f1816b3d7ce80dcf086bb68ff5ae6e09520ca1fa (opens in a new tab)
- https://git.kernel.org/stable/c/fc62a26493a98a0424d9dae2eb92a1daa1321f65 (opens in a new tab)
- https://git.kernel.org/stable/c/94fd4debd2e3a69cf93e766c8b328a810c228119 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-86639 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-97985)Record last updated .