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