File: [local] / www / errata64.html (download) (as text)
Revision 1.14, Tue Mar 26 19:44:41 2019 UTC (5 years, 2 months ago) by tj
Branch: MAIN
Changes since 1.13: +11 -0 lines
release vmmints errata.
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<title>OpenBSD 6.4 Errata</title>
<meta name="description" content="the OpenBSD errata page">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="openbsd.css">
<link rel="canonical" href="https://www.openbsd.org/errata64.html">
</head>
<!--
IMPORTANT REMINDER
IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
-->
<body bgcolor="#ffffff" text="#000000" link="#23238E">
<h2>
<a href="index.html">
<font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
<font color="#e00000">6.4 Errata</font>
</h2>
<hr>
For errata on a certain release, click below:<br>
<a href="errata21.html">2.1</a>,
<a href="errata22.html">2.2</a>,
<a href="errata23.html">2.3</a>,
<a href="errata24.html">2.4</a>,
<a href="errata25.html">2.5</a>,
<a href="errata26.html">2.6</a>,
<a href="errata27.html">2.7</a>,
<a href="errata28.html">2.8</a>,
<a href="errata29.html">2.9</a>,
<a href="errata30.html">3.0</a>,
<a href="errata31.html">3.1</a>,
<a href="errata32.html">3.2</a>,
<a href="errata33.html">3.3</a>,
<a href="errata34.html">3.4</a>,
<a href="errata35.html">3.5</a>,
<a href="errata36.html">3.6</a>,
<br>
<a href="errata37.html">3.7</a>,
<a href="errata38.html">3.8</a>,
<a href="errata39.html">3.9</a>,
<a href="errata40.html">4.0</a>,
<a href="errata41.html">4.1</a>,
<a href="errata42.html">4.2</a>,
<a href="errata43.html">4.3</a>,
<a href="errata44.html">4.4</a>,
<a href="errata45.html">4.5</a>,
<a href="errata46.html">4.6</a>,
<a href="errata47.html">4.7</a>,
<a href="errata48.html">4.8</a>,
<a href="errata49.html">4.9</a>,
<a href="errata50.html">5.0</a>,
<a href="errata51.html">5.1</a>,
<a href="errata52.html">5.2</a>,
<br>
<a href="errata53.html">5.3</a>,
<a href="errata54.html">5.4</a>,
<a href="errata55.html">5.5</a>,
<a href="errata56.html">5.6</a>,
<a href="errata57.html">5.7</a>,
<a href="errata58.html">5.8</a>,
<a href="errata59.html">5.9</a>,
<a href="errata60.html">6.0</a>,
<a href="errata61.html">6.1</a>,
<a href="errata62.html">6.2</a>,
<a href="errata63.html">6.3</a>.
<hr>
<p>
Patches for the OpenBSD base system are distributed as unified diffs.
Each patch is cryptographically signed with the
<a href="https://man.openbsd.org/OpenBSD-6.4/signify.1">signify(1)</a> tool and contains
usage instructions.
All the following patches are also available in one
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4.tar.gz">tar.gz file</a>
for convenience.
<p>
Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
utility can be used to apply binary updates on the following architectures:
amd64, i386, arm64.
<p>
Patches for supported releases are also incorporated into the
<a href="stable.html">-stable branch</a>, which is maintained for one year
after release.
<hr>
<ul>
<li id="p001_xserver">
<font color="#009000">
<strong>001: SECURITY FIX: October 25, 2018</strong></font>
<i>All architectures</i>
<br>
The Xorg X server incorrectly validates certain options, allowing arbitrary
files to be overwritten.
As an immediate (temporary) workaround, the Xorg binary can be disabled
by running: <code>chmod u-s /usr/X11R6/bin/Xorg</code>
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/001_xserver.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p002_syspatch">
<font color="#009000">
<strong>002: RELIABILITY FIX: November 2, 2018</strong></font>
<i>i386, amd64, arm64</i>
<br>
The syspatch utility incorrectly handles symbolic links.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/002_syspatch.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p003_portsmash">
<font color="#009000">
<strong>003: SECURITY FIX: November 17, 2018</strong></font>
<i>All architectures</i>
<br>
The portsmash vulnerability allows exfiltration of elliptic curve keys.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/003_portsmash.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p004_lockf">
<font color="#009000">
<strong>004: RELIABILITY FIX: November 17, 2018</strong></font>
<i>All architectures</i>
<br>
A recent change to POSIX file locks could cause incorrect results
during lock acquisition.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/004_lockf.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p005_perl">
<font color="#009000">
<strong>005: SECURITY FIX: November 29, 2018</strong></font>
<i>All architectures</i>
<br>
Various overflows exist in perl.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/005_perl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p006_uipc">
<font color="#009000">
<strong>006: RELIABILITY FIX: November 29, 2018</strong></font>
<i>All architectures</i>
<br>
UNIX domain sockets leak kernel memory with MSG_PEEK on SCM_RIGHTS, or can
attempt excessive memory allocations leading to a crash.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/006_uipc.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p007_smtpd">
<font color="#009000">
<strong>007: RELIABILITY FIX: November 29, 2018</strong></font>
<i>All architectures</i>
<br>
The mail.mda and mail.lmtp delivery agents were not reporting temporary
failures correctly, causing smtpd to bounce messages in some cases where
it should have retried them.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/007_smtpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p008_qcow2">
<font color="#009000">
<strong>008: RELIABILITY FIX: November 29, 2018</strong></font>
<i>amd64 and i386</i>
<br>
Writing more than 4GB to a qcow2 volume corrupts the virtual disk.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/008_qcow2.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p009_recvwait">
<font color="#009000">
<strong>009: RELIABILITY FIX: December 20, 2018</strong></font>
<i>All architectures</i>
<br>
While recv(2) with the MSG_WAITALL flag was receiving control
messages from a socket, the kernel could panic.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/009_recvwait.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p010_pcbopts">
<font color="#009000">
<strong>010: SECURITY FIX: December 22, 2018</strong></font>
<i>All architectures</i>
<br>
The setsockopt(2) system call could overflow mbuf cluster kernel
memory by 4 bytes.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/010_pcbopts.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p011_mincore">
<font color="#009000">
<strong>011: SECURITY FIX: January 27, 2019</strong></font>
<i>All architectures</i>
<br>
The mincore() system call can be used to observe memory access patterns
of other processes.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/011_mincore.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p012_nfs">
<font color="#009000">
<strong>012: RELIABILITY FIX: January 27, 2019</strong></font>
<i>All architectures</i>
<br>
Missing length checks in the NFS server and client can lead to crashes
and other errors.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/012_nfs.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p013_unveil">
<font color="#009000">
<strong>013: SECURITY FIX: January 27, 2019</strong></font>
<i>All architectures</i>
<br>
The unveil() system call can leak memory.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/013_unveil.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p014_pf6frag">
<font color="#009000">
<strong>014: SECURITY FIX: March 1, 2019</strong></font>
<i>All architectures</i>
<br>
Fragmented IPv6 packets may be erroneously passed by pf or lead to a crash.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/014_pf6frag.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p015_pficmp">
<font color="#009000">
<strong>015: SECURITY FIX: March 22, 2019</strong></font>
<i>All architectures</i>
<br>
A state in pf could pass ICMP packets to a destination IP address
that did not match the state.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/015_pficmp.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
<li id="p016_vmmints">
<font color="#009000">
<strong>016: SECURITY FIX: March 27, 2019</strong></font>
<i>amd64 and i386</i>
<br>
GDT and IDT limits were improperly restored during VMM context switches.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/016_vmmints.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>
</ul>
<hr>
</body>
</html>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata64.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www