Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68259: KVM: SVM: Don't skip unrelated instruction if INT3/INTO is replaced

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
  • Fixed version: Linux Linux 152289a51107ef45bbfe9b4aeeaa584a503042b5, 2e84a018c2895c05abe213eb10db128aa45f6ec6, 4da3768e1820cf15cced390242d8789aed34f54d.

Low priority for now. Upgrade to Linux Linux 152289a51107ef45bbfe9b4aeeaa584a503042b5, 2e84a018c2895c05abe213eb10db128aa45f6ec6, 4da3768e1820cf15cced390242d8789aed34f54d or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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

—No exploit Fix available
Published
Dec 16, 2025
Updated
Oct 14, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-68259

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 6.0affected
    • 6ef88d6e36c2b4b3886ec9967cafabe4424d27d5 and later · before 2e84a018c2895c05abe213eb10db128aa45f6ec6affected · git
    • 6ef88d6e36c2b4b3886ec9967cafabe4424d27d5 and later · before 152289a51107ef45bbfe9b4aeeaa584a503042b5affected · git
    • 6ef88d6e36c2b4b3886ec9967cafabe4424d27d5 and later · before 87cc1622c88a4888959d64fa1fc9ba1e264aa3d4affected · git
    • 6ef88d6e36c2b4b3886ec9967cafabe4424d27d5 and later · before 54bcccc2c7805a00af1d7d2faffd6f424c0133aaaffected · git
    • 6ef88d6e36c2b4b3886ec9967cafabe4424d27d5 and later · before 53903ac9ca1abffa27327e85075ec496fa55ccf3affected · git
    • 6ef88d6e36c2b4b3886ec9967cafabe4424d27d5 and later · before 4da3768e1820cf15cced390242d8789aed34f54daffected · git
    • before 6.0not affected · semver
    • 6.1.160 and later · up to and including 6.1.*not affected · semver
    • 6.6.120 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.12-16.17.12-1
openSUSE:Tumbleweedkernel-sourcebefore 6.18.2-1.16.18.2-1.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68257Dec 16, 2025 · comedi: check device's attached status in compat ioctls
    0Monitor
  • ← EarlierCVE-2025-68258Dec 16, 2025 · comedi: multiq3: sanitize config options in multiq3_attach()
    0Monitor
  • Later →CVE-2025-68260Dec 16, 2025 · rust_binder: fix race condition on death_list
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux152289a51107ef45bbfe9b4aeeaa584a503042b5Vendor (CNA)
Linux Linux2e84a018c2895c05abe213eb10db128aa45f6ec6Vendor (CNA)
Linux Linux4da3768e1820cf15cced390242d8789aed34f54dVendor (CNA)
Linux Linux53903ac9ca1abffa27327e85075ec496fa55ccf3Vendor (CNA)
Linux Linux54bcccc2c7805a00af1d7d2faffd6f424c0133aaVendor (CNA)
Linux Linux87cc1622c88a4888959d64fa1fc9ba1e264aa3d4Vendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
opensuse:kernel-source6.18.2-1.1 · openSUSE:TumbleweedPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records