errata71.html

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

<title>OpenBSD 7.1 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/errata71.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>
7.1 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="errata66.html">6.6</a>,
<a href="errata67.html">6.7</a>,
<br>
<a href="errata68.html">6.8</a>,
<a href="errata69.html">6.9</a>,
<a href="errata70.html">7.0</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-7.1/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/7.1.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_wifi">
<strong>001: RELIABILITY FIX: April 22, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
Many wireless network drivers could not scan access points correctly.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/001_wifi.patch.sig">
A source code patch exists which remedies this problem.</a><br>
<b>Notice:</b>
Some users will have installed a broken version of the
<b>syspatch71-001_wifi.tgz</b> file (which prevents future syspatch files
from installing), and must manually perform the following step to force
deletion of the old file, and then syspatch forward:<br>
<kbd># sed -i /release/d /usr/sbin/syspatch && syspatch -R && syspatch</kbd>
<p>

<li id="p002_ipsec">
<strong>002: RELIABILITY FIX: May 5, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
When using IPsec, the kernel could crash.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/002_ipsec.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p003_kqueue">
<strong>003: RELIABILITY FIX: May 16, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
The kernel could crash due to a race in kqueue.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/003_kqueue.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p004_asn1">
<strong>004: RELIABILITY FIX: May 16, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
libcrypto would incorrectly decode certain ASN.1 objects.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/004_asn1.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p005_pppoe">
<strong>005: SECURITY FIX: May 16, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
Malicious PPPoE packets could corrupt kernel memory.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/005_pppoe.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p006_xserver">
<strong>006: SECURITY FIX: July 24, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
Input validation failures in the X server request parsing code can
lead to out of bounds memory accesses for authorized clients.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/006_xserver.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p007_cron">
<strong>007: RELIABILITY FIX: July 24, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
cron(8) aborted due to strange poll timevals.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/007_cron.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p008_bgpd">
<strong>008: RELIABILITY FIX: August 2, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
bgpd(8) could fail to invalidate nexthops and incorrectly leave them in
the FIB or Adj-RIB-Out.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/008_bgpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p009_zlib">
<strong>009: SECURITY FIX: August 12, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
A missing length check in zlib could lead to a heap buffer overflow.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/009_zlib.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p010_expat">
<strong>010: SECURITY FIX: September 23, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
In libexpat fix heap use-after-free vulnerability CVE-2022-40674.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/010_expat.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p011_smtpd">
<strong>011: SECURITY FIX: September 26, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
In smtpd(8), possible use-after-free if TLS handshake fails for
outbound connections.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/011_smtpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p012_expat">
<strong>012: SECURITY FIX: November 1, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
In libexpat fix heap use-after-free vulnerability CVE-2022-43680.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/012_expat.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p013_pixman">
<strong>013: SECURITY FIX: November 14, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
CVE-2022-44638: An integer overflow in pixman may lead to an out-of-bounds
write.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/013_pixman.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p014_unwind">
<strong>014: SECURITY FIX: November 26, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
A crafted TCP query from localhost could crash the unwind(8) daemon.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/014_unwind.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p015_xserver">
<strong>015: SECURITY FIX: December 14, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
In X11 server fix local privileges elevation and remote code
execution for ssh X forwarding sessions.  This addresses CVE-2022-46340
CVE-2022-46341 CVE-2022-46342 CVE-2022-46343 CVE-2022-46344.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/015_xserver.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p016_gpuinv">
<strong>016: RELIABILITY FIX: December 14, 2022</strong>
&nbsp; <i>amd64 i386</i>
<br>
TLB entries were not invalidated for all types of engine on
12th generation Intel graphics (Tiger Lake, Rocket Lake, Alder Lake).
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/016_gpuinv.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p017_acme">
<strong>017: RELIABILITY FIX: December 16, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
Removing a domain can result in an out-of-bounds write in acme-client(8).
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/017_acme.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p018_tcp">
<strong>018: SECURITY FIX: January 13, 2023</strong>
&nbsp; <i>All architectures</i>
<br>
A TCP packet with destination port 0 that matches a pf divert-to
rule could crash the kernel.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/018_tcp.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p019_libxpm">
<strong>019: SECURITY FIX: January 17, 2023</strong>
&nbsp; <i>All architectures</i>
<br>
Input validation issues and path validation issues in libXpm can lead
to infinite loops, memory corruption or arbitrary command execution.
CVE-2022-46285, CVE-2022-44617 and CVE-2022-4883
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/019_libxpm.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p020_vmm">
<strong>020: SECURITY FIX: January 21, 2023</strong>
&nbsp; <i>amd64</i>
<br>
vmm(4) exposed unsupported cpuid feature flags to guests.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/020_vmm.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p021_vmd">
<strong>021: SECURITY FIX: January 21, 2023</strong>
&nbsp; <i>amd64</i>
<br>
vmd(8) exposed unsupported cpuid feature flags to guests.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/021_vmd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p022_x509">
<strong>022: SECURITY FIX: February 7, 2023</strong>
&nbsp; <i>All architectures</i>
<br>
A malicious certificate revocation list or timestamp response token would
allow an attacker to read arbitrary memory.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/022_x509.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p023_xserver">
<strong>023: SECURITY FIX: February 7, 2023</strong>
&nbsp; <i>All architectures</i>
<br>
CVE-2023-0494: use after free in the Xinput X server extension.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/023_xserver.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p024_smtpd">
<strong>024: SECURITY FIX: February 7, 2023</strong>
&nbsp; <i>All architectures</i>
<br>
smtpd(8) could abort due to a connection from a local, scoped ipv6 address.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/024_smtpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p025_wscons">
<strong>025: RELIABILITY FIX: February 26, 2023</strong>
&nbsp; <i>All architectures</i>
<br>
Missing bounds check in console terminal emulation could cause a kernel
crash after receiving specially crafted escape sequences.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/025_wscons.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p026_resolv">
<strong>026: SECURITY FIX: March 16, 2023</strong>
&nbsp; <i>All architectures</i>
<br>
Out of bounds accesses in libc resolver.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/026_resolv.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p027_bgpd">
<strong>027: RELIABILITY FIX: March 23, 2023</strong>
&nbsp; <i>All architectures</i>
<br>
Incorrect length checks allow an out-of-bounds read in bgpd(8).
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/027_bgpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p028_xserver">
<strong>028: SECURITY FIX: March 29, 2023</strong>
&nbsp; <i>All architectures</i>
<br>
Xserver, CVE-2023-1393: use after free bug in the Composite server extension.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/028_xserver.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

</ul>

<hr>