{"id":"AZL-115576","summary":"CVE-2026-99712 affecting package kernel 6.6.161.1-1","details":"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.","modified":"2026-11-21T14:17:23.958321921Z","published":"2026-11-20T06:18:07Z","upstream":["CVE-2026-99712"],"references":[{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-99712"}],"affected":[{"package":{"name":"kernel","ecosystem":"Azure Linux:3","purl":"pkg:rpm/azure-linux/kernel"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"6.6.161.1-1"}]}],"database_specific":{"source":"https://github.com/microsoft/AzureLinuxVulnerabilityData/blob/main/osv/AZL-115576.json"}}],"schema_version":"1.9.2"}