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