CVE-2024-36357: Xen Security Advisory 471 v1 (CVE-2024-36350,CVE-2024-36357) - x86: Transitive Scheduler Attacks

Published Mar 7, 2025
·
Updated

A transient execution vulnerability in some AMD processors may allow an attacker to infer data in the L1D cache, potentially resulting in the leakage of sensitive information across privileged boundaries.

Other sources

AMD: CVE-2024-36357 Transient Scheduler Attack in L1 Data Queue

Microsoft

The vulnerability assigned to this CVE is in certain processor models offered by AMD. The mitigation for this vulnerability requires a Windows update. This CVE is being documented in the Security Update Guide to announce that the latest builds of Windows enable the mitigation and provide protection against the vulnerability. Please see the following for more information:

AMD-SB-7029

Microsoft

Affected Software

29 affected componentsFixes available
XEN Xen
Microsoft Windows Server 2025
Microsoft Windows 10=22H2
Microsoft Windows Server 2022, 23H2 Edition
Microsoft Windows 11=23H2
Microsoft Windows 10=22H2
Microsoft Windows Server 2016
Microsoft Windows Server 2016
Microsoft Windows 11=22H2
Microsoft Windows 10=21H2
Microsoft Windows 10=1607
Microsoft Windows 10=21H2
Microsoft Windows 11=24H2
Microsoft Windows Server 2022
Microsoft Windows Server 2025
Microsoft Windows Server 2022
Microsoft Windows 10=1607
Microsoft Windows Server 2019
Microsoft Windows 10=1809
Microsoft Windows Server 2019
Microsoft Windows 10=1809
debian/amd64-microcode<=3.20240820.1~deb11u1, <=3.20250311.1~deb11u1, <=3.20250311.1~deb12u1, <=3.20230719.1~deb12u1, <=3.20250311.1
3.20251202.1
debian/linux<=5.10.223-1
5.10.257-16.1.170-36.1.174-16.12.86-16.12.94-17.0.13-1
debian/linux-6.1
6.1.174-1~deb11u1
debian/xen<=4.14.6-1, <=4.14.5+94-ge49571868d-1
4.17.5+72-g01140da4e8-14.20.2+37-g61ff35323e-0+deb13u14.20.2+7-g1badcf5035-0+deb13u14.20.2+37-g61ff35323e-1
IBM Verify Identity Access<=11.0 - 11.0.2
IBM Security Verify Access<=10.0 - 10.0.9.1
IBM Verify Identity Access Container<=11.0 - 11.0.2
IBM Security Verify Access Container<=10.0 - 10.0.9.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/amd64-microcode to a version that resolves this vulnerability.

    Fixed in 3.20251202.1
  2. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.257-1Fixed in 6.1.170-3Fixed in 6.1.174-1Fixed in 6.12.86-1Fixed in 6.12.94-1Fixed in 7.0.13-1
  3. Upgrade

    Upgrade debian/linux-6.1 to a version that resolves this vulnerability.

    Fixed in 6.1.174-1~deb11u1
  4. Upgrade

    Upgrade debian/xen to a version that resolves this vulnerability.

    Fixed in 4.17.5+72-g01140da4e8-1Fixed in 4.20.2+37-g61ff35323e-0+deb13u1Fixed in 4.20.2+7-g1badcf5035-0+deb13u1Fixed in 4.20.2+37-g61ff35323e-1
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch AMD-SB-7029
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch Xen Security Advisory 471 v1
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch Xen Security Advisory 471 v2
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch Xen Security Advisory 471 v3

Event History

Mar 7, 2025
Data Sourced
via Red Hat·08:52 PM
DescriptionSeverityAffected Software
Jul 8, 2025
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
CVE Published
via MITRE·05:01 PM
Data Sourced
via MITRE·05:01 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
DescriptionSeverity
Jun 26, 2026
Data Sourced
via Ubuntu·06:26 PM
RemedyDescriptionSeverityAffected Software
Jun 28, 2026
Data Sourced
via Debian·06:29 PM
DescriptionAffected Software
Jul 8, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-36357?

CVE-2024-36357 is categorized as a high-severity vulnerability due to the potential leakage of sensitive information.

2

How do I fix CVE-2024-36357?

To mitigate CVE-2024-36357, it is recommended to apply firmware updates provided by the manufacturer for affected AMD processors.

3

What type of vulnerability is CVE-2024-36357?

CVE-2024-36357 is a transient execution vulnerability that may allow attackers to infer data from the L1D cache.

4

Which processors are affected by CVE-2024-36357?

CVE-2024-36357 affects certain AMD processors that are susceptible to transient execution attacks.

5

What could be the consequence of exploiting CVE-2024-36357?

Exploiting CVE-2024-36357 could allow an attacker to leak sensitive information across privileged boundaries, posing a significant security risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203