CVE-2024-53122MediumMicrosoft CVSS 5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Microsoft security update for CVE-2024-53122

Published
January 29, 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-53122. This page also shows what EchelonGraph holds for CVE-2024-53122, 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.57.1-7 on Azure Linux 3.0
  • azl3 kernel 6.6.64.2-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 articleUpdateFixed build
—Security Update5.15.176.3-1
—Security Update6.6.64.2-1
—Security Update—

🧭 EchelonGraph on CVE-2024-53122

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: mptcp: cope racing subflow creation in mptcp_rcv_space_adjust Additional active subflows - i.e. created by the in kernel path manager - are included into the subflow list before starting the 3whs. A racing recvmsg() spooling data received on an already established subflow would unconditionally call tcp_cleanup_rbuf() on all the current subflows, potentially hitting a divide by zero error on the newly created ones. Explicitly check that the subflow is in a suitable state before invoking tcp_cleanup_rbuf().

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