Annotation of www/errata61.html, Revision 1.38
1.1 tj 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
4: <title>OpenBSD 6.1 Errata</title>
5: <meta name="description" content="the OpenBSD errata page">
6: <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
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: </head>
11:
12: <!--
13: IMPORTANT REMINDER
14: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
15: -->
16: <body bgcolor="#ffffff" text="#000000" link="#23238E">
17:
18: <h2>
19: <a href="index.html">
20: <font color="#0000ff"><i>Open</i></font><font color="#000084">BSD</font></a>
21: <font color="#e00000">6.1 Errata</font>
22: </h2>
23: <hr>
24:
25: For errata on a certain release, click below:<br>
26: <a href="errata21.html">2.1</a>,
27: <a href="errata22.html">2.2</a>,
28: <a href="errata23.html">2.3</a>,
29: <a href="errata24.html">2.4</a>,
30: <a href="errata25.html">2.5</a>,
31: <a href="errata26.html">2.6</a>,
32: <a href="errata27.html">2.7</a>,
33: <a href="errata28.html">2.8</a>,
34: <a href="errata29.html">2.9</a>,
35: <a href="errata30.html">3.0</a>,
36: <a href="errata31.html">3.1</a>,
37: <a href="errata32.html">3.2</a>,
38: <a href="errata33.html">3.3</a>,
39: <a href="errata34.html">3.4</a>,
40: <a href="errata35.html">3.5</a>,
41: <a href="errata36.html">3.6</a>,
42: <br>
43: <a href="errata37.html">3.7</a>,
44: <a href="errata38.html">3.8</a>,
45: <a href="errata39.html">3.9</a>,
46: <a href="errata40.html">4.0</a>,
47: <a href="errata41.html">4.1</a>,
48: <a href="errata42.html">4.2</a>,
49: <a href="errata43.html">4.3</a>,
50: <a href="errata44.html">4.4</a>,
51: <a href="errata45.html">4.5</a>,
52: <a href="errata46.html">4.6</a>,
53: <a href="errata47.html">4.7</a>,
54: <a href="errata48.html">4.8</a>,
55: <a href="errata49.html">4.9</a>,
56: <a href="errata50.html">5.0</a>,
57: <a href="errata51.html">5.1</a>,
58: <a href="errata52.html">5.2</a>,
59: <br>
60: <a href="errata53.html">5.3</a>,
61: <a href="errata54.html">5.4</a>,
62: <a href="errata55.html">5.5</a>,
63: <a href="errata56.html">5.6</a>,
64: <a href="errata57.html">5.7</a>,
65: <a href="errata58.html">5.8</a>,
66: <a href="errata59.html">5.9</a>,
1.23 deraadt 67: <a href="errata60.html">6.0</a>,
1.34 deraadt 68: <a href="errata62.html">6.2</a>,
1.37 deraadt 69: <a href="errata63.html">6.3</a>,
1.38 ! deraadt 70: <a href="errata64.html">6.4</a>,
! 71: <a href="errata65.html">6.5</a>.
1.1 tj 72: <hr>
73:
74: <p>
75: Patches for the OpenBSD base system are distributed as unified diffs.
76: Each patch is cryptographically signed with the
1.15 tb 77: <a href="https://man.openbsd.org/OpenBSD-6.1/signify.1">signify(1)</a> tool and contains
1.1 tj 78: usage instructions.
79: All the following patches are also available in one
80: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1.tar.gz">tar.gz file</a>
81: for convenience.
82:
83: <p>
1.32 tj 84: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
85: utility can be used to apply binary updates on the following architectures:
1.35 tj 86: amd64, i386.
1.32 tj 87:
88: <p>
1.1 tj 89: Patches for supported releases are also incorporated into the
1.35 tj 90: <a href="stable.html">-stable branch</a>.
1.1 tj 91:
92: <hr>
93:
94: <ul>
95:
1.4 tj 96: <li id="p001_dhcpd">
97: <font color="#009000">
98: <strong>001: INTEROPERABILITY FIX: May 2, 2017</strong></font>
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">
109: <font color="#009000">
110: <strong>002: SECURITY FIX: May 2, 2017</strong></font>
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">
120: <font color="#009000">
121: <strong>003: SECURITY FIX: May 2, 2017</strong></font>
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">
132: <font color="#009000">
133: <strong>004: RELIABILITY FIX: May 2, 2017</strong></font>
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">
144: <font color="#009000">
145: <strong>005: RELIABILITY FIX: May 6, 2017</strong></font>
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">
156: <font color="#009000">
157: <strong>006: RELIABILITY FIX: May 8, 2017</strong></font>
158: <i>All architectures</i>
159: <br>
160: Incorrect DTLS cookie handling can result in a NULL pointer dereference.
161: <br>
162: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/006_libssl.patch.sig">
163: A source code patch exists which remedies this problem.</a>
164: <p>
165:
1.9 tj 166: <li id="p007_freetype">
167: <font color="#009000">
1.10 tj 168: <strong>007: SECURITY FIX: May 13, 2017</strong></font>
1.9 tj 169: <i>All architectures</i>
170: <br>
171: Heap-based buffer overflows in freetype can result in out-of-bounds writes.
172: <br>
173: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/007_freetype.patch.sig">
174: A source code patch exists which remedies this problem.</a>
175: <p>
176:
1.11 tj 177: <li id="p008_exec_subr">
178: <font color="#009000">
179: <strong>008: SECURITY FIX: May 19, 2017</strong></font>
180: <i>All architectures</i>
181: <br>
182: An additional mitigation is added by placing a gap of 1 MB between the
183: stack and mmap spaces.
184: <br>
185: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/008_exec_subr.patch.sig">
186: A source code patch exists which remedies this problem.</a>
187: <p>
188:
1.12 tj 189: <li id="p009_icmp_opts">
190: <font color="#009000">
191: <strong>009: RELIABILITY FIX: May 22, 2017</strong></font>
192: <i>All architectures</i>
193: <br>
1.14 tj 194: The kernel could leak memory when processing ICMP packets with IP options.
1.12 tj 195: Note that pf blocks such packets by default.
196: <br>
197: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/009_icmp_opts.patch.sig">
198: A source code patch exists which remedies this problem.</a>
199: <p>
200:
1.13 tj 201: <li id="p010_perl">
202: <font color="#009000">
203: <strong>010: SECURITY FIX: June 4, 2017</strong></font>
204: <i>All architectures</i>
205: <br>
206: A race condition exists in the File::Path perl module.
207: <br>
208: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/010_perl.patch.sig">
1.14 tj 209: A source code patch exists which remedies this problem.</a>
210: <p>
211:
212: <li id="p011_sti">
213: <font color="#009000">
214: <strong>011: SECURITY FIX: June 12, 2017</strong></font>
215: <i>hppa</i>
216: <br>
217: An integer overflow exists in two range checks of the sti(4) display driver.
218: <br>
219: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/011_sti.patch.sig">
220: A source code patch exists which remedies this problem.</a>
221: <p>
222:
223: <li id="p012_wsmux">
224: <font color="#009000">
225: <strong>012: RELIABILITY FIX: June 12, 2017</strong></font>
226: <i>All architectures</i>
227: <br>
228: An unprivileged user can cause a kernel crash.
229: <br>
230: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/012_wsmux.patch.sig">
1.13 tj 231: A source code patch exists which remedies this problem.</a>
232: <p>
233:
1.16 tj 234: <li id="p013_icmp6_linklocal">
235: <font color="#009000">
236: <strong>013: RELIABILITY FIX: June 27, 2017</strong></font>
237: <i>All architectures</i>
238: <br>
239: When pinging an IPv6 link-local address, the reflected packet had
240: ::1 as source address. The echo reply was ignored as it must be
241: from the link-local address.
242: <br>
243: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/013_icmp6_linklocal.patch.sig">
244: A source code patch exists which remedies this problem.</a>
245: <p>
246:
1.17 tj 247: <li id="p014_libcrypto">
248: <font color="#009000">
249: <strong>014: RELIABILITY FIX: July 5, 2017</strong></font>
250: <i>All architectures</i>
251: <br>
252: Self-issued certificates are improperly treated as self-signed certificates,
253: leading to possible verification failures.
254: <br>
255: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/014_libcrypto.patch.sig">
256: A source code patch exists which remedies this problem.</a>
257: <p>
258:
1.18 tj 259: <li id="p015_sigio">
260: <font color="#009000">
261: <strong>015: RELIABILITY FIX: August 3, 2017</strong></font>
262: <i>All architectures</i>
263: <br>
264: A SIGIO-related use-after-free can occur in two drivers.
265: <br>
266: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/015_sigio.patch.sig">
267: A source code patch exists which remedies this problem.</a>
268: <p>
269:
270: <li id="p016_sendsyslog">
271: <font color="#009000">
272: <strong>016: RELIABILITY FIX: August 3, 2017</strong></font>
273: <i>All architectures</i>
274: <br>
275: A missing length check in sendsyslog() may result in a kernel panic.
276: <br>
277: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/016_sendsyslog.patch.sig">
278: A source code patch exists which remedies this problem.</a>
279: <p>
280:
281: <li id="p017_fuse">
282: <font color="#009000">
283: <strong>017: SECURITY FIX: August 3, 2017</strong></font>
284: <i>All architectures</i>
285: <br>
286: An out-of-bound read in vfs_getcwd_scandir() (mainly used for FUSE)
287: may result in a kernel panic or info leak.
288: <br>
289: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/017_fuse.patch.sig">
290: A source code patch exists which remedies this problem.</a>
291: <p>
292:
293: <li id="p018_recv">
294: <font color="#009000">
295: <strong>018: SECURITY FIX: August 3, 2017</strong></font>
296: <i>All architectures</i>
297: <br>
298: An alignment issue in recv() may result in an info leak via ktrace().
299: <br>
300: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/018_recv.patch.sig">
301: A source code patch exists which remedies this problem.</a>
302: <p>
303:
304: <li id="p019_tcp_usrreq">
305: <font color="#009000">
306: <strong>019: SECURITY FIX: August 3, 2017</strong></font>
307: <i>All architectures</i>
308: <br>
309: With an invalid address family, tcp_usrreq() may take an unintended code path.
310: <br>
311: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/019_tcp_usrreq.patch.sig">
312: A source code patch exists which remedies this problem.</a>
313: <p>
314:
315: <li id="p020_sockaddr">
316: <font color="#009000">
317: <strong>020: SECURITY FIX: August 3, 2017</strong></font>
318: <i>All architectures</i>
319: <br>
320: Missing socket address validation from userland may result in an info leak.
321: <br>
322: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/020_sockaddr.patch.sig">
323: A source code patch exists which remedies this problem.</a>
324: <p>
325:
326: <li id="p021_ptrace">
327: <font color="#009000">
328: <strong>021: SECURITY FIX: August 3, 2017</strong></font>
329: <i>All architectures</i>
330: <br>
331: An uninitialized variable in ptrace() may result in an info leak.
332: <br>
333: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/021_ptrace.patch.sig">
334: A source code patch exists which remedies this problem.</a>
335: <p>
336:
337: <li id="p022_fcntl">
338: <font color="#009000">
339: <strong>022: SECURITY FIX: August 3, 2017</strong></font>
340: <i>All architectures</i>
341: <br>
342: An uninitialized variable in fcntl() may result in an info leak.
343: <br>
344: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/022_fcntl.patch.sig">
345: A source code patch exists which remedies this problem.</a>
346: <p>
347:
348: <li id="p023_wsdisplay">
349: <font color="#009000">
350: <strong>023: RELIABILITY FIX: August 3, 2017</strong></font>
351: <i>All architectures</i>
352: <br>
353: An integer overflow in wsdisplay_cfg_ioctl() may result in an out-of-bounds
354: read.
355: <br>
356: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/023_wsdisplay.patch.sig">
357: A source code patch exists which remedies this problem.</a>
358: <p>
359:
360: <li id="p024_sosplice">
361: <font color="#009000">
362: <strong>024: SECURITY FIX: August 3, 2017</strong></font>
363: <i>All architectures</i>
364: <br>
365: A race condition in sosplice() may result in a kernel memory leak.
366: <br>
367: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/024_sosplice.patch.sig">
368: A source code patch exists which remedies this problem.</a>
369: <p>
370:
371: <li id="p025_ieee80211">
372: <font color="#009000">
373: <strong>025: SECURITY FIX: August 3, 2017</strong></font>
374: <i>All architectures</i>
375: <br>
376: An out of bounds read could occur during processing of EAPOL frames in
377: the wireless stack. Information from kernel memory could be leaked to
378: root in userland via an ieee80211(9) ioctl.
379: <br>
380: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/025_ieee80211.patch.sig">
381: A source code patch exists which remedies this problem.</a>
382: <p>
383:
1.19 tj 384: <li id="p026_smap">
385: <font color="#009000">
386: <strong>026: SECURITY FIX: August 26, 2017</strong></font>
387: <i>amd64 and i386</i>
388: <br>
389: SMAP enforcement could be bypassed by userland code.
390: <br>
391: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/026_smap.patch.sig">
392: A source code patch exists which remedies this problem.</a>
393: <p>
394:
1.20 tj 395: <li id="p027_net80211_replay">
396: <font color="#009000">
397: <strong>027: SECURITY FIX: August 30, 2017</strong></font>
398: <i>All architectures</i>
399: <br>
400: State transition errors could cause reinstallation of old WPA keys.
401: <br>
402: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/027_net80211_replay.patch.sig">
403: A source code patch exists which remedies this problem.</a>
404: <p>
405:
1.21 tj 406: <li id="p028_perl">
407: <font color="#009000">
408: <strong>028: SECURITY FIX: September 22, 2017</strong></font>
409: <i>All architectures</i>
410: <br>
411: A buffer over-read and heap overflow in perl's regexp may result in
412: a crash or memory leak.
413: <br>
414: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/028_perl.patch.sig">
415: A source code patch exists which remedies this problem.</a>
416: <p>
417:
1.22 tj 418: <li id="p029_tcb">
419: <font color="#009000">
420: <strong>029: RELIABILITY FIX: September 27, 2017</strong></font>
421: <i>amd64</i>
422: <br>
423: Out of bounds TCB settings may result in a kernel panic.
424: <br>
425: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/029_tcb.patch.sig">
426: A source code patch exists which remedies this problem.</a>
427: <p>
428:
1.24 tj 429: <li id="p030_xrstor">
430: <font color="#009000">
431: <strong>030: RELIABILITY FIX: October 4, 2017</strong></font>
432: <i>amd64</i>
433: <br>
434: An unprivileged user can cause a kernel crash.
435: <br>
436: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/030_xrstor.patch.sig">
437: A source code patch exists which remedies this problem.</a>
438: <p>
439:
1.25 tj 440: <li id="p031_xrstor_resume">
441: <font color="#009000">
442: <strong>031: SECURITY FIX: October 4, 2017</strong></font>
443: <i>amd64</i>
444: <br>
445: A kernel executable address was leaked to userland.
446: <br>
1.26 tj 447: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/031_xrstor_resume.patch.sig">
1.25 tj 448: A source code patch exists which remedies this problem.</a>
449: <p>
450:
1.27 bluhm 451: <li id="p032_tcb_invalid">
452: <font color="#009000">
453: <strong>032: RELIABILITY FIX: October 13, 2017</strong></font>
454: <i>amd64</i>
455: <br>
456: A local user could trigger a kernel panic by using an invalid TCB value.
457: <br>
458: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/032_tcb_invalid.patch.sig">
459: A source code patch exists which remedies this problem.</a>
460: <p>
461:
1.29 tj 462: <li id="p033_mpls">
463: <font color="#009000">
464: <strong>033: RELIABILITY FIX: December 10, 2017</strong></font>
465: All architectures
466: <br>
467: A number of bugs were discovered in the MPLS stack that can be used to
468: remotely trigger a kernel panic.
469: <br>
470: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/033_mpls.patch.sig">
471: A source code patch exists which remedies this problem.</a>
472: <p>
473:
1.30 tj 474: <li id="p034_ahopts">
475: <font color="#009000">
476: <strong>034: RELIABILITY FIX: February 2, 2018</strong></font>
477: <i>All architectures</i>
478: <br>
479: Specially crafted IPsec AH packets with IP options or IPv6 extension
480: headers could crash or hang the kernel.
481: <br>
482: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/034_ahopts.patch.sig">
483: A source code patch exists which remedies this problem.</a>
484: <p>
485:
486: <li id="p035_prevhdr">
487: <font color="#009000">
488: <strong>035: RELIABILITY FIX: February 2, 2018</strong></font>
489: <i>All architectures</i>
490: <br>
491: Processing IPv6 fragments could incorrectly access memory of an mbuf
492: chain that is not within an mbuf. This may crash the kernel.
493: <br>
494: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/035_prevhdr.patch.sig">
495: A source code patch exists which remedies this problem.</a>
496: <p>
497:
498: <li id="p036_etherip">
499: <font color="#009000">
500: <strong>036: SECURITY FIX: February 2, 2018</strong></font>
501: <i>All architectures</i>
502: <br>
503: If the EtherIP tunnel protocol was disabled, IPv6 packets were not
504: discarded properly. This causes a double free in the kernel.
505: <br>
506: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/036_etherip.patch.sig">
507: A source code patch exists which remedies this problem.</a>
508: <p>
509:
1.31 tj 510: <li id="p037_meltdown">
511: <font color="#009000">
512: <strong>037: SECURITY FIX: March 1, 2018</strong></font>
513: <i>amd64</i>
514: <br>
515: Intel CPUs contain a speculative execution flaw called Meltdown which
516: allows userspace programs to access kernel memory.
517: <br>
518: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/037_meltdown.patch.sig">
519: A complex workaround solves the problem.</a>
520: <p>
521:
1.33 tj 522: <li id="p038_ahauth">
523: <font color="#009000">
524: <strong>038: RELIABILITY FIX: March 20, 2018</strong></font>
525: <i>All architectures</i>
526: <br>
527: The IPsec AH header could be longer than the network packet, resulting in
528: a kernel crash.
529: <br>
530: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/038_ahauth.patch.sig">
531: A source code patch exists which remedies this problem.</a>
532: <p>
533:
1.36 afresh1 534: <li id="p039_perl">
535: <font color="#009000">
536: <strong>039: SECURITY FIX: April 14, 2018</strong></font>
537: <i>All architectures</i>
538: <br>
539: Heap overflows exist in perl which can lead to segmentation faults,
540: crashes, and reading memory past the buffer.
541: <br>
542: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/039_perl.patch.sig">
543: A source code patch exists which remedies this problem.</a>
544: <p>
545:
1.1 tj 546: </ul>
547:
548: <hr>
549:
550: </body>
551: </html>
![[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