VDB

CVE-2025-68259

CVE-2025-68259 PUBLISHED

KVM: SVM: Don't skip unrelated instruction if INT3/INTO is replaced

Reported by linux · Published December 16, 2025

In the Linux kernel, the following vulnerability has been resolved: KVM: SVM: Don't skip unrelated instruction if INT3/INTO is replaced When re-injecting a soft interrupt from an INT3, INT0, or (select) INTn instruction, discard the exception and retry the instruction if the code stream is changed (e.g. by a different vCPU) between when the CPU executes the instruction and when KVM decodes the instruction to get the next RIP. As effectively predicted by commit 6ef88d6e36c2 ("KVM: SVM: Re-inject INT3/INTO instead of retrying the instruction"), failure to verify that the correct INTn instruction was decoded can effectively clobber guest state due to decoding the wrong instruction and thus specifying the wrong next RIP. The bug most often manifests as "Oops: int3" panics on static branch checks in Linux guests. Enabling or disabling a static branch in Linux uses the kernel's "text poke" code patching mechanism. To modify code while other CPUs may be executing that code, Linux (temporarily) replaces the first byte of the original instruction with an int3 (opcode 0xcc), then patches in the new code stream except for the first byte, and finally replaces the int3 with the first byte of the new code stream. If a CPU hits the int3, i.e. executes the code while it's being modified, then the guest kernel must look up the RIP to determine how to handle the #BP, e.g. by emulating the new instruction. If the RIP is incorrect, then this lookup fails and the guest kernel panics. The bug reproduces almost instantly by hacking the guest kernel to repeatedly check a static branch[1] while running a drgn script[2] on the host to constantly swap out the memory containing the guest's TSS. [1]: https://gist.github.com/osandov/44d17c51c28c0ac998ea0334edf90b5a [2]: https://gist.github.com/osandov/10e45e45afa29b11e0c7209247afc00b

EPSS 0.21% · 10.5th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
kernel6.12-libbpf-staticAmazon Linux1:6.12.63-84.121.amzn2023
kernel6.12Amazon Linux1:6.12.63-84.121.amzn2023
kernel-livepatch-6.1.161-183.298Amazon Linux1:1.0-0.amzn2023
kernel-develAmazon Linux1:6.1.161-183.298.amzn2023
kernel-libbpf-develAmazon Linux1:6.1.161-183.298.amzn2023
kernel-tools-develAmazon Linux1:6.1.161-183.298.amzn2023
kernel6.12-modules-extraAmazon Linux1:6.12.63-84.121.amzn2023
python3-perfAmazon Linux1:6.1.161-183.298.amzn2023
python3-perf6.12Amazon Linux1:6.12.63-84.121.amzn2023
kernel6.12-toolsAmazon Linux1:6.12.63-84.121.amzn2023
kernel6.12-headersAmazon Linux1:6.12.63-84.121.amzn2023
kernel-libbpfAmazon Linux1:6.1.161-183.298.amzn2023

10 more packages have a fixed version. See every fix in Lookup.

Risk scores

EPSS Score
0.21%
10.5th percentile

Affected products

VendorProductVersions
LinuxLinux6ef88d6e36c2b4b3886ec9967cafabe4424d27d5, 6ef88d6e36c2b4b3886ec9967cafabe4424d27d5, 6ef88d6e36c2b4b3886ec9967cafabe4424d27d5
LinuxLinux6.0, 0, 6.1.160
amazon:2023kernel6.12-libbpf-static0
amazon:2023kernel6.120
amazon:2023kernel-livepatch-6.1.161-183.2980
amazon:2023kernel-devel0
amazon:2023kernel-libbpf-devel0
amazon:2023kernel-tools-devel0
amazon:2023kernel6.12-modules-extra0
amazon:2023python3-perf0
amazon:2023python3-perf6.120
amazon:2023kernel6.12-tools0
amazon:2023kernel6.12-headers0
amazon:2023kernel-libbpf0
amazon:2023kernel-livepatch-6.12.63-84.1210
amazon:2023kernel6.12-libbpf0
amazon:2023bpftool6.120
amazon:2023perf6.120
amazon:2023kernel-headers0
amazon:2023kernel-modules-extra-common0

…and 12 more

Timeline

  • Dec 16, 2025 CVE Published
  • Dec 17, 2025 EPSS Score (30 in total, the first dated here)
  • Mar 26, 2026 Coalition ESS Score (2 in total, the first dated here)
  • Mar 29, 2026 Distribution Patch (181 in total, the first dated here)
  • Mar 29, 2026 Security Advisory (188 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-68259
vulnetix vdb fixes CVE-2025-68259

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-68259/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›