All reports
Medium

kernel: hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2024-53103

Probability of exploitation in the next 30 days: 0.24%

FIRST EPSS · 2026-11-19

Description

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.

A flaw was found in the Linux kernel's Hyper-V socket (hv_sock) driver. When a socket connection is released, the transport pointer is not properly cleared, creating a dangling pointer that references already released memory. A local attacker could exploit this issue to trigger memory corruption, leading to a system crash and Denial of Service (DoS).