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