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