Annotation of www/errata71.html, Revision 1.25
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
1.15 tj 97: <a href="stable.html">-stable branch</a>.
1.1 deraadt 98:
99: <hr>
100:
101: <ul>
102:
1.2 bluhm 103: <li id="p001_wifi">
104: <strong>001: RELIABILITY FIX: April 22, 2022</strong>
105: <i>All architectures</i>
106: <br>
107: Many wireless network drivers could not scan access points correctly.
108: <br>
109: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/001_wifi.patch.sig">
1.3 benno 110: A source code patch exists which remedies this problem.</a><br>
1.4 deraadt 111: <b>Notice:</b>
1.6 deraadt 112: Some users will have installed a broken version of the
113: <b>syspatch71-001_wifi.tgz</b> file (which prevents future syspatch files
114: from installing), and must manually perform the following step to force
115: deletion of the old file, and then syspatch forward:<br>
1.4 deraadt 116: <kbd># sed -i /release/d /usr/sbin/syspatch && syspatch -R && syspatch</kbd>
1.7 bluhm 117: <p>
1.3 benno 118:
1.7 bluhm 119: <li id="p002_ipsec">
120: <strong>002: RELIABILITY FIX: May 5, 2022</strong>
121: <i>All architectures</i>
122: <br>
123: When using IPsec, the kernel could crash.
124: <br>
125: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/002_ipsec.patch.sig">
126: A source code patch exists which remedies this problem.</a>
1.1 deraadt 127: <p>
128:
1.8 bluhm 129: <li id="p003_kqueue">
130: <strong>003: RELIABILITY FIX: May 16, 2022</strong>
131: <i>All architectures</i>
132: <br>
133: The kernel could crash due to a race in kqueue.
134: <br>
135: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/003_kqueue.patch.sig">
136: A source code patch exists which remedies this problem.</a>
137: <p>
138:
139: <li id="p004_asn1">
140: <strong>004: RELIABILITY FIX: May 16, 2022</strong>
141: <i>All architectures</i>
142: <br>
143: libcrypto would incorrectly decode certain ASN.1 objects.
144: <br>
145: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/004_asn1.patch.sig">
146: A source code patch exists which remedies this problem.</a>
147: <p>
148:
149: <li id="p005_pppoe">
150: <strong>005: SECURITY FIX: May 16, 2022</strong>
151: <i>All architectures</i>
152: <br>
153: Malicious PPPoE packets could corrupt kernel memory.
154: <br>
155: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/005_pppoe.patch.sig">
156: A source code patch exists which remedies this problem.</a>
157: <p>
158:
1.9 bluhm 159: <li id="p006_xserver">
160: <strong>006: SECURITY FIX: July 24, 2022</strong>
161: <i>All architectures</i>
162: <br>
163: Input validation failures in the X server request parsing code can
164: lead to out of bounds memory accesses for authorized clients.
165: <br>
166: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/006_xserver.patch.sig">
167: A source code patch exists which remedies this problem.</a>
168: <p>
169:
170: <li id="p007_cron">
171: <strong>007: RELIABILITY FIX: July 24, 2022</strong>
172: <i>All architectures</i>
173: <br>
174: cron(8) aborted due to strange poll timevals.
175: <br>
176: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/007_cron.patch.sig">
177: A source code patch exists which remedies this problem.</a>
178: <p>
179:
1.10 bluhm 180: <li id="p008_bgpd">
181: <strong>008: RELIABILITY FIX: August 2, 2022</strong>
182: <i>All architectures</i>
183: <br>
184: bgpd(8) could fail to invalidate nexthops and incorrectly leave them in
185: the FIB or Adj-RIB-Out.
186: <br>
187: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/008_bgpd.patch.sig">
188: A source code patch exists which remedies this problem.</a>
189: <p>
190:
1.11 bluhm 191: <li id="p009_zlib">
192: <strong>009: SECURITY FIX: August 12, 2022</strong>
193: <i>All architectures</i>
194: <br>
195: A missing length check in zlib could lead to a heap buffer overflow.
196: <br>
197: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/009_zlib.patch.sig">
198: A source code patch exists which remedies this problem.</a>
199: <p>
200:
1.12 bluhm 201: <li id="p010_expat">
202: <strong>010: SECURITY FIX: September 23, 2022</strong>
203: <i>All architectures</i>
204: <br>
205: In libexpat fix heap use-after-free vulnerability CVE-2022-40674.
206: <br>
207: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/010_expat.patch.sig">
208: A source code patch exists which remedies this problem.</a>
209: <p>
210:
1.14 bluhm 211: <li id="p011_smtpd">
212: <strong>011: SECURITY FIX: September 26, 2022</strong>
213: <i>All architectures</i>
214: <br>
215: In smtpd(8), possible use-after-free if TLS handshake fails for
216: outbound connections.
217: <br>
218: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/011_smtpd.patch.sig">
219: A source code patch exists which remedies this problem.</a>
220: <p>
221:
1.16 bluhm 222: <li id="p012_expat">
223: <strong>012: SECURITY FIX: November 1, 2022</strong>
224: <i>All architectures</i>
225: <br>
226: In libexpat fix heap use-after-free vulnerability CVE-2022-43680.
227: <br>
228: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/012_expat.patch.sig">
229: A source code patch exists which remedies this problem.</a>
230: <p>
231:
1.17 bluhm 232: <li id="p013_pixman">
233: <strong>013: SECURITY FIX: November 14, 2022</strong>
234: <i>All architectures</i>
235: <br>
236: CVE-2022-44638: An integer overflow in pixman may lead to an out-of-bounds
237: write.
238: <br>
239: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/013_pixman.patch.sig">
240: A source code patch exists which remedies this problem.</a>
241: <p>
242:
1.18 bluhm 243: <li id="p014_unwind">
244: <strong>014: SECURITY FIX: November 26, 2022</strong>
245: <i>All architectures</i>
246: <br>
247: A crafted TCP query from localhost could crash the unwind(8) daemon.
248: <br>
249: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/014_unwind.patch.sig">
250: A source code patch exists which remedies this problem.</a>
251: <p>
252:
1.19 bluhm 253: <li id="p015_xserver">
254: <strong>015: SECURITY FIX: December 14, 2022</strong>
255: <i>All architectures</i>
256: <br>
257: In X11 server fix local privileges elevation and and remote code
258: execution for ssh X forwarding sessions. This addresses CVE-2022-46340
259: CVE-2022-46341 CVE-2022-46342 CVE-2022-46343 CVE-2022-46344.
260: <br>
261: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/015_xserver.patch.sig">
262: A source code patch exists which remedies this problem.</a>
263: <p>
264:
265: <li id="p016_gpuinv">
266: <strong>016: RELIABILITY FIX: December 14, 2022</strong>
267: <i>amd64 i386</i>
268: <br>
269: TLB entries were not invalidated for all types of engine on
270: 12th generation Intel graphics (Tiger Lake, Rocket Lake, Alder Lake).
271: <br>
272: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/016_gpuinv.patch.sig">
273: A source code patch exists which remedies this problem.</a>
274: <p>
275:
1.20 bluhm 276: <li id="p017_acme">
277: <strong>017: RELIABILITY FIX: December 16, 2022</strong>
278: <i>All architectures</i>
279: <br>
280: Removing a domain can result in an out-of-bounds write in acme-client(8).
281: <br>
282: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/017_acme.patch.sig">
283: A source code patch exists which remedies this problem.</a>
284: <p>
285:
1.21 bluhm 286: <li id="p018_tcp">
287: <strong>018: SECURITY FIX: January 13, 2023</strong>
288: <i>All architectures</i>
289: <br>
290: A TCP packet with destination port 0 that matches a pf divert-to
291: rule could crash the kernel.
292: <br>
293: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/018_tcp.patch.sig">
294: A source code patch exists which remedies this problem.</a>
295: <p>
296:
1.22 bluhm 297: <li id="p019_libxpm">
298: <strong>019: SECURITY FIX: January 17, 2023</strong>
299: <i>All architectures</i>
300: <br>
301: Input validation issues and path validation issues in libXpm can lead
302: to infinite loops, memory corruption or arbitrary command execution.
303: CVE-2022-46285, CVE-2022-44617 and CVE-2022-4883
304: <br>
305: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/019_libxpm.patch.sig">
306: A source code patch exists which remedies this problem.</a>
307: <p>
308:
1.23 bluhm 309: <li id="p020_vmm">
310: <strong>020: SECURITY FIX: January 21, 2023</strong>
1.24 bluhm 311: <i>amd64</i>
1.23 bluhm 312: <br>
313: vmm(4) exposed unsupported cpuid feature flags to guests.
314: <br>
315: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/020_vmm.patch.sig">
316: A source code patch exists which remedies this problem.</a>
317: <p>
318:
319: <li id="p021_vmd">
320: <strong>021: SECURITY FIX: January 21, 2023</strong>
1.24 bluhm 321: <i>amd64</i>
1.23 bluhm 322: <br>
323: vmd(8) exposed unsupported cpuid feature flags to guests.
324: <br>
325: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/021_vmd.patch.sig">
326: A source code patch exists which remedies this problem.</a>
327: <p>
328:
1.25 ! bluhm 329: <li id="p022_x509">
! 330: <strong>022: SECURITY FIX: February 7, 2023</strong>
! 331: <i>All architectures</i>
! 332: <br>
! 333: A malicious certificate revocation list or timestamp response token would
! 334: allow an attacker to read arbitrary memory.
! 335: <br>
! 336: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/022_x509.patch.sig">
! 337: A source code patch exists which remedies this problem.</a>
! 338: <p>
! 339:
! 340: <li id="p023_xserver">
! 341: <strong>023: SECURITY FIX: February 7, 2023</strong>
! 342: <i>All architectures</i>
! 343: <br>
! 344: CVE-2023-0494: use after free in the Xinput X server extension.
! 345: <br>
! 346: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/023_xserver.patch.sig">
! 347: A source code patch exists which remedies this problem.</a>
! 348: <p>
! 349:
! 350: <li id="p024_smtpd">
! 351: <strong>024: SECURITY FIX: February 7, 2023</strong>
! 352: <i>All architectures</i>
! 353: <br>
! 354: smtpd(8) could abort due to a connection from a local, scoped ipv6 address.
! 355: <br>
! 356: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/7.1/common/024_smtpd.patch.sig">
! 357: A source code patch exists which remedies this problem.</a>
! 358: <p>
! 359:
1.1 deraadt 360: </ul>
361:
362: <hr>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata71.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www