version 1.16, 2018/08/06 14:48:10 |
version 1.17, 2018/08/23 19:30:02 |
|
|
A source code patch exists which remedies this problem.</a> |
A source code patch exists which remedies this problem.</a> |
<p> |
<p> |
|
|
|
<li id="p017_fpufork"> |
|
<font color="#009000"> |
|
<strong>017: SECURITY FIX: August 24, 2018</strong></font> |
|
<i>amd64</i> |
|
<br> |
|
State from the FPU of one userland process could be exposed to other processes. |
|
<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/017_fpufork.patch.sig"> |
|
A source code patch exists which remedies this problem.</a> |
|
<p> |
|
|
|
<li id="p018_vmml1tf"> |
|
<font color="#009000"> |
|
<strong>018: SECURITY FIX: August 24, 2018</strong></font> |
|
<i>amd64</i> |
|
<br> |
|
The Intel L1TF bug allows a vmm guest to read host memory. |
|
Install the CPU firmware using fw_update(1) and apply this workaround. |
|
<br> |
|
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.3/common/018_vmml1tf.patch.sig"> |
|
A source code patch exists which remedies this problem.</a> |
|
<p> |
|
|
</ul> |
</ul> |
|
|
<hr> |
<hr> |