# CVE-2024-42230: powerpc/pseries: Fix scv instruction crash with kexec

> A flaw in the Linux kernel's kexec sequence on pseries platforms allows a local attacker to crash the system by triggering an unexpected interrupt.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2024
- **Updated:** 11 May 2026
- **Also known as:** AZL-47232, BELL-CVE-2024-42230, DEBIAN-CVE-2024-42230, GHSA-qf7q-7m3q-4gg2, ROOT-OS-DEBIAN-11-CVE-2024-42230, UBUNTU-CVE-2024-42230

## What is CVE-2024-42230?

CVE-2024-42230 is a medium-severity denial of service vulnerability in Linux kernel, published on 30 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:

powerpc/pseries: Fix scv instruction crash with kexec

kexec on pseries disables AIL (reloc_on_exc), required for scv
instruction support, before other CPUs have been shut down. This means
they can execute scv instructions after AIL is disabled, which causes an
interrupt at an unexpected entry location that crashes the kernel.

Change the kexec sequence to disable AIL after other CPUs have been
brought down.

As a refresher, the real-mode scv interrupt vector is 0x17000, and the
fixed-location head code probably couldn't easily deal with implementing
such high addresses so it was just decided not to support that interrupt
at all.

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

It affects 1 product.


Products: Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2024-42230 being exploited?

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

What it is: CVE-2024-42230 is a medium-severity denial of service vulnerability in Linux kernel, published on 30 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-42230 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-42230/ (Markdown: https://insights.sbomify.com/CVE-2024-42230/index.md)
```

## Sources

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

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