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