errata66.html

<!doctype html>
<html lang=en id=errata>
<meta charset=utf-8>

<title>OpenBSD 6.6 Errata</title>
<meta name="description" content="the OpenBSD errata page">
<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/errata66.html">

<!--
			IMPORTANT REMINDER
	IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
-->

<h2 id=OpenBSD>
<a href="index.html">
<i>Open</i><b>BSD</b></a>
6.6 Errata
</h2>
<hr>

For errata on a certain release, click below:<br>
<a href="errata20.html">2.0</a>,
<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>,
<br>
<a href="errata36.html">3.6</a>,
<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>,
<br>
<a href="errata52.html">5.2</a>,
<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>,
<a href="errata64.html">6.4</a>,
<a href="errata65.html">6.5</a>,
<a href="errata67.html">6.7</a>,
<a href="errata68.html">6.8</a>,
<br>
<a href="errata69.html">6.9</a>,
<a href="errata70.html">7.0</a>,
<a href="errata71.html">7.1</a>,
<a href="errata72.html">7.2</a>,
<a href="errata73.html">7.3</a>,
<a href="errata74.html">7.4</a>,
<a href="errata75.html">7.5</a>,
<a href="errata76.html">7.6</a>,
<a href="errata77.html">7.7</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.6/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.6.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>.

<hr>

<ul>

