# CVE-2024-2201: CVE-2024-2201

> Attackers can bypass Spectre v2 mitigations to leak arbitrary Linux kernel memory on Intel systems, requiring kernel patches.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 19 Dec 2024
- **Updated:** 9 Jan 2025
- **Also known as:** ALPINE-CVE-2024-2201, CLSA-2025-1756482270, DEBIAN-CVE-2024-2201, GHSA-j32h-9rm6-p2c5, ROOT-OS-DEBIAN-11-CVE-2024-2201, UBUNTU-CVE-2024-2201, openSUSE-SU-2024:13858-1

## What is CVE-2024-2201?

CVE-2024-2201 is a medium-severity vulnerability in Xen, published on 19 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A cross-privilege Spectre v2 vulnerability allows attackers to bypass all deployed mitigations, including the recent Fine(IBT), and to leak arbitrary Linux kernel memory on Intel systems.

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel-source` | openSUSE:Tumbleweed | All versions | 6.8.5-1.1 |

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

Apply the vendor's patch.

## Is CVE-2024-2201 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2201 is a medium-severity vulnerability in Xen, published on 19 Dec 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-2201 in the wild and no public exploit code.

Affected product: Xen. 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-2201/ (Markdown: https://insights.sbomify.com/CVE-2024-2201/index.md)
```

## Sources

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

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