Annotation of www/errata71.html, Revision 1.14
1.1 deraadt 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
5: <title>OpenBSD 7.1 Errata</title>
6: <meta name="description" content="the OpenBSD errata page">
7: <meta name="viewport" content="width=device-width, initial-scale=1">
8: <link rel="stylesheet" type="text/css" href="openbsd.css">
9: <link rel="canonical" href="https://www.openbsd.org/errata71.html">
10:
11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
15:
16: <h2 id=OpenBSD>
17: <a href="index.html">
18: <i>Open</i><b>BSD</b></a>
19: 7.1 Errata
20: </h2>
21: <hr>
22:
23: For errata on a certain release, click below:<br>
24: <a href="errata20.html">2.0</a>,
25: <a href="errata21.html">2.1</a>,
26: <a href="errata22.html">2.2</a>,
27: <a href="errata23.html">2.3</a>,
28: <a href="errata24.html">2.4</a>,
29: <a href="errata25.html">2.5</a>,
30: <a href="errata26.html">2.6</a>,
31: <a href="errata27.html">2.7</a>,
32: <a href="errata28.html">2.8</a>,
33: <a href="errata29.html">2.9</a>,
34: <a href="errata30.html">3.0</a>,
35: <a href="errata31.html">3.1</a>,
36: <a href="errata32.html">3.2</a>,
37: <a href="errata33.html">3.3</a>,
38: <a href="errata34.html">3.4</a>,
39: <a href="errata35.html">3.5</a>,
40: <br>
41: <a href="errata36.html">3.6</a>,
42: <a href="errata37.html">3.7</a>,
43: <a href="errata38.html">3.8</a>,
44: <a href="errata39.html">3.9</a>,
45: <a href="errata40.html">4.0</a>,
46: <a href="errata41.html">4.1</a>,
47: <a href="errata42.html">4.2</a>,
48: <a href="errata43.html">4.3</a>,
49: <a href="errata44.html">4.4</a>,
50: <a href="errata45.html">4.5</a>,
51: <a href="errata46.html">4.6</a>,
52: <a href="errata47.html">4.7</a>,
53: <a href="errata48.html">4.8</a>,
54: <a href="errata49.html">4.9</a>,
55: <a href="errata50.html">5.0</a>,
56: <a href="errata51.html">5.1</a>,
57: <br>
58: <a href="errata52.html">5.2</a>,
59: <a href="errata53.html">5.3</a>,
60: <a href="errata54.html">5.4</a>,
61: <a href="errata55.html">5.5</a>,
62: <a href="errata56.html">5.6</a>,
63: <a href="errata57.html">5.7</a>,
64: <a href="errata58.html">5.8</a>,
65: <a href="errata59.html">5.9</a>,
66: <a href="errata60.html">6.0</a>,
67: <a href="errata61.html">6.1</a>,
68: <a href="errata62.html">6.2</a>,
69: <a href="errata63.html">6.3</a>,
70: <a href="errata64.html">6.4</a>,
71: <a href="errata65.html">6.5</a>,
72: <a href="errata66.html">6.6</a>,
73: <a href="errata67.html">6.7</a>,
74: <br>
75: <a href="errata68.html">6.8</a>,
76: <a href="errata69.html">6.9</a>,
1.13 deraadt 77: <a href="errata70.html">7.0</a>,
78: <a href="errata72.html">7.2</a>.
1.1 deraadt 79: <hr>
80:
81: <p>
82: Patches for the OpenBSD base system are distributed as unified diffs.
83: Each patch is cryptographically signed with the
84: <a href="https://man.openbsd.org/OpenBSD-7.1/signify.1">signify(1)</a> tool and contains
85: usage instructions.
86: All the following patches are also available in one
87: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1.tar.gz">tar.gz file</a>
88: for convenience.
89:
90: <p>
91: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
92: utility can be used to apply binary updates on the following architectures:
93: amd64, i386, arm64.
94:
95: <p>
96: Patches for supported releases are also incorporated into the
97: <a href="stable.html">-stable branch</a>, which is maintained for one year
98: after release.
99:
100: <hr>
101:
102: <ul>
103:
1.2 bluhm 104: <li id="p001_wifi">
105: <strong>001: RELIABILITY FIX: April 22, 2022</strong>
106: <i>All architectures</i>
107: <br>
108: Many wireless network drivers could not scan access points correctly.
109: <br>
110: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/001_wifi.patch.sig">
1.3 benno 111: A source code patch exists which remedies this problem.</a><br>
1.4 deraadt 112: <b>Notice:</b>
1.6 deraadt 113: Some users will have installed a broken version of the
114: <b>syspatch71-001_wifi.tgz</b> file (which prevents future syspatch files
115: from installing), and must manually perform the following step to force
116: deletion of the old file, and then syspatch forward:<br>
1.4 deraadt 117: <kbd># sed -i /release/d /usr/sbin/syspatch && syspatch -R && syspatch</kbd>
1.7 bluhm 118: <p>
1.3 benno 119:
1.7 bluhm 120: <li id="p002_ipsec">
121: <strong>002: RELIABILITY FIX: May 5, 2022</strong>
122: <i>All architectures</i>
123: <br>
124: When using IPsec, the kernel could crash.
125: <br>
126: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/002_ipsec.patch.sig">
127: A source code patch exists which remedies this problem.</a>
1.1 deraadt 128: <p>
129:
1.8 bluhm 130: <li id="p003_kqueue">
131: <strong>003: RELIABILITY FIX: May 16, 2022</strong>
132: <i>All architectures</i>
133: <br>
134: The kernel could crash due to a race in kqueue.
135: <br>
136: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/003_kqueue.patch.sig">
137: A source code patch exists which remedies this problem.</a>
138: <p>
139:
140: <li id="p004_asn1">
141: <strong>004: RELIABILITY FIX: May 16, 2022</strong>
142: <i>All architectures</i>
143: <br>
144: libcrypto would incorrectly decode certain ASN.1 objects.
145: <br>
146: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/004_asn1.patch.sig">
147: A source code patch exists which remedies this problem.</a>
148: <p>
149:
150: <li id="p005_pppoe">
151: <strong>005: SECURITY FIX: May 16, 2022</strong>
152: <i>All architectures</i>
153: <br>
154: Malicious PPPoE packets could corrupt kernel memory.
155: <br>
156: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/005_pppoe.patch.sig">
157: A source code patch exists which remedies this problem.</a>
158: <p>
159:
1.9 bluhm 160: <li id="p006_xserver">
161: <strong>006: SECURITY FIX: July 24, 2022</strong>
162: <i>All architectures</i>
163: <br>
164: Input validation failures in the X server request parsing code can
165: lead to out of bounds memory accesses for authorized clients.
166: <br>
167: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/006_xserver.patch.sig">
168: A source code patch exists which remedies this problem.</a>
169: <p>
170:
171: <li id="p007_cron">
172: <strong>007: RELIABILITY FIX: July 24, 2022</strong>
173: <i>All architectures</i>
174: <br>
175: cron(8) aborted due to strange poll timevals.
176: <br>
177: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/007_cron.patch.sig">
178: A source code patch exists which remedies this problem.</a>
179: <p>
180:
1.10 bluhm 181: <li id="p008_bgpd">
182: <strong>008: RELIABILITY FIX: August 2, 2022</strong>
183: <i>All architectures</i>
184: <br>
185: bgpd(8) could fail to invalidate nexthops and incorrectly leave them in
186: the FIB or Adj-RIB-Out.
187: <br>
188: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/008_bgpd.patch.sig">
189: A source code patch exists which remedies this problem.</a>
190: <p>
191:
1.11 bluhm 192: <li id="p009_zlib">
193: <strong>009: SECURITY FIX: August 12, 2022</strong>
194: <i>All architectures</i>
195: <br>
196: A missing length check in zlib could lead to a heap buffer overflow.
197: <br>
198: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/009_zlib.patch.sig">
199: A source code patch exists which remedies this problem.</a>
200: <p>
201:
1.12 bluhm 202: <li id="p010_expat">
203: <strong>010: SECURITY FIX: September 23, 2022</strong>
204: <i>All architectures</i>
205: <br>
206: In libexpat fix heap use-after-free vulnerability CVE-2022-40674.
207: <br>
208: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/010_expat.patch.sig">
209: A source code patch exists which remedies this problem.</a>
210: <p>
211:
1.14 ! bluhm 212: <li id="p011_smtpd">
! 213: <strong>011: SECURITY FIX: September 26, 2022</strong>
! 214: <i>All architectures</i>
! 215: <br>
! 216: In smtpd(8), possible use-after-free if TLS handshake fails for
! 217: outbound connections.
! 218: <br>
! 219: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/011_smtpd.patch.sig">
! 220: A source code patch exists which remedies this problem.</a>
! 221: <p>
! 222:
1.1 deraadt 223: </ul>
224:
225: <hr>