{"api_version":"1","generated_at":"2026-11-20T07:30:03+00:00","cve":"CVE-2026-99712","urls":{"html":"https://cve.report/CVE-2026-99712","api":"https://cve.report/api/cve/CVE-2026-99712.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-99712","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-99712"},"summary":{"title":"KVM: x86: Conditionally resched when restarting REP string emulation","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Conditionally resched when restarting REP string emulation\n\nWhen restarting emulation, e.g. of a REP-prefixed string instruction,\nconditionally reschedule as emulating guest writes can be deceptively slow\nand expensive, e.g. when shadow paging is in use and each write can trigger\nwrite tracking.\n\nIn a perfect world, restarting emulation (or not) would be less arbitrary,\ne.g. would honor not only host events (NEED_RESCHED, signals, etc.) but\nalso guest events (e.g. by checking kvm_vcpu_has_events()).  Unfortunately,\nas pointed out by Sashiko, pio_in_emulated()'s read-ahead logic is baked\ninto the restart logic, as KVM relies on restarting emulation to drain the\ncache and avoid duplicate reads from the I/O port.  I.e. re-entering the\nguest on kvm_vcpu_has_events() or __xfer_to_guest_mode_work_pending() would\nintroduce architecturally-incorrect, guest-visible changes.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-11-20 06:18:07","updated_at":"2026-11-20 06:18:07"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/ae85ac25eb671d174811cc3101549448671fd505","name":"https://git.kernel.org/stable/c/ae85ac25eb671d174811cc3101549448671fd505","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5a5f9853a78c45927cd0814ae67c5ad8b5021bcc","name":"https://git.kernel.org/stable/c/5a5f9853a78c45927cd0814ae67c5ad8b5021bcc","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c1293d2134c2d63741b197a1e5a6363894ed4bce","name":"https://git.kernel.org/stable/c/c1293d2134c2d63741b197a1e5a6363894ed4bce","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/41a43510f77298d147a098eb182695d0001593c8","name":"https://git.kernel.org/stable/c/41a43510f77298d147a098eb182695d0001593c8","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-99712","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99712","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5cd21917da245fbe98bd443de2c7f519b3df6814 c1293d2134c2d63741b197a1e5a6363894ed4bce git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5cd21917da245fbe98bd443de2c7f519b3df6814 41a43510f77298d147a098eb182695d0001593c8 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5cd21917da245fbe98bd443de2c7f519b3df6814 5a5f9853a78c45927cd0814ae67c5ad8b5021bcc git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 5cd21917da245fbe98bd443de2c7f519b3df6814 ae85ac25eb671d174811cc3101549448671fd505 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 2.6.35","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 2.6.35 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.118 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.64 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3.5 7.3.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.4-rc2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["arch/x86/kvm/x86.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"c1293d2134c2d63741b197a1e5a6363894ed4bce","status":"affected","version":"5cd21917da245fbe98bd443de2c7f519b3df6814","versionType":"git"},{"lessThan":"41a43510f77298d147a098eb182695d0001593c8","status":"affected","version":"5cd21917da245fbe98bd443de2c7f519b3df6814","versionType":"git"},{"lessThan":"5a5f9853a78c45927cd0814ae67c5ad8b5021bcc","status":"affected","version":"5cd21917da245fbe98bd443de2c7f519b3df6814","versionType":"git"},{"lessThan":"ae85ac25eb671d174811cc3101549448671fd505","status":"affected","version":"5cd21917da245fbe98bd443de2c7f519b3df6814","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["arch/x86/kvm/x86.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"2.6.35"},{"lessThan":"2.6.35","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.118","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.64","versionType":"semver"},{"lessThanOrEqual":"7.3.*","status":"unaffected","version":"7.3.5","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.4-rc2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.118","versionStartIncluding":"2.6.35","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.64","versionStartIncluding":"2.6.35","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3.5","versionStartIncluding":"2.6.35","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.4-rc2","versionStartIncluding":"2.6.35","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Conditionally resched when restarting REP string emulation\n\nWhen restarting emulation, e.g. of a REP-prefixed string instruction,\nconditionally reschedule as emulating guest writes can be deceptively slow\nand expensive, e.g. when shadow paging is in use and each write can trigger\nwrite tracking.\n\nIn a perfect world, restarting emulation (or not) would be less arbitrary,\ne.g. would honor not only host events (NEED_RESCHED, signals, etc.) but\nalso guest events (e.g. by checking kvm_vcpu_has_events()).  Unfortunately,\nas pointed out by Sashiko, pio_in_emulated()'s read-ahead logic is baked\ninto the restart logic, as KVM relies on restarting emulation to drain the\ncache and avoid duplicate reads from the I/O port.  I.e. re-entering the\nguest on kvm_vcpu_has_events() or __xfer_to_guest_mode_work_pending() would\nintroduce architecturally-incorrect, guest-visible changes."}],"providerMetadata":{"dateUpdated":"2026-11-20T05:50:51.565Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/c1293d2134c2d63741b197a1e5a6363894ed4bce"},{"url":"https://git.kernel.org/stable/c/41a43510f77298d147a098eb182695d0001593c8"},{"url":"https://git.kernel.org/stable/c/5a5f9853a78c45927cd0814ae67c5ad8b5021bcc"},{"url":"https://git.kernel.org/stable/c/ae85ac25eb671d174811cc3101549448671fd505"}],"title":"KVM: x86: Conditionally resched when restarting REP string emulation","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-99712","datePublished":"2026-11-20T05:50:51.565Z","dateReserved":"2026-09-25T10:25:14.430Z","dateUpdated":"2026-11-20T05:50:51.565Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-11-20 06:18:07","lastModifiedDate":"2026-11-20 06:18:07","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"99712","Ordinal":"1","Title":"KVM: x86: Conditionally resched when restarting REP string emula","CVE":"CVE-2026-99712","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"99712","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nKVM: x86: Conditionally resched when restarting REP string emulation\n\nWhen restarting emulation, e.g. of a REP-prefixed string instruction,\nconditionally reschedule as emulating guest writes can be deceptively slow\nand expensive, e.g. when shadow paging is in use and each write can trigger\nwrite tracking.\n\nIn a perfect world, restarting emulation (or not) would be less arbitrary,\ne.g. would honor not only host events (NEED_RESCHED, signals, etc.) but\nalso guest events (e.g. by checking kvm_vcpu_has_events()).  Unfortunately,\nas pointed out by Sashiko, pio_in_emulated()'s read-ahead logic is baked\ninto the restart logic, as KVM relies on restarting emulation to drain the\ncache and avoid duplicate reads from the I/O port.  I.e. re-entering the\nguest on kvm_vcpu_has_events() or __xfer_to_guest_mode_work_pending() would\nintroduce architecturally-incorrect, guest-visible changes.","Type":"Description","Title":"KVM: x86: Conditionally resched when restarting REP string emula"}]}}}