# CVE-2024-38667: riscv: prevent pt_regs corruption for secondary idle threads

> A memory corruption flaw in the Linux kernel RISC-V architecture allows stack overlap, potentially leading to system crashes or arbitrary code execution.

- **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:** 24 Jun 2024
- **Updated:** 11 May 2026
- **Also known as:** AZL-42901, BELL-CVE-2024-38667, DEBIAN-CVE-2024-38667, GHSA-cqg5-mcpx-q78p, ROOT-OS-DEBIAN-11-CVE-2024-38667, UBUNTU-CVE-2024-38667

## What is CVE-2024-38667?

CVE-2024-38667 is a high-severity memory corruption vulnerability in Linux kernel, published on 24 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:

riscv: prevent pt_regs corruption for secondary idle threads

Top of the kernel thread stack should be reserved for pt_regs. However
this is not the case for the idle threads of the secondary boot harts.
Their stacks overlap with their pt_regs, so both may get corrupted.

Similar issue has been fixed for the primary hart, see c7cdd96eca28
("riscv: prevent stack corruption by reserving task_pt_regs(p) early").
However that fix was not propagated to the secondary harts. The problem
has been noticed in some CPU hotplug tests with V enabled. The function
smp_callin stored several registers on stack, corrupting top of pt_regs
structure including status field. As a result, kernel attempted to save
or restore inexistent V context.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-38667 being exploited?

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

What it is: CVE-2024-38667 is a high-severity memory corruption vulnerability in Linux kernel, published on 24 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-38667 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-38667/ (Markdown: https://insights.sbomify.com/CVE-2024-38667/index.md)
```

## Sources

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

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