Microsoft security update for CVE-2024-38583
🔗 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-38583. This page also shows what EchelonGraph holds for CVE-2024-38583, 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.22.1-2 on Azure Linux 3.0
- azl3 kernel 6.6.35.1-5 on Azure Linux 3.0
- cbl2 kernel 5.15.160.1-1 on CBL Mariner 2.0
- cbl2 kernel 5.15.160.1-1 on CBL-Mariner 2.0
- cbl2 kernel 5.15.161.1-1 on CBL Mariner 2.0
✅ Updates Microsoft lists: 4 updates
4 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.161.1-1 |
| — | Security Update | - |
| — | Security Update | 5.15.162.2-1 |
| — | Security Update | 6.6.35.1-5 |
🧭 EchelonGraph on CVE-2024-38583
- 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: nilfs2: fix use-after-free of timer for log writer thread Patch series "nilfs2: fix log writer related issues". This bug fix series covers three nilfs2 log writer-related issues, including a timer use-after-free issue and potential deadlock issue on unmount, and a potential freeze issue in event synchronization found during their analysis. Details are described in each commit log. This patch (of 3): A use-after-free issue has been reported regarding the timer sc_timer on the nilfs_sc_info structure. The problem is that even though it is used to wake up a sleeping log writer thread, sc_timer is not shut down until the nilfs_sc_info structure is about to be freed, and is used regardless of the thread's lifetime. Fix this issue by limiting the use of sc_timer only while the log writer thread is alive.
Published by kernel.org, the CVE Numbering Authority that assigned CVE-2024-38583, 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).