CVE-2026-98394: Linux kernel · af_unix: Return immediately when manage_oob() returns NULL for 0-length buffer.
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in d5dd55b316ca229a4cbf11729483ba5bb57233e7 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in d5dd55b316ca229a4cbf11729483ba5bb57233e7, c81c5be3826c8467945b964d0cf7f7b3d65461db, 6e5ee08eb5858d175da6768d75d163817b6a9d4a +1
Exploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade Linux kernel to d5dd55b316ca229a4cbf11729483ba5bb57233e7, c81c5be3826c8467945b964d0cf7f7b3d65461db, 6e5ee08eb5858d175da6768d75d163817b6a9d4a or 3d3c7a3df66b2ca3d2cd1a2a0c37eb701feba713.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
The issue has been fixed in specific Linux kernel commits identified by their hashes. Users should apply the official Linux kernel updates that include these fixes to remediate the vulnerability.
Description
A vulnerability in the Linux kernel's af_unix subsystem caused a busy-wait condition when recv(0, MSG_PEEK) is called with a blocking recv() and the last socket buffer is an MSG_OOB skb. This occurs because the function manage_oob() returns NULL for a 0-length buffer, but the code did not return immediately, leading to the busy-wait. The issue has been fixed in specific Linux kernel commits.
References
- git.kernel.org/stable/c/3d3c7a3df66b2ca3d2cd1a2a0c37eb701feba713 (opens in a new tab)
- git.kernel.org/stable/c/d5dd55b316ca229a4cbf11729483ba5bb57233e7 (opens in a new tab)
- git.kernel.org/stable/c/c81c5be3826c8467945b964d0cf7f7b3d65461db (opens in a new tab)
- git.kernel.org/stable/c/6e5ee08eb5858d175da6768d75d163817b6a9d4a (opens in a new tab)