[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted amd64-microcode 2.20160316.1~bpo70+1 (amd64 i386 source) into wheezy-backports->backports-policy, wheezy-backports



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Sat, 19 Mar 2016 16:34:08 -0300
Source: amd64-microcode
Binary: amd64-microcode
Architecture: amd64 i386 source
Version: 2.20160316.1~bpo70+1
Distribution: wheezy-backports
Urgency: critical
Maintainer: Henrique de Moraes Holschuh <hmh@debian.org>
Changed-By: Henrique de Moraes Holschuh <hmh@debian.org>
Description: 
 amd64-microcode - Processor microcode firmware for AMD CPUs
Changes:
 amd64-microcode (2.20160316.1~bpo70+1) wheezy-backports; urgency=critical
 .
   * Rebuild for jessie-backports (no changes).
   * This is the same package as 2.20160316.1 and 2.20160316.1~deb8u1.
 .
 amd64-microcode (2.20160316.1) unstable; urgency=critical
 .
   * Upstream release 20160316 built from linux-firmware:
     + Updated Microcodes:
       sig 0x00600f20, patch id 0x0600084f, 2016-01-25
     + This microcode updates fixes a critical erratum on NMI handling
       introduced by microcode patch id 0x6000832 from the 20141028 update.
       The erratum is also present on microcode patch id 0x6000836.
     + THIS IS A CRITICAL STABILITY AND SECURITY UPDATE FOR THE EARLIER
       AMD PILEDRIVER PROCESSORS, including:
       + AMD Opteron 3300, 4300, 6300
       + AMD FX "Vishera" (43xx, 63xx, 83xx, 93xx, 95xx)
       + AMD processors with family 21, model 2, stepping 0
   * Robert Święcki, while fuzzing the kernel using the syzkaller tool,
     uncovered very strange behavior on an AMD FX-8320, later reproduced on
     other AMD Piledriver model 2, stepping 0 processors including the Opteron
     6300.  Robert discovered, using his proof-of-concept exploit code, that
     the incorrect behavior allows an unpriviledged attacker on an unpriviledged
     VM to corrupt the return stack of the host kernel's NMI handler.  At best,
     this results in unpredictable host behavior.  At worst, it allows for an
     unpriviledged user on unpriviledged VM to carry a sucessful host-kernel
     ring 0 code injection attack.
   * The erratum is timing-dependant, easily triggered by workloads that cause
     a high number of NMIs, such as running the "perf" tool.
Checksums-Sha1: 
 104cae95e8934c1c45fb045aa845a1e9ee0251ab 1713 amd64-microcode_2.20160316.1~bpo70+1.dsc
 88b6e9cb9a90e66292174eb929cd06c1a772f08b 29196 amd64-microcode_2.20160316.1~bpo70+1.tar.xz
 0a38c9f9f379e33ad090d796d30b513e0e252ac0 29720 amd64-microcode_2.20160316.1~bpo70+1_amd64.deb
 12ac0334f5f0740e4818b5c88ebda62114578741 29730 amd64-microcode_2.20160316.1~bpo70+1_i386.deb
Checksums-Sha256: 
 f4a33d89360340b2d89f96913df6c1f44b0eebe80e615c027d2b9281acad4b79 1713 amd64-microcode_2.20160316.1~bpo70+1.dsc
 a4c3fe48b363b542d08c545401ccff6a9fb94b484caf734cf642d2d121e4b9b3 29196 amd64-microcode_2.20160316.1~bpo70+1.tar.xz
 4d1fb6572515a4c6426b1b24256042cfa826a301ca53d0ff5896484c6be3e057 29720 amd64-microcode_2.20160316.1~bpo70+1_amd64.deb
 95b936b40e4a21419a6bbcad86b14eb6e1a3243f9125255047e36acfa5cfe126 29730 amd64-microcode_2.20160316.1~bpo70+1_i386.deb
Files: 
 71dc229516b4cfdd3d9483eb4f55bc6e 1713 non-free/admin standard amd64-microcode_2.20160316.1~bpo70+1.dsc
 ffdefb903a6299426a9cb4f692405e5e 29196 non-free/admin standard amd64-microcode_2.20160316.1~bpo70+1.tar.xz
 06d70f559316a5975a4367725c7ce8c5 29720 non-free/admin standard amd64-microcode_2.20160316.1~bpo70+1_amd64.deb
 6aeb7611d013a6271f13d62d874d640d 29730 non-free/admin standard amd64-microcode_2.20160316.1~bpo70+1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJW7a+bAAoJEJE3+9PebwqTRK4P/1ifx2xB6RuM6yBxkLyc9x7S
ZERGrzFxrp6BKpj9RyzN/ZTGxd+jiSE+nx96lzlaZKi8LvqNsBTVqJkicrYMXctb
jw4KJNz98VqhAgHgfRPDRRvMTr+9qCiOwtYNAdtWwpTJey6K0xTYRRCWugSiKDzO
sU/OkpPiludgxdpei0yLJTeZ7MoBCPcXeXj8InO2EvQzj5WC3/1DQjaldyo9/fzV
WhMQkjtayYCoU91tUGWGqO7m8tRadEBKnPYF6qKZKgnwm5t/QLOcs/pFd4UpE7m2
lpOXMGVxMaXVjiJLbzhOLOBqCG5LmFvWbxBsz6B+lU8+9u3DOdxEFi0DZ8kazAPV
yj4xQmLrnOqc3AFTeb8DTzK8yif05zpduHyGCSZy4Y+ZxjLl7DpMDuKb9ejTzyrc
jDSQwFn/CkaPCn2zDocROqAD2moOlOMi+joEOYhaEoXYINSSGZ5j63Pp+bGZnWtc
haQ1PLz8BUUez2tnc7aO6Ny6UCVHPi+5bzX0GPFDTh2WElXUb6l/Ud89B4gGHY4H
BwmCG3d6jveltIFDTVcXmIvdE1m83zRVYMDMym17oUJmkrgM7Ot4BVs6ENDutkDD
wcg8MDdeJVjD12QAb5gZ6T526RcpzMbYgIBlVxmnzZlZWLiQiQ+Z2pVFBaLUm0hj
82MWmnW9VicW62osIxgz
=3Xm2
-----END PGP SIGNATURE-----


Reply to: