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