[BACK]Return to errata70.html CVS log [TXT][DIR] Up to [local] / www

File: [local] / www / errata70.html (download) (as text)

Revision 1.35, Sun Mar 10 18:46:50 2024 UTC (2 months ago) by tj
Branch: MAIN
CVS Tags: HEAD
Changes since 1.34: +2 -1 lines

add 7.5 errata page

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

<title>OpenBSD 7.0 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/errata70.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.0 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="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>.
<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.0/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.0.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_nsd">
<strong>001: RELIABILITY FIX: October 31, 2021</strong>
&nbsp; <i>All architectures</i>
<br>
In certain configurations, nsd(8) can be crashed by a remote attacker.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/001_nsd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p002_bpf">
<strong>002: RELIABILITY FIX: October 31, 2021</strong>
&nbsp; <i>All architectures</i>
<br>
Opening /dev/bpf too often could lead to resource exhaustion.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/002_bpf.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p003_uipc">
<strong>003: SECURITY FIX: October 31, 2021</strong>
&nbsp; <i>All architectures</i>
<br>
The kernel could leak memory when closing unix sockets.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/003_uipc.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p004_rpki">
<strong>004: SECURITY FIX: November 9, 2021</strong>
&nbsp; <i>All architectures</i>
<br>
rpki-client(8) should handle CA misbehaviours as soft-errors.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/004_rpki.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p005_unpcon">
<strong>005: RELIABILITY FIX: November 26, 2021</strong>
&nbsp; <i>All architectures</i>
<br>
An unprivileged user could crash the kernel by using UNIX-domain
sockets in multiple threads.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/005_unpcon.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p006_x509">
<strong>006: SECURITY FIX: November 26, 2021</strong>
&nbsp; <i>All architectures</i>
<br>
In some situations the X.509 verifier would discard an error on
an unverified certificate chain, resulting in an authentication bypass.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/006_x509.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p007_xserver">
<strong>007: SECURITY FIX: December 14, 2021</strong>
&nbsp; <i>All architectures</i>
<br>
Multiple 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.0/common/007_xserver.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p008_mrt">
<strong>008: SECURITY FIX: December 16, 2021</strong>
&nbsp; <i>All architectures</i>
<br>
If multicast routing is used, kernel memory is leaked to userland.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/008_mrt.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p009_expat">
<strong>009: SECURITY FIX: January 19, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
Fix 8 security issues in libexpat, all related to fixed-size integer
math (integer overflow and invalid shifts) near memory allocation.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/009_expat.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p010_vmm">
<strong>010: RELIABILITY FIX: January 19, 2022</strong>
&nbsp; <i>amd64</i>
<br>
Intel-based vmm(4) hosts may have vm processes die due to host-side
state corruption.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/010_vmm.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p011_ppctrap">
<strong>011: SECURITY FIX: January 24, 2022</strong>
&nbsp; <i>macppc</i>
<br>
On PowerPC kernel memory is leaked to userland.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/011_ppctrap.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p012_gpuflush">
<strong>012: RELIABILITY FIX: February 2, 2022</strong>
&nbsp; <i>amd64 i386</i>
<br>
Userspace controlled code on GPU can access kernel memory on Intel
gen 8 and later GPUs.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/012_gpuflush.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p013_expat">
<strong>013: SECURITY FIX: February 2, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
Fix two security issues in libexpat related to integer overflow.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/013_expat.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p014_slaacd">
<strong>014: SECURITY FIX: February 21, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
More than 7 nameservers in an IPv6 router advertisement could crash slaacd.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/014_slaacd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p015_expat">
<strong>015: SECURITY FIX: February 24, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
Fix five security issues in libexpat related to encoding, stack
exhaustion, and integer overflow.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/015_expat.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p016_bignum">
<strong>016: SECURITY FIX: March 15, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
A malicious certificate can cause an infinite loop.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/016_bignum.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p017_slaacd">
<strong>017: SECURITY FIX: March 22, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
A malicious router advertisement could overflow heap memory in
unprivileged slaacd process.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/017_slaacd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p018_zlib">
<strong>018: SECURITY FIX: April 1, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
Memory corruption in zlib can lead to a crash.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/018_zlib.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p019_syszlib">
<strong>019: SECURITY FIX: April 5, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
Fix zlib vulnerability in PPP and IPComp compression.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/019_syszlib.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p020_rpki">
<strong>020: RELIABILITY FIX: April 11, 2022</strong>
&nbsp; <i>All architectures</i>
<br>
rpki-client(8) handled time zones incorrectly.
<br>
<a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.0/common/020_rpki.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p021_pppoe">
<strong>021: 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.0/common/021_pppoe.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p022_xserver">
<strong>022: 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.0/common/022_xserver.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p023_cron">
<strong>023: 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.0/common/023_cron.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p024_zlib">
<strong>024: 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.0/common/024_zlib.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p025_expat">
<strong>025: 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.0/common/025_expat.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

<li id="p026_smtpd">
<strong>026: 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.0/common/026_smtpd.patch.sig">
A source code patch exists which remedies this problem.</a>
<p>

</ul>

<hr>