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