CVE-2024-25178HighMicrosoft CVSS 9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Microsoft security update for CVE-2024-25178

Published
July 19, 2025
Last Modified
—

🔗 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-25178. This page also shows what EchelonGraph holds for CVE-2024-25178, 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 sysbench 1.0.20-5 on Azure Linux 3.0
  • azl3 sysbench 1.0.20-6 on Azure Linux 3.0
  • cbl2 luajit 2.1.0-26 on CBL Mariner 2.0
  • cbl2 sysbench 1.0.20-2 on CBL Mariner 2.0
  • cm2 luajit 2.1.0-27 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 articleUpdateFixed build
—Security Update1.0.20-6
—Security Update1.0.20-3
—Security Update2.1.0-27

🧭 EchelonGraph on CVE-2024-25178

EchelonGraph score
9.1 CRITICAL
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

LuaJIT through 2.1 and OpenRusty luajit2 before v2.1-20240314 have an out-of-bounds read in the stack-overflow handler in lj_state.c.

Published by MITRE Corporation, the CVE Numbering Authority that assigned CVE-2024-25178, 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).

🔗 References (2)