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