{"push_id":859752364,"size":1,"distinct_size":1,"ref":"refs/heads/staging-4.3","head":"fd1e4cc4d1d100337931b6f6dc50ed0b9766968a","before":"e875e0e5fcc5912f71422b53674a97e5c0ae77be","commits":[{"sha":"fd1e4cc4d1d100337931b6f6dc50ed0b9766968a","author":{"email":"01de09643e0ae62e116f8bd77de435799874b456@suse.com","name":"Jan Beulich"},"message":"x86/HVM: always intercept #AC and #DB\n\nBoth being benign exceptions, and both being possible to get triggered\nby exception delivery, this is required to prevent a guest from locking\nup a CPU (resulting from no other VM exits occurring once getting into\nsuch a loop).\n\nThe specific scenarios:\n\n1) #AC may be raised during exception delivery if the handler is set to\nbe a ring-3 one by a 32-bit guest, and the stack is misaligned.\n\nThis is CVE-2015-5307 / XSA-156.\n\nReported-by: Benjamin Serebrin <serebrin@google.com>\n\n2) #DB may be raised during exception delivery when a breakpoint got\nplaced on a data structure involved in delivering the exception. This\ncan result in an endless loop when a 64-bit guest uses a non-zero IST\nfor the vector 1 IDT entry, but even without use of IST the time it\ntakes until a contributory fault would get raised (results depending\non the handler) may be quite long.\n\nThis is CVE-2015-8104 / XSA-156.\n\nSigned-off-by: Jan Beulich <jbeulich@suse.com>\nReviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>\nTested-by: Andrew Cooper <andrew.cooper3@citrix.com>\nmaster commit: bd2239d9fa975a1ee5bcd27c218ae042cd0a57bc\nmaster date: 2015-11-10 12:03:08 +0100","distinct":true,"url":"https://api.github.com/repos/mirage/xen/commits/fd1e4cc4d1d100337931b6f6dc50ed0b9766968a"}]}