CVE-2024-53103
hv_sock: Initializing vsk->trans to NULL to prevent a dangling pointer
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
4.14
References 9
git.kernel.org
- stable/c/285266ef92f7b4bf7d26e1e95e215ce6a6badb4a
- stable/c/4fe1d42f2acc463b733bb42e3f8e67dbc2a0eb2d
- stable/c/414476c4fb11be070c09ab8f3e75c9ee324a108a
- stable/c/7cf25987820350cb950856c71b409e5b6eed52bd
- stable/c/98d8dde9232250a57ad5ef16479bf6a349e09b80
- stable/c/4bdc5a62c6e50600d8a1c3e18fd6dce0c27c9497
- stable/c/e0fe3392371293175f25028020ded5267f4cd8e3
- stable/c/8621725afb38e111969c64280b71480afde2aace
- stable/c/e629295bd60abf4da1db85b82819ca6a4f6c1e79