Incorrect buffer tracking via misordered move notifications
Published May 13, 2024 · Updated Aug 5, 2026
Incorrect state handling in affected Linux kernel releases allows local users to disrupt AMDGPU buffer-move tracking. In amdgpu_ttm_move(), notification occurs after the buffer move, when the old location is unavailable, misordering DMA-buf and virtual-memory notifications and updating eviction statistics too early. Exploitation requires low-privilege local access and an AMDGPU path that moves a buffer object; the exact security consequence is not publicly documented.
Summary
What happened
Incorrect state handling in affected Linux kernel releases allows local users to disrupt AMDGPU buffer-move tracking. In amdgpu_ttm_move(), notification occurs after the buffer move, when the old location is unavailable, misordering DMA-buf and virtual-memory notifications and updating eviction statistics too early. Exploitation requires low-privilege local access and an AMDGPU path that moves a buffer object; the exact security consequence is not publicly documented.
The record
- CVE
- CVE-2024-27400
- Published
- May 13, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1cd2b612474c07b17a21e27f2eed8dff75cb5057
- Affected versionversion=5.15.149 <5.16
- Affected versionversion=6.1.77 <6.1.91
- Affected versionversion=6.6.16 <6.6.31
- Affected versionversion=6.7.4 <6.8
- Affected versionversion=6.8
- Affected versionversion=77bcd4ab446fa35ad135b1c7404415ed9a129296
- Affected versionversion=94aeb4117343d072e3a35b9595bcbfc0058ee724 <9a4f6e138720b6e9adf7b82a71d0292f3f276480
- Affected versionversion=94aeb4117343d072e3a35b9595bcbfc0058ee724 <d3a9331a6591e9df64791e076f6591f440af51c3
- Affected versionversion=d443fb67ca5ab04760449d21ddea66f6728e5b00 <5c25b169f9a0b34ee410891a96bc9d7b9ed6f9be
- Affected versionversion=e7a0ee45c653784edda5e36bae6ae3c75fd5e7a8 <0c7ed3ed35eec9138b88d42217b5a6b9a62bda4d
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo