x86/platform/uv: Handle deconfigured sockets
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
x86/platform/uv: Handle deconfigured sockets
When a socket is deconfigured, it's mapped to SOCK_EMPTY (0xffff). This causes a panic while allocating UV hub info structures.
Fix this by using NUMA_NO_NODE, allowing UV hub info structures to be allocated on valid nodes.
From the CVE record · Linux
The Linux kernel can panic while allocating UV hub information structures when a socket is deconfigured and mapped to SOCK_EMPTY. The input does not describe an attacker action or specify network access, authentication, or user interaction requirements.
Engineers running the Linux kernel on systems using x86/platform/uv should check their deployments; affected versions are not specified.