Microsoft security update for CVE-2024-26583
🔗 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-26583. This page also shows what EchelonGraph holds for CVE-2024-26583, 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 products6
- azl3 hyperv-daemons 6.6.14.1-1 on Azure Linux 3.0
- azl3 hyperv-daemons 6.6.22.1-2 on Azure Linux 3.0
- azl3 kernel 6.6.14.1-4 on Azure Linux 3.0
- azl3 kernel 6.6.22.1-2 on Azure Linux 3.0
- cbl2 kernel 5.15.158.2-1 on CBL Mariner 2.0
- cbl2 kernel 5.15.180.1-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.158.2-1 |
| — | Security Update | 6.6.22.1-2 |
🧭 EchelonGraph on CVE-2024-26583
- EchelonGraph score
- 4.7 MEDIUM
- 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: tls: fix race between async notify and socket close The submitting thread (one which called recvmsg/sendmsg) may exit as soon as the async crypto handler calls complete() so any code past that point risks touching already freed data. Try to avoid the locking and extra flags altogether. Have the main thread hold an extra reference, this way we can depend solely on the atomic ref counter for synchronization. Don't futz with reiniting the completion, either, we are now tightly controlling when completion fires.
Published by kernel.org, the CVE Numbering Authority that assigned CVE-2024-26583, 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).