Microsoft security update for CVE-2024-50036
🔗 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-50036. This page also shows what EchelonGraph holds for CVE-2024-50036, 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.56.1-5 on Azure Linux 3.0
- azl3 kernel 6.6.57.1-1 on Azure Linux 3.0
- cbl2 kernel 5.15.176.3-1 on CBL Mariner 2.0
- cbl2 kernel 5.15.180.1-1 on CBL Mariner 2.0
- cbl2 kernel 5.15.180.1-1 on CBL-Mariner 2.0
✅ Updates Microsoft lists: 3 updates
3 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.57.1-1 |
| — | Security Update | — |
🧭 EchelonGraph on CVE-2024-50036
- EchelonGraph score
- 7.0 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: do not delay dst_entries_add() in dst_release() dst_entries_add() uses per-cpu data that might be freed at netns dismantle from ip6_route_net_exit() calling dst_entries_destroy() Before ip6_route_net_exit() can be called, we release all the dsts associated with this netns, via calls to dst_release(), which waits an rcu grace period before calling dst_destroy() dst_entries_add() use in dst_destroy() is racy, because dst_entries_destroy() could have been called already. Decrementing the number of dsts must happen sooner. Notes: 1) in CONFIG_XFRM case, dst_destroy() can call dst_release_immediate(child), this might also cause UAF if the child does not have DST_NOCOUNT set. IPSEC maintainers might take a look and see how to address this. 2) There is also discussion about removing this count of dst, which might happen in future kernels.
Published by kernel.org, the CVE Numbering Authority that assigned CVE-2024-50036, 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).