# CVE-2024-41008: drm/amdgpu: change vm->task_info handling

> A use-after-free vulnerability in the Linux kernel's amdgpu driver allows attackers to execute arbitrary code or escalate privileges.

- **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:** 16 Jul 2024
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-62848, AZL-68255, BELL-CVE-2024-41008, DEBIAN-CVE-2024-41008, GHSA-x67r-7mr9-vwm2, ROOT-OS-DEBIAN-11-CVE-2024-41008, ROOT-OS-DEBIAN-12-CVE-2024-41008, ROOT-OS-UBUNTU-2204-CVE-2024-41008, ROOT-OS-UBUNTU-2404-CVE-2024-41008, UBUNTU-CVE-2024-41008

## What is CVE-2024-41008?

CVE-2024-41008 is a high-severity use after free vulnerability in Linux kernel, published on 16 Jul 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: change vm->task_info handling

This patch changes the handling and lifecycle of vm->task_info object.
The major changes are:
- vm->task_info is a dynamically allocated ptr now, and its uasge is
  reference counted.
- introducing two new helper funcs for task_info lifecycle management
    - amdgpu_vm_get_task_info: reference counts up task_info before
      returning this info
    - amdgpu_vm_put_task_info: reference counts down task_info
- last put to task_info() frees task_info from the vm.

This patch also does logistical changes required for existing usage
of vm->task_info.

V2: Do not block all the prints when task_info not found (Felix)

V3: Fixed review comments from Felix
   - Fix wrong indentation
   - No debug message for -ENOMEM
   - Add NULL check for task_info
   - Do not duplicate the debug messages (ti vs no ti)
   - Get first reference of task_info in vm_init(), put last
     in vm_fini()

V4: Fixed review comments from Felix
   - fix double reference increment in create_task_info
   - change amdgpu_vm_get_task_info_pasid
   - additional changes in amdgpu_gem.c while porting

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-41008 being exploited?

There is no known exploitation of CVE-2024-41008 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-41008 and fix it if it is affected.

What it is: CVE-2024-41008 is a high-severity use after free vulnerability in Linux kernel, published on 16 Jul 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-41008 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-41008/ (Markdown: https://insights.sbomify.com/CVE-2024-41008/index.md)
```

## Sources

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

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