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