CVE-2024-56712Microsoft CVSS 3.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Microsoft advisory for CVE-2024-56712

Published
September 3, 2025
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2024-56712 →

📋 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-56712. This page also shows what EchelonGraph holds for CVE-2024-56712, 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 products22

  • azl3 kernel 6.6.104.2-4 on Azure Linux 3.0
  • azl3 kernel 6.6.112.1-2 on Azure Linux 3.0
  • azl3 kernel 6.6.117.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.119.3-1 on Azure Linux 3.0
  • azl3 kernel 6.6.119.3-3 on Azure Linux 3.0
  • azl3 kernel 6.6.121.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.126.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.130.1-3 on Azure Linux 3.0
  • azl3 kernel 6.6.134.1-2 on Azure Linux 3.0
  • azl3 kernel 6.6.137.1-2 on Azure Linux 3.0
  • azl3 kernel 6.6.138.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.139.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.141.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.143.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.144.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.145.2-1 on Azure Linux 3.0
  • azl3 kernel 6.6.150.1-1 on Azure Linux 3.0
  • azl3 kernel 6.6.96.2-1 on Azure Linux 3.0
  • azl3 kernel 6.6.96.2-2 on Azure Linux 3.0
  • cbl2 kernel 5.15.186.1-1 on CBL Mariner 2.0
  • cbl2 kernel 5.15.200.1-1 on CBL Mariner 2.0
  • cbl2 kernel 5.15.202.1-1 on CBL Mariner 2.0

🧭 EchelonGraph on CVE-2024-56712

EchelonGraph score
5.5 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: udmabuf: fix memory leak on last export_udmabuf() error path In export_udmabuf(), if dma_buf_fd() fails because the FD table is full, a dma_buf owning the udmabuf has already been created; but the error handling in udmabuf_create() will tear down the udmabuf without doing anything about the containing dma_buf. This leaves a dma_buf in memory that contains a dangling pointer; though that doesn't seem to lead to anything bad except a memory leak. Fix it by moving the dma_buf_fd() call out of export_udmabuf() so that we can give it different error handling. Note that the shape of this code changed a lot in commit 5e72b2b41a21 ("udmabuf: convert udmabuf driver to use folios"); but the memory leak seems to have existed since the introduction of udmabuf.

Published by kernel.org, the CVE Numbering Authority that assigned CVE-2024-56712, 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 (1)