CVE-2026-31542: Linux kernel · x86/platform/uv: Handle deconfigured sockets
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c51957601d32c0d195bce0b9345dfe93ef5728cc : update Linux kernel when convenient.
Data as of 5 Nov 2026, 22:06 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-05.
- Patch
- Available – fixed in c51957601d32c0d195bce0b9345dfe93ef5728cc, c1cf2218d2fa40a49921a7460981e5faab26f04e, 9956d4892e78812246336c7ea51f5aa62018049e +2
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 5 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
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
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
The vulnerability has been fixed in the Linux kernel. Users should update to the fixed kernel versions identified by the commits c51957601d32c0d195bce0b9345dfe93ef5728cc, c1cf2218d2fa40a49921a7460981e5faab26f04e, 9956d4892e78812246336c7ea51f5aa62018049e, 79f0faf81d3bbbe5f07bf6892450d3740a1b290d, and 1f6aa5bbf1d0f81a8a2aafc16136e7dd9a609ff3. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's x86 platform UV code caused a kernel panic when sockets were deconfigured and mapped to SOCK_EMPTY (0xffff). This issue occurred during allocation of UV hub info structures. The flaw has been fixed by changing the allocation to use NUMA_NO_NODE, ensuring allocations occur on valid nodes.
References
- git.kernel.org/stable/c/c51957601d32c0d195bce0b9345dfe93ef5728cc (opens in a new tab)
- git.kernel.org/stable/c/9956d4892e78812246336c7ea51f5aa62018049e (opens in a new tab)
- git.kernel.org/stable/c/79f0faf81d3bbbe5f07bf6892450d3740a1b290d (opens in a new tab)
- git.kernel.org/stable/c/c1cf2218d2fa40a49921a7460981e5faab26f04e (opens in a new tab)
- git.kernel.org/stable/c/1f6aa5bbf1d0f81a8a2aafc16136e7dd9a609ff3 (opens in a new tab)