CVE-2024-53103Published Dec 2, 2024 · Dec 2Updated Oct 28
hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer
Linux
High7.8Fix available
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ae0078fcf0a5eb3a8623bfb5f988262e0911fdb9 · < 4bdc5a62c6e50600d8a1c3e18fd6dce0c27c9497| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer
When hvs is released, there is a possibility that vsk->trans may not be initialized to NULL, which could lead to a dangling pointer. This issue is resolved by initializing vsk->trans to NULL.
From the CVE record · Linux
The Linux kernel’s hv_sock component may leave vsk->trans as a dangling pointer when hvs is released. The input does not specify what an attacker could do with this condition or whether exploitation requires network access, authentication, or user interaction.
Engineers running the Linux kernel should check their installations; affected versions are not specified.