Annotation of www/errata61.html, Revision 1.41
1.39 bentley 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
1.1 tj 5: <title>OpenBSD 6.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/errata61.html">
10:
11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
15:
1.39 bentley 16: <h2 id=OpenBSD>
1.1 tj 17: <a href="index.html">
1.39 bentley 18: <i>Open</i><b>BSD</b></a>
19: 6.1 Errata
1.1 tj 20: </h2>
21: <hr>
22:
23: For errata on a certain release, click below:<br>
1.41 ! schwarze 24: <a href="errata20.html">2.0</a>,
1.1 tj 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>,
1.41 ! schwarze 40: <br>
1.1 tj 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>,
1.41 ! schwarze 57: <br>
1.1 tj 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>,
1.23 deraadt 66: <a href="errata60.html">6.0</a>,
1.34 deraadt 67: <a href="errata62.html">6.2</a>,
1.37 deraadt 68: <a href="errata63.html">6.3</a>,
1.38 deraadt 69: <a href="errata64.html">6.4</a>,
1.40 deraadt 70: <a href="errata65.html">6.5</a>,
71: <a href="errata66.html">6.6</a>.
1.1 tj 72: <hr>
73:
74: <p>
75: Patches for the OpenBSD base system are distributed as unified diffs.
76: Each patch is cryptographically signed with the
1.15 tb 77: <a href="https://man.openbsd.org/OpenBSD-6.1/signify.1">signify(1)</a> tool and contains
1.1 tj 78: usage instructions.
79: All the following patches are also available in one
80: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1.tar.gz">tar.gz file</a>
81: for convenience.
82:
83: <p>
1.32 tj 84: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
85: utility can be used to apply binary updates on the following architectures:
1.35 tj 86: amd64, i386.
1.32 tj 87:
88: <p>
1.1 tj 89: Patches for supported releases are also incorporated into the
1.35 tj 90: <a href="stable.html">-stable branch</a>.
1.1 tj 91:
92: <hr>
93:
94: <ul>
95:
1.4 tj 96: <li id="p001_dhcpd">
1.39 bentley 97: <strong>001: INTEROPERABILITY FIX: May 2, 2017</strong>
1.4 tj 98: <i>All architectures</i>
99: <br>
100: dhcpd unconditionally echoed the client identifier, preventing some devices
1.5 tb 101: from acquiring a lease.
1.4 tj 102: <br>
103: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/001_dhcpd.patch.sig">
104: A source code patch exists which remedies this problem.</a>
105: <p>
106:
107: <li id="p002_vmmfpu">
1.39 bentley 108: <strong>002: SECURITY FIX: May 2, 2017</strong>
1.6 mlarkin 109: <i>amd64</i>
1.4 tj 110: <br>
111: vmm mismanaged floating point contexts.
112: <br>
113: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/002_vmmfpu.patch.sig">
114: A source code patch exists which remedies this problem.</a>
115: <p>
116:
117: <li id="p003_libressl">
1.39 bentley 118: <strong>003: SECURITY FIX: May 2, 2017</strong>
1.4 tj 119: <i>All architectures</i>
120: <br>
121: A consistency check error could cause programs to incorrectly verify
122: TLS certificates when using callbacks that always return 1.
123: <br>
124: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/003_libressl.patch.sig">
125: A source code patch exists which remedies this problem.</a>
126: <p>
127:
128: <li id="p004_softraid_concat">
1.39 bentley 129: <strong>004: RELIABILITY FIX: May 2, 2017</strong>
1.4 tj 130: <i>All architectures</i>
131: <br>
132: softraid was unable to create usable concat volumes because
133: it always set the size of the volume to zero sectors.
134: <br>
135: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/004_softraid_concat.patch.sig">
136: A source code patch exists which remedies this problem.</a>
137: <p>
1.1 tj 138:
1.7 tj 139: <li id="p005_pf_src_tracking">
1.39 bentley 140: <strong>005: RELIABILITY FIX: May 6, 2017</strong>
1.7 tj 141: <i>All architectures</i>
142: <br>
143: Expired pf source tracking entries never got removed, leading to
144: memory exhaustion.
145: <br>
146: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/005_pf_src_tracking.patch.sig">
147: A source code patch exists which remedies this problem.</a>
148: <p>
149:
1.8 tj 150: <li id="p006_libssl">
1.39 bentley 151: <strong>006: RELIABILITY FIX: May 8, 2017</strong>
1.8 tj 152: <i>All architectures</i>
153: <br>
154: Incorrect DTLS cookie handling can result in a NULL pointer dereference.
155: <br>
156: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/006_libssl.patch.sig">
157: A source code patch exists which remedies this problem.</a>
158: <p>
159:
1.9 tj 160: <li id="p007_freetype">
1.39 bentley 161: <strong>007: SECURITY FIX: May 13, 2017</strong>
1.9 tj 162: <i>All architectures</i>
163: <br>
164: Heap-based buffer overflows in freetype can result in out-of-bounds writes.
165: <br>
166: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/007_freetype.patch.sig">
167: A source code patch exists which remedies this problem.</a>
168: <p>
169:
1.11 tj 170: <li id="p008_exec_subr">
1.39 bentley 171: <strong>008: SECURITY FIX: May 19, 2017</strong>
1.11 tj 172: <i>All architectures</i>
173: <br>
174: An additional mitigation is added by placing a gap of 1 MB between the
175: stack and mmap spaces.
176: <br>
177: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/008_exec_subr.patch.sig">
178: A source code patch exists which remedies this problem.</a>
179: <p>
180:
1.12 tj 181: <li id="p009_icmp_opts">
1.39 bentley 182: <strong>009: RELIABILITY FIX: May 22, 2017</strong>
1.12 tj 183: <i>All architectures</i>
184: <br>
1.14 tj 185: The kernel could leak memory when processing ICMP packets with IP options.
1.12 tj 186: Note that pf blocks such packets by default.
187: <br>
188: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/009_icmp_opts.patch.sig">
189: A source code patch exists which remedies this problem.</a>
190: <p>
191:
1.13 tj 192: <li id="p010_perl">
1.39 bentley 193: <strong>010: SECURITY FIX: June 4, 2017</strong>
1.13 tj 194: <i>All architectures</i>
195: <br>
196: A race condition exists in the File::Path perl module.
197: <br>
198: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/010_perl.patch.sig">
1.14 tj 199: A source code patch exists which remedies this problem.</a>
200: <p>
201:
202: <li id="p011_sti">
1.39 bentley 203: <strong>011: SECURITY FIX: June 12, 2017</strong>
1.14 tj 204: <i>hppa</i>
205: <br>
206: An integer overflow exists in two range checks of the sti(4) display driver.
207: <br>
208: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/011_sti.patch.sig">
209: A source code patch exists which remedies this problem.</a>
210: <p>
211:
212: <li id="p012_wsmux">
1.39 bentley 213: <strong>012: RELIABILITY FIX: June 12, 2017</strong>
1.14 tj 214: <i>All architectures</i>
215: <br>
216: An unprivileged user can cause a kernel crash.
217: <br>
218: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/012_wsmux.patch.sig">
1.13 tj 219: A source code patch exists which remedies this problem.</a>
220: <p>
221:
1.16 tj 222: <li id="p013_icmp6_linklocal">
1.39 bentley 223: <strong>013: RELIABILITY FIX: June 27, 2017</strong>
1.16 tj 224: <i>All architectures</i>
225: <br>
226: When pinging an IPv6 link-local address, the reflected packet had
227: ::1 as source address. The echo reply was ignored as it must be
228: from the link-local address.
229: <br>
230: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/013_icmp6_linklocal.patch.sig">
231: A source code patch exists which remedies this problem.</a>
232: <p>
233:
1.17 tj 234: <li id="p014_libcrypto">
1.39 bentley 235: <strong>014: RELIABILITY FIX: July 5, 2017</strong>
1.17 tj 236: <i>All architectures</i>
237: <br>
238: Self-issued certificates are improperly treated as self-signed certificates,
239: leading to possible verification failures.
240: <br>
241: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/014_libcrypto.patch.sig">
242: A source code patch exists which remedies this problem.</a>
243: <p>
244:
1.18 tj 245: <li id="p015_sigio">
1.39 bentley 246: <strong>015: RELIABILITY FIX: August 3, 2017</strong>
1.18 tj 247: <i>All architectures</i>
248: <br>
249: A SIGIO-related use-after-free can occur in two drivers.
250: <br>
251: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/015_sigio.patch.sig">
252: A source code patch exists which remedies this problem.</a>
253: <p>
254:
255: <li id="p016_sendsyslog">
1.39 bentley 256: <strong>016: RELIABILITY FIX: August 3, 2017</strong>
1.18 tj 257: <i>All architectures</i>
258: <br>
259: A missing length check in sendsyslog() may result in a kernel panic.
260: <br>
261: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/016_sendsyslog.patch.sig">
262: A source code patch exists which remedies this problem.</a>
263: <p>
264:
265: <li id="p017_fuse">
1.39 bentley 266: <strong>017: SECURITY FIX: August 3, 2017</strong>
1.18 tj 267: <i>All architectures</i>
268: <br>
269: An out-of-bound read in vfs_getcwd_scandir() (mainly used for FUSE)
270: may result in a kernel panic or info leak.
271: <br>
272: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/017_fuse.patch.sig">
273: A source code patch exists which remedies this problem.</a>
274: <p>
275:
276: <li id="p018_recv">
1.39 bentley 277: <strong>018: SECURITY FIX: August 3, 2017</strong>
1.18 tj 278: <i>All architectures</i>
279: <br>
280: An alignment issue in recv() may result in an info leak via ktrace().
281: <br>
282: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/018_recv.patch.sig">
283: A source code patch exists which remedies this problem.</a>
284: <p>
285:
286: <li id="p019_tcp_usrreq">
1.39 bentley 287: <strong>019: SECURITY FIX: August 3, 2017</strong>
1.18 tj 288: <i>All architectures</i>
289: <br>
290: With an invalid address family, tcp_usrreq() may take an unintended code path.
291: <br>
292: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/019_tcp_usrreq.patch.sig">
293: A source code patch exists which remedies this problem.</a>
294: <p>
295:
296: <li id="p020_sockaddr">
1.39 bentley 297: <strong>020: SECURITY FIX: August 3, 2017</strong>
1.18 tj 298: <i>All architectures</i>
299: <br>
300: Missing socket address validation from userland may result in an info leak.
301: <br>
302: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/020_sockaddr.patch.sig">
303: A source code patch exists which remedies this problem.</a>
304: <p>
305:
306: <li id="p021_ptrace">
1.39 bentley 307: <strong>021: SECURITY FIX: August 3, 2017</strong>
1.18 tj 308: <i>All architectures</i>
309: <br>
310: An uninitialized variable in ptrace() may result in an info leak.
311: <br>
312: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/021_ptrace.patch.sig">
313: A source code patch exists which remedies this problem.</a>
314: <p>
315:
316: <li id="p022_fcntl">
1.39 bentley 317: <strong>022: SECURITY FIX: August 3, 2017</strong>
1.18 tj 318: <i>All architectures</i>
319: <br>
320: An uninitialized variable in fcntl() may result in an info leak.
321: <br>
322: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/022_fcntl.patch.sig">
323: A source code patch exists which remedies this problem.</a>
324: <p>
325:
326: <li id="p023_wsdisplay">
1.39 bentley 327: <strong>023: RELIABILITY FIX: August 3, 2017</strong>
1.18 tj 328: <i>All architectures</i>
329: <br>
330: An integer overflow in wsdisplay_cfg_ioctl() may result in an out-of-bounds
331: read.
332: <br>
333: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/023_wsdisplay.patch.sig">
334: A source code patch exists which remedies this problem.</a>
335: <p>
336:
337: <li id="p024_sosplice">
1.39 bentley 338: <strong>024: SECURITY FIX: August 3, 2017</strong>
1.18 tj 339: <i>All architectures</i>
340: <br>
341: A race condition in sosplice() may result in a kernel memory leak.
342: <br>
343: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/024_sosplice.patch.sig">
344: A source code patch exists which remedies this problem.</a>
345: <p>
346:
347: <li id="p025_ieee80211">
1.39 bentley 348: <strong>025: SECURITY FIX: August 3, 2017</strong>
1.18 tj 349: <i>All architectures</i>
350: <br>
351: An out of bounds read could occur during processing of EAPOL frames in
352: the wireless stack. Information from kernel memory could be leaked to
353: root in userland via an ieee80211(9) ioctl.
354: <br>
355: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/025_ieee80211.patch.sig">
356: A source code patch exists which remedies this problem.</a>
357: <p>
358:
1.19 tj 359: <li id="p026_smap">
1.39 bentley 360: <strong>026: SECURITY FIX: August 26, 2017</strong>
1.19 tj 361: <i>amd64 and i386</i>
362: <br>
363: SMAP enforcement could be bypassed by userland code.
364: <br>
365: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/026_smap.patch.sig">
366: A source code patch exists which remedies this problem.</a>
367: <p>
368:
1.20 tj 369: <li id="p027_net80211_replay">
1.39 bentley 370: <strong>027: SECURITY FIX: August 30, 2017</strong>
1.20 tj 371: <i>All architectures</i>
372: <br>
373: State transition errors could cause reinstallation of old WPA keys.
374: <br>
375: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/027_net80211_replay.patch.sig">
376: A source code patch exists which remedies this problem.</a>
377: <p>
378:
1.21 tj 379: <li id="p028_perl">
1.39 bentley 380: <strong>028: SECURITY FIX: September 22, 2017</strong>
1.21 tj 381: <i>All architectures</i>
382: <br>
383: A buffer over-read and heap overflow in perl's regexp may result in
384: a crash or memory leak.
385: <br>
386: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/028_perl.patch.sig">
387: A source code patch exists which remedies this problem.</a>
388: <p>
389:
1.22 tj 390: <li id="p029_tcb">
1.39 bentley 391: <strong>029: RELIABILITY FIX: September 27, 2017</strong>
1.22 tj 392: <i>amd64</i>
393: <br>
394: Out of bounds TCB settings may result in a kernel panic.
395: <br>
396: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/029_tcb.patch.sig">
397: A source code patch exists which remedies this problem.</a>
398: <p>
399:
1.24 tj 400: <li id="p030_xrstor">
1.39 bentley 401: <strong>030: RELIABILITY FIX: October 4, 2017</strong>
1.24 tj 402: <i>amd64</i>
403: <br>
404: An unprivileged user can cause a kernel crash.
405: <br>
406: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/030_xrstor.patch.sig">
407: A source code patch exists which remedies this problem.</a>
408: <p>
409:
1.25 tj 410: <li id="p031_xrstor_resume">
1.39 bentley 411: <strong>031: SECURITY FIX: October 4, 2017</strong>
1.25 tj 412: <i>amd64</i>
413: <br>
414: A kernel executable address was leaked to userland.
415: <br>
1.26 tj 416: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/031_xrstor_resume.patch.sig">
1.25 tj 417: A source code patch exists which remedies this problem.</a>
418: <p>
419:
1.27 bluhm 420: <li id="p032_tcb_invalid">
1.39 bentley 421: <strong>032: RELIABILITY FIX: October 13, 2017</strong>
1.27 bluhm 422: <i>amd64</i>
423: <br>
424: A local user could trigger a kernel panic by using an invalid TCB value.
425: <br>
426: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/032_tcb_invalid.patch.sig">
427: A source code patch exists which remedies this problem.</a>
428: <p>
429:
1.29 tj 430: <li id="p033_mpls">
1.39 bentley 431: <strong>033: RELIABILITY FIX: December 10, 2017</strong>
1.29 tj 432: All architectures
433: <br>
434: A number of bugs were discovered in the MPLS stack that can be used to
435: remotely trigger a kernel panic.
436: <br>
437: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/033_mpls.patch.sig">
438: A source code patch exists which remedies this problem.</a>
439: <p>
440:
1.30 tj 441: <li id="p034_ahopts">
1.39 bentley 442: <strong>034: RELIABILITY FIX: February 2, 2018</strong>
1.30 tj 443: <i>All architectures</i>
444: <br>
445: Specially crafted IPsec AH packets with IP options or IPv6 extension
446: headers could crash or hang the kernel.
447: <br>
448: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/034_ahopts.patch.sig">
449: A source code patch exists which remedies this problem.</a>
450: <p>
451:
452: <li id="p035_prevhdr">
1.39 bentley 453: <strong>035: RELIABILITY FIX: February 2, 2018</strong>
1.30 tj 454: <i>All architectures</i>
455: <br>
456: Processing IPv6 fragments could incorrectly access memory of an mbuf
457: chain that is not within an mbuf. This may crash the kernel.
458: <br>
459: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/035_prevhdr.patch.sig">
460: A source code patch exists which remedies this problem.</a>
461: <p>
462:
463: <li id="p036_etherip">
1.39 bentley 464: <strong>036: SECURITY FIX: February 2, 2018</strong>
1.30 tj 465: <i>All architectures</i>
466: <br>
467: If the EtherIP tunnel protocol was disabled, IPv6 packets were not
468: discarded properly. This causes a double free in the kernel.
469: <br>
470: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/036_etherip.patch.sig">
471: A source code patch exists which remedies this problem.</a>
472: <p>
473:
1.31 tj 474: <li id="p037_meltdown">
1.39 bentley 475: <strong>037: SECURITY FIX: March 1, 2018</strong>
1.31 tj 476: <i>amd64</i>
477: <br>
478: Intel CPUs contain a speculative execution flaw called Meltdown which
479: allows userspace programs to access kernel memory.
480: <br>
481: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/037_meltdown.patch.sig">
482: A complex workaround solves the problem.</a>
483: <p>
484:
1.33 tj 485: <li id="p038_ahauth">
1.39 bentley 486: <strong>038: RELIABILITY FIX: March 20, 2018</strong>
1.33 tj 487: <i>All architectures</i>
488: <br>
489: The IPsec AH header could be longer than the network packet, resulting in
490: a kernel crash.
491: <br>
492: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/038_ahauth.patch.sig">
493: A source code patch exists which remedies this problem.</a>
494: <p>
495:
1.36 afresh1 496: <li id="p039_perl">
1.39 bentley 497: <strong>039: SECURITY FIX: April 14, 2018</strong>
1.36 afresh1 498: <i>All architectures</i>
499: <br>
500: Heap overflows exist in perl which can lead to segmentation faults,
501: crashes, and reading memory past the buffer.
502: <br>
503: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/039_perl.patch.sig">
504: A source code patch exists which remedies this problem.</a>
505: <p>
506:
1.1 tj 507: </ul>
508:
509: <hr>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata61.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www