Microsoft security update for CVE-2024-56600
🔗 CVE IDs covered (1)
📋 Microsoft's advisory
EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-56600. This page also shows what EchelonGraph holds for CVE-2024-56600, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.
🎯 Affected products5
- azl3 kernel 6.6.64.2-9 on Azure Linux 3.0
- azl3 kernel 6.6.76.1-1 on Azure Linux 3.0
- cbl2 kernel 5.15.173.1-2 on CBL Mariner 2.0
- cbl2 kernel 5.15.173.1-2 on CBL-Mariner 2.0
- cbl2 kernel 5.15.176.3-1 on CBL Mariner 2.0
✅ Updates Microsoft lists: 2 updates
2 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 5.15.176.3-1 |
| — | Security Update | 6.6.76.1-1 |
🧭 EchelonGraph on CVE-2024-56600
- EchelonGraph score
- 7.8 HIGH
- CISA KEV
- Not listed
- Fix status
- A fix is available — apply it.
Description from the CVE record (CVE.org), as published by its numbering authority
In the Linux kernel, the following vulnerability has been resolved: net: inet6: do not leave a dangling sk pointer in inet6_create() sock_init_data() attaches the allocated sk pointer to the provided sock object. If inet6_create() fails later, the sk object is released, but the sock object retains the dangling sk pointer, which may cause use-after-free later. Clear the sock sk pointer on error.
Published by kernel.org, the CVE Numbering Authority that assigned CVE-2024-56600, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).