# CVE-2024-35817: drm/amdgpu: amdgpu_ttm_gart_bind set gtt bound flag

> A missing flag in the AMD GPU driver allows the GPU to read stale system memory, potentially disclosing sensitive data.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 May 2024
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2024-35817, DEBIAN-CVE-2024-35817, GHSA-r5rh-f6h6-v872, ROOT-OS-DEBIAN-11-CVE-2024-35817, SUSE-SU-2024:3321-1, UBUNTU-CVE-2024-35817

## What is CVE-2024-35817?

CVE-2024-35817 is a high-severity vulnerability in Linux kernel, published on 17 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

drm/amdgpu: amdgpu_ttm_gart_bind set gtt bound flag

Otherwise after the GTT bo is released, the GTT and gart space is freed
but amdgpu_ttm_backend_unbind will not clear the gart page table entry
and leave valid mapping entry pointing to the stale system page. Then
if GPU access the gart address mistakely, it will read undefined value
instead page fault, harder to debug and reproduce the real issue.

## Which versions are affected by CVE-2024-35817?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel-livepatch-SLE15-SP6-RT_Update_0` | SUSE:Linux Enterprise Live Patching 15 SP6 | All versions | 3-150600.3.2 |

Products: Linux kernel.

## How do I fix CVE-2024-35817?

Apply the vendor's patch.

## Is CVE-2024-35817 being exploited?

There is no known exploitation of CVE-2024-35817 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-35817 and fix it if it is affected.

What it is: CVE-2024-35817 is a high-severity vulnerability in Linux kernel, published on 17 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-35817 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-35817/ (Markdown: https://insights.sbomify.com/CVE-2024-35817/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-35817
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-35817
- OSV: https://osv.dev/vulnerability/CVE-2024-35817

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-35817/
Summaries are generated and may contain mistakes; the official description above is the record.