# CVE-2024-38630: watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger

> A use-after-free bug in the Linux kernel's cpu5wdt watchdog driver allows attackers to potentially execute code or escalate privileges during module removal.

- **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:** 21 Jun 2024
- **Updated:** 11 May 2026
- **Also known as:** AZL-48939, BELL-CVE-2024-38630, DEBIAN-CVE-2024-38630, GHSA-w952-23jq-pvh9, ROOT-OS-DEBIAN-11-CVE-2024-38630, ROOT-OS-DEBIAN-12-CVE-2024-38630, UBUNTU-CVE-2024-38630

## What is CVE-2024-38630?

CVE-2024-38630 is a high-severity use after free vulnerability in Linux kernel, published on 21 Jun 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:

watchdog: cpu5wdt.c: Fix use-after-free bug caused by cpu5wdt_trigger

When the cpu5wdt module is removing, the origin code uses del_timer() to
de-activate the timer. If the timer handler is running, del_timer() could
not stop it and will return directly. If the port region is released by
release_region() and then the timer handler cpu5wdt_trigger() calls outb()
to write into the region that is released, the use-after-free bug will
happen.

Change del_timer() to timer_shutdown_sync() in order that the timer handler
could be finished before the port region is released.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-38630 being exploited?

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

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

## Sources

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

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