CVE-2024-27400: drm/amdgpu: once more fix the call oder in amdgpu_ttm_move() v2

Published May 13, 2024
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: once more fix the call oder in amdgputtmmove() v2

This reverts drm/amdgpu: fix ftrace event amdgpubomove always move on same heap. The basic problem here is that after the move the old location is simply not available any more.

Some fixes were suggested, but essentially we should call the move notification before actually moving things because only this way we have the correct order for DMA-buf and VM move notifications as well.

Also rework the statistic handling so that we don't update the eviction counter before the move.

v2: add missing NULL check

Affected Software

14 affected componentsFixes available
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1
Linux Linux kernel>=5.15.149<5.16
Linux Linux kernel>=6.1.77<6.1.91
Linux Linux kernel>=6.6.16<6.6.31
Linux Linux kernel>=6.7.4<6.8.10
Linux Linux kernel=6.9-rc1
Linux Linux kernel=6.9-rc2
Linux Linux kernel=6.9-rc3
Linux Linux kernel=6.9-rc4
Linux Linux kernel=6.9-rc5
Linux Linux kernel=6.9-rc6
Fedoraproject Fedora=39
Fedoraproject Fedora=40
Microsoft cbl2 kernel 5.15.186.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  2. Configuration

    Rework amdgpu_ttm_move() so that eviction statistics/counters are not updated before the move, and move/notification ordering is performed before the actual relocation to ensure correct DMA-buf and VM move notification order.

    Linux kernel drm/amdgpu amdgpu_ttm_move() call order = Call the move notification before actually moving the TTM buffer/model; do not update the eviction counter before the move
  3. Compensating control

    If you cannot immediately update, ensure your kernel build does not include the faulty call order behavior where eviction counters are updated before the move and notifications occur after relocation (this restores the required ordering for DMA-buf/VM move notifications).

Event History

May 13, 2024
CVE Published
via MITRE·10:26 AM
Data Sourced
via MITRE·10:26 AM
DescriptionSeverity
May 14, 2024
Data Sourced
via NVD·03:12 PM
Description
Data Sourced
via NVD·03:12 PM
RemedySeverityAffected Software
Aug 8, 2024
Data Sourced
via Launchpad·11:25 PM
Description
May 1, 2025
Data Sourced
via Ubuntu·12:19 AM
RemedyDescriptionSeverityAffected Software
Dec 25, 2025
Data Sourced
via Microsoft·01:01 AM
DescriptionSeverityWeaknessAffected Software
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-27400?

The severity of CVE-2024-27400 is classified as medium, indicating a moderate potential for impact.

2

How do I fix CVE-2024-27400?

To fix CVE-2024-27400, update the linux package to the recommended versions: 5.10.223-1, 5.10.226-1, 6.1.123-1, 6.1.119-1, 6.12.10-1, or 6.12.11-1.

3

Which Linux kernel versions are affected by CVE-2024-27400?

CVE-2024-27400 affects multiple Linux kernel versions including 5.10.x and 6.1.x.

4

Is CVE-2024-27400 a critical vulnerability?

CVE-2024-27400 is not considered a critical vulnerability but should still be addressed to maintain system security.

5

What software packages are impacted by CVE-2024-27400?

The linux package on Debian systems is impacted by CVE-2024-27400.

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