<li id="p001_bpf">
<strong>001: RELIABILITY FIX: October 28, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
bpf(4) has a race condition during device removal.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/001_bpf.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p002_ber">
<strong>002: RELIABILITY FIX: October 28, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
Various third party applications may crash due to symbol collision.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/002_ber.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p003_bgpd">
<strong>003: RELIABILITY FIX: October 31, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
bgpd(8) can crash on nexthop changes or during startup in certain
configurations.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/003_bgpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p004_net80211">
<strong>004: RELIABILITY FIX: November 16, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
The kernel could crash due to a NULL pointer dereference in net80211.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/004_net80211.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p005_sysupgrade">
<strong>005: RELIABILITY FIX: November 16, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
A new kernel may require newer firmware images when using sysupgrade.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/005_sysupgrade.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p006_ifioctl">
<strong>006: SECURITY FIX: November 16, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
A regular user could change some network interface parameters due
to missing checks in the ioctl(2) system call.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/006_ifioctl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p007_inteldrm">
<strong>007: SECURITY FIX: November 22, 2019</strong>
&nbsp; <i>i386 and amd64</i>
<br>
A local user could cause the system to hang by reading specific
registers when Intel Gen8/Gen9 graphics hardware is in a low power state.
A local user could perform writes to memory that should be blocked with
Intel Gen9 graphics hardware.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/007_inteldrm.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p008_mesa">
<strong>008: SECURITY FIX: November 22, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
Shared memory regions used by some Mesa drivers had permissions which
allowed others to access that memory.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/008_mesa.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p009_mesaxlock">
<strong>009: SECURITY FIX: December 4, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
Environment-provided paths are used for dlopen() in mesa, resulting in
escalation to the auth group in xlock(1).
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/009_mesaxlock.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p010_libcauth">
<strong>010: SECURITY FIX: December 4, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
libc's authentication layer performed insufficient username validation.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/010_libcauth.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p011_xenodm">
<strong>011: SECURITY FIX: December 4, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
xenodm uses the libc authentication layer incorrectly.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/011_xenodm.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p012_suauth">
<strong>012: SECURITY FIX: December 8, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
A user can log in with a different user's login class.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/012_suauth.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p013_ldso">
<strong>013: SECURITY FIX: December 11, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
ld.so may fail to remove the LD_LIBRARY_PATH environment variable for
set-user-ID and set-group-ID executables in low memory conditions.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/013_ldso.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p014_eret">
<strong>014: SECURITY FIX: December 18, 2019</strong>
&nbsp; <i>arm64</i>
<br>
ARM64 CPUs speculatively execute instructions after ERET.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/014_eret.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p015_ftp">
<strong>015: SECURITY FIX: December 20, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
ftp(1) will follow remote redirects to local files.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/015_ftp.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p016_ripd">
<strong>016: SECURITY FIX: December 20, 2019</strong>
&nbsp; <i>All architectures</i>
<br>
ripd(8) fails to validate authentication lengths.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/016_ripd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p017_inteldrmctx">
<strong>017: SECURITY FIX: January 17, 2020</strong>
&nbsp; <i>i386 and amd64</i>
<br>
Execution Unit state was not cleared on context switch with Intel Gen9
graphics hardware.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/017_inteldrmctx.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p018_smtpd_tls">
<strong>018: RELIABILITY FIX: January 30, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
smtpd can crash on opportunistic TLS downgrade, causing a denial of service.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/018_smtpd_tls.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p019_smtpd_exec">
<strong>019: SECURITY FIX: January 30, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
An incorrect check allows an attacker to trick mbox delivery into executing
arbitrary commands as root and lmtp delivery into executing arbitrary commands
as an unprivileged user.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/019_smtpd_exec.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p020_vmm_pvclock">
<strong>020: SECURITY FIX: February 17, 2020</strong>
&nbsp; <i>amd64</i>
<br>
A missing range check in the vmm pvclock allows a guest to write
to host memory.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/020_vmm_pvclock.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p021_smtpd_envelope">
<strong>021: SECURITY FIX: February 24, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
An out of bounds read in smtpd allows an attacker to inject arbitrary
commands into the envelope file which are then executed as root.
Separately, missing privilege revocation in smtpctl allows arbitrary
commands to be run with the _smtpq group.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/021_smtpd_envelope.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p022_sysctl">
<strong>022: RELIABILITY FIX: March 10, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
Missing input validation in sysctl(2) can be used to crash the kernel.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/022_sysctl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p023_sosplice">
<strong>023: RELIABILITY FIX: March 13, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
Local outbound UDP broadcast or multicast packets sent by a spliced
socket can crash the kernel.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/023_sosplice.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p024_dhcpd">
<strong>024: SECURITY FIX: April 7, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
dhcpd could reference freed memory after releasing a lease with an
unusually long uid.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/024_dhcpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p025_drm">
<strong>025: SECURITY FIX: April 19, 2020</strong>
&nbsp; <i>i386, amd64, arm64, loongson, macppc, sparc64</i>
<br>
There was an incorrect test for root in the DRM Linux compatibility code.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/025_drm.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p026_ospfd_lsa">
<strong>026: RELIABILITY FIX: May 10, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
ospfd could generate corrupt OSPF Router (Type 1) LSAs in certain situations.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/026_ospfd_lsa.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p027_wscons">
<strong>027: SECURITY FIX: May 13, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
An out-of-bounds index access in wscons(4) can cause a kernel crash.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/027_wscons.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p028_unbound">
<strong>028: SECURITY FIX: May 22, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
Specially crafted queries may crash unbound and unwind.
Both can be tricked into amplifying an incoming query.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/028_unbound.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p029_perl">
<strong>029: SECURITY FIX: June 1, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
Several problems in Perl's regular expression compiler could lead to
corruption of the intermediate language state of a compiled regular
expression.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/029_perl.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p030_hid">
<strong>030: SECURITY FIX: June 5, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
Malicious HID descriptors could be misparsed.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/030_hid.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p031_asr">
<strong>031: RELIABILITY FIX: June 8, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
libc's resolver could get into a corrupted state.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/031_asr.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p032_x509">
<strong>032: RELIABILITY FIX: June 11, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
libcrypto may fail to build a valid certificate chain due to
expired untrusted issuer certificates.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/032_x509.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p033_shmget">
<strong>033: SECURITY FIX: July 9, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
shmget IPC_STAT leaked some kernel data.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/033_shmget.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p034_tty">
<strong>034: RELIABILITY FIX: July 16, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
tty subsystem abuse can impact performance badly.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/034_tty.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p035_tty">
<strong>035: RELIABILITY FIX: July 22, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
Only pty devices need reprint delays.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/035_tty.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p036_iked">
<strong>036: SECURITY FIX: July 27, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
In iked, incorrect use of EVP_PKEY_cmp allows an authentication bypass.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/036_iked.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p037_ximcp">
<strong>037: SECURITY FIX: July 31, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
Malformed messages can cause heap corruption in the X Input Method
client implementation in libX11.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/037_ximcp.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p038_dix">
<strong>038: SECURITY FIX: July 31, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
Pixmaps inside the xserver were an info leak.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/038_dix.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p039_ximcp">
<strong>039: RELIABILITY FIX: August 7, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
The recent security errata 037 broke X11 input methods.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/039_ximcp.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p040_xinitom">
<strong>040: SECURITY FIX: August 25, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
An integer overflow in libX11 could lead to a double free.
Additionally fix a regression in ximcp.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/040_xinitom.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p041_xserverlen">
<strong>041: SECURITY FIX: August 25, 2020</strong>
&nbsp; <i>All architectures</i>
<br>
Various X server extensions had deficient input validation.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/041_xserverlen.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p042_amdgpu">
<strong>042: SECURITY FIX: September 5, 2020</strong>
&nbsp; <i>amd64, arm64</i>
<br>
A buffer overflow was discovered in an amdgpu ioctl.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/042_amdgpu.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

</ul>

<hr>