CVE-2024-53241

x86/xen: don't do PV iret hypercall through hypercall page

MEDIUM

5.5

CVSS Score

Published: December 24, 2024 at 09:24 AM UTC

Updated: June 17, 2026 at 08:08 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.3%

Description

In the Linux kernel, the following vulnerability has been resolved: x86/xen: don't do PV iret hypercall through hypercall page Instead of jumping to the Xen hypercall page for doing the iret hypercall, directly code the required sequence in xen-asm.S. This is done in preparation of no longer using hypercall page at all, as it has shown to cause problems with speculation mitigations. This is part of XSA-466 / CVE-2024-53241.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

v < 5.10.2322.6.27 ≤ v < 5.10.2322.6.27 ≤ v < 5.15.1752.6.27 ≤ v < 6.1.1212.6.27 ≤ v < 6.12.62.6.27 ≤ v < 6.132.6.27 ≤ v < 6.6.675.11 ≤ v < 5.15.1755.16 ≤ v < 6.1.1216.2 ≤ v < 6.6.676.7 ≤ v < 6.12.62.6.27 6.13 rc1 6.13 rc2 6.13 rc3cdacc1278b12d929f9a053c245ff3d16eb7af9f8

Vendor states this is fixed in 05df6e6cd9a76b778aee33c3c18c9f3b3566d4a5 (fixed)

Vendor states this is fixed in 82c211ead1ec440dbf81727e17b03b5e3c44b93d (fixed)

Vendor states this is fixed in a2796dff62d6c6bfc5fbebdf2bee0d5ac0438906 (fixed)

Vendor states this is fixed in c7b4cfa6213a44fa48714186dfdf125072d036e3 (fixed)

Vendor states this is fixed in f7c3fdad0a474062d566aae3289d490d7e702d30 (fixed)

Vendor states this is fixed in fa719857f613fed94a79da055b13ca51214c694f (fixed)

Vendor states this is fixed in 2.6.27 (unaffected)

Vendor states this is fixed in 5.10.232 (unaffected)

Vendor states this is fixed in 5.15.175 (unaffected)

Vendor states this is fixed in 6.1.121 (unaffected)

Vendor states this is fixed in 6.12.6 (unaffected)

Vendor states this is fixed in 6.13 (unaffected)