CVE-2024-53103·Kernel vulnerability
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.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.11.8
- Published
- 2024-12-02
Affected versions
From: 6.7
Until: 6.11.8
Fixed in: 6.11.8
How to fix this CVE
Update your Linux kernel to version 6.11.8 or later to resolve a memory safety issue in the Hyper-V socket (hv_sock) subsystem. The vulnerability stems from improper pointer initialization during resource cleanup, which could potentially lead to use-after-free conditions. Apply the patch immediately on systems running kernel versions 6.7 through 6.11.7 that rely on Hyper-V socket functionality.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check current kernel version with 'uname -r' and compare against affected range 6.7-6.11.7
- Step 2: Verify hv_sock module is loaded with 'lsmod | grep hv_sock' (presence indicates exposure on Hyper-V guests)
- Step 3: Search kernel logs for hv_sock-related crashes or NULL pointer exceptions: 'sudo journalctl -xe | grep -i hv_sock'
- Step 4: After patching, confirm kernel version is 6.11.8+ with 'uname -r' and reboot if necessary
FAQ
What is CVE-2024-53103?
CVE-2024-53103 is a memory safety vulnerability in the Linux kernel's Hyper-V socket implementation where the vsk->trans pointer may remain uninitialized during resource release, creating a dangling pointer condition that could cause system crashes or unexpected behavior.
Is CVE-2024-53103 being actively exploited?
No, there is no evidence of active exploitation. This vulnerability has not been added to the CISA Known Exploited Vulnerabilities catalog, and no public exploits are currently available.
What versions of Kernel are affected by CVE-2024-53103?
Linux kernel versions 6.7 through 6.11.7 are vulnerable. The fix is included in kernel 6.11.8 and later stable releases.
How do I check if my server is vulnerable to CVE-2024-53103?
Run 'uname -r' to check your kernel version. If it reports a version between 6.7 and 6.11.7 inclusive, and your system uses Hyper-V sockets (check with 'lsmod | grep hv_sock'), your system is vulnerable.
Does Defensia detect CVE-2024-53103?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2024-53103 will appear in your dashboard with remediation steps.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/285266ef92f7b4bf7d26e1e95e215ce6a6badb4a
- https://git.kernel.org/stable/c/414476c4fb11be070c09ab8f3e75c9ee324a108a
- https://git.kernel.org/stable/c/4bdc5a62c6e50600d8a1c3e18fd6dce0c27c9497
- https://git.kernel.org/stable/c/4fe1d42f2acc463b733bb42e3f8e67dbc2a0eb2d
- https://git.kernel.org/stable/c/7cf25987820350cb950856c71b409e5b6eed52bd
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-53103. Free for 1 server.
Get started free