For errata on a certain release, click below:
2.1,
2.2,
2.3,
2.4,
2.5,
2.6,
2.7,
2.8,
2.9,
3.0,
3.1,
3.2,
3.3,
3.4,
3.5,
3.6,
3.7,
3.8,
3.9,
4.0,
4.1,
4.2,
4.3,
4.4,
4.5,
4.6,
4.7,
4.8,
4.9,
5.0,
5.1,
5.2,
5.3,
5.4,
5.5,
5.6,
5.7,
5.8,
5.9,
6.0,
6.1,
6.2,
6.3,
6.4,
6.6.
Patches for the OpenBSD base system are distributed as unified diffs.
Each patch is cryptographically signed with the
signify(1) tool and contains
usage instructions.
All the following patches are also available in one
tar.gz file
for convenience.
Alternatively, the syspatch(8)
utility can be used to apply binary updates on the following architectures:
amd64, i386, arm64.
Patches for supported releases are also incorporated into the
-stable branch, which is maintained for one year
after release.
-
001: RELIABILITY FIX: May 3, 2019
All architectures
If a userland program sets the IPv6 checksum offset on a raw socket,
an incoming packet could crash the kernel. ospf6d is such a program.
A source code patch exists which remedies this problem.
-
002: RELIABILITY FIX: May 16, 2019
All architectures
LibreSSL servers did not provide an SRTP profile, so DTLS negotiation failed.
A source code patch exists which remedies this problem.
-
003: SECURITY FIX: May 29, 2019
amd64
Intel CPUs have a cross privilege side-channel attack (MDS).
A source code patch exists which remedies this problem.
-
004: RELIABILITY FIX: June 10, 2019
All architectures
Several issues were corrected in bgpd: "network" statements with no fixed
prefix were incorrectly removed when configuration was reloaded, "export
default-route" did not work, and "network 0.0.0.0/0" could not be used
in some cases.
A source code patch exists which remedies these problems.
-
005: RELIABILITY FIX: June 10, 2019
All architectures
TLS handshakes fail if a client supporting TLS 1.3 tries to connect to
an OpenBSD server and sends a key share extension that does not include
X25519.
A source code patch exists which remedies this problem.
-
006: RELIABILITY FIX: July 25, 2019
All architectures
By creating long chains of TCP SACK holes, an attacker could possibly
slow down the system temporarily.
A source code patch exists which remedies this problem.
-
007: RELIABILITY FIX: August 2, 2019
All architectures
smtpd can crash on excessively large input, causing a denial of service.
A source code patch exists which remedies this problem.
-
008: SECURITY FIX: August 9, 2019
amd64
Intel CPUs have another cross privilege side-channel attack. (SWAPGS)
A source code patch exists which remedies this problem.
-
009: RELIABILITY FIX: September 2, 2019
amd64
Resume forgot to restore MSR/PAT configuration.
A source code patch exists which remedies this problem.
-
010: RELIABILITY FIX: September 2, 2019
All architectures
When processing ECN bits on incoming IPv6 fragments, the kernel
could crash. Per default pf fragment reassemble prevents the crash.
A source code patch exists which remedies this problem.
-
011: SECURITY FIX: September 14, 2019
All architectures
Libexpat 2.2.6 was affected by the heap overflow CVE-2019-15903.
A source code patch exists which remedies this problem.
-
012: RELIABILITY FIX: October 3, 2019
All architectures
The sysupgrade utility can be used to upgrade the system to the next
release or to a new snapshot.
A source code patch exists which adds this utility.
-
013: RELIABILITY FIX: October 5, 2019
All architectures
Specially crafted queries may crash unwind and unbound.
A source code patch exists which remedies this problem.
-
014: SECURITY FIX: October 5, 2019
All architectures
dhcpd leaks 4 bytes of stack to the network.
A source code patch exists which remedies this problem.
-
015: RELIABILITY FIX: November 16, 2019
All architectures
The kernel could crash due to a NULL pointer dereference in net80211.
A source code patch exists which remedies this problem.
-
016: RELIABILITY FIX: November 16, 2019
All architectures
A new kernel may require newer firmware images when using sysupgrade.
A source code patch exists which remedies this problem.
-
017: SECURITY FIX: November 16, 2019
All architectures
A regular user could change some network interface parameters due
to missing checks in the ioctl(2) system call.
A source code patch exists which remedies this problem.