Annotation of www/errata61.html, Revision 1.22
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>,
67: <a href="errata60.html">6.0</a>.
68: <hr>
69:
70: <p>
71: Patches for the OpenBSD base system are distributed as unified diffs.
72: Each patch is cryptographically signed with the
1.15 tb 73: <a href="https://man.openbsd.org/OpenBSD-6.1/signify.1">signify(1)</a> tool and contains
1.1 tj 74: usage instructions.
75: All the following patches are also available in one
76: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1.tar.gz">tar.gz file</a>
77: for convenience.
78:
79: <p>
1.15 tb 80: Alternatively, the <a href="https://man.openbsd.org/syspatch">syspatch(8)</a>
1.1 tj 81: utility can be used to apply binary updates on the following architectures:
1.3 tj 82: amd64, i386.
1.1 tj 83:
84: <p>
85: Patches for supported releases are also incorporated into the
86: <a href="stable.html">-stable branch</a>, which is maintained for one year
87: after release.
88:
89: <hr>
90:
91: <ul>
92:
1.4 tj 93: <li id="p001_dhcpd">
94: <font color="#009000">
95: <strong>001: INTEROPERABILITY FIX: May 2, 2017</strong></font>
96: <i>All architectures</i>
97: <br>
98: dhcpd unconditionally echoed the client identifier, preventing some devices
1.5 tb 99: from acquiring a lease.
1.4 tj 100: <br>
101: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/001_dhcpd.patch.sig">
102: A source code patch exists which remedies this problem.</a>
103: <p>
104:
105: <li id="p002_vmmfpu">
106: <font color="#009000">
107: <strong>002: SECURITY FIX: May 2, 2017</strong></font>
1.6 mlarkin 108: <i>amd64</i>
1.4 tj 109: <br>
110: vmm mismanaged floating point contexts.
111: <br>
112: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/002_vmmfpu.patch.sig">
113: A source code patch exists which remedies this problem.</a>
114: <p>
115:
116: <li id="p003_libressl">
117: <font color="#009000">
118: <strong>003: SECURITY FIX: May 2, 2017</strong></font>
119: <i>All architectures</i>
120: <br>
121: A consistency check error could cause programs to incorrectly verify
122: TLS certificates when using callbacks that always return 1.
123: <br>
124: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/003_libressl.patch.sig">
125: A source code patch exists which remedies this problem.</a>
126: <p>
127:
128: <li id="p004_softraid_concat">
129: <font color="#009000">
130: <strong>004: RELIABILITY FIX: May 2, 2017</strong></font>
131: <i>All architectures</i>
132: <br>
133: softraid was unable to create usable concat volumes because
134: it always set the size of the volume to zero sectors.
135: <br>
136: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/004_softraid_concat.patch.sig">
137: A source code patch exists which remedies this problem.</a>
138: <p>
1.1 tj 139:
1.7 tj 140: <li id="p005_pf_src_tracking">
141: <font color="#009000">
142: <strong>005: RELIABILITY FIX: May 6, 2017</strong></font>
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">
153: <font color="#009000">
154: <strong>006: RELIABILITY FIX: May 8, 2017</strong></font>
155: <i>All architectures</i>
156: <br>
157: Incorrect DTLS cookie handling can result in a NULL pointer dereference.
158: <br>
159: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/006_libssl.patch.sig">
160: A source code patch exists which remedies this problem.</a>
161: <p>
162:
1.9 tj 163: <li id="p007_freetype">
164: <font color="#009000">
1.10 tj 165: <strong>007: SECURITY FIX: May 13, 2017</strong></font>
1.9 tj 166: <i>All architectures</i>
167: <br>
168: Heap-based buffer overflows in freetype can result in out-of-bounds writes.
169: <br>
170: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/007_freetype.patch.sig">
171: A source code patch exists which remedies this problem.</a>
172: <p>
173:
1.11 tj 174: <li id="p008_exec_subr">
175: <font color="#009000">
176: <strong>008: SECURITY FIX: May 19, 2017</strong></font>
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">
187: <font color="#009000">
188: <strong>009: RELIABILITY FIX: May 22, 2017</strong></font>
189: <i>All architectures</i>
190: <br>
1.14 tj 191: The kernel could leak memory when processing ICMP packets with IP options.
1.12 tj 192: Note that pf blocks such packets by default.
193: <br>
194: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/009_icmp_opts.patch.sig">
195: A source code patch exists which remedies this problem.</a>
196: <p>
197:
1.13 tj 198: <li id="p010_perl">
199: <font color="#009000">
200: <strong>010: SECURITY FIX: June 4, 2017</strong></font>
201: <i>All architectures</i>
202: <br>
203: A race condition exists in the File::Path perl module.
204: <br>
205: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/010_perl.patch.sig">
1.14 tj 206: A source code patch exists which remedies this problem.</a>
207: <p>
208:
209: <li id="p011_sti">
210: <font color="#009000">
211: <strong>011: SECURITY FIX: June 12, 2017</strong></font>
212: <i>hppa</i>
213: <br>
214: An integer overflow exists in two range checks of the sti(4) display driver.
215: <br>
216: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/011_sti.patch.sig">
217: A source code patch exists which remedies this problem.</a>
218: <p>
219:
220: <li id="p012_wsmux">
221: <font color="#009000">
222: <strong>012: RELIABILITY FIX: June 12, 2017</strong></font>
223: <i>All architectures</i>
224: <br>
225: An unprivileged user can cause a kernel crash.
226: <br>
227: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/012_wsmux.patch.sig">
1.13 tj 228: A source code patch exists which remedies this problem.</a>
229: <p>
230:
1.16 tj 231: <li id="p013_icmp6_linklocal">
232: <font color="#009000">
233: <strong>013: RELIABILITY FIX: June 27, 2017</strong></font>
234: <i>All architectures</i>
235: <br>
236: When pinging an IPv6 link-local address, the reflected packet had
237: ::1 as source address. The echo reply was ignored as it must be
238: from the link-local address.
239: <br>
240: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/013_icmp6_linklocal.patch.sig">
241: A source code patch exists which remedies this problem.</a>
242: <p>
243:
1.17 tj 244: <li id="p014_libcrypto">
245: <font color="#009000">
246: <strong>014: RELIABILITY FIX: July 5, 2017</strong></font>
247: <i>All architectures</i>
248: <br>
249: Self-issued certificates are improperly treated as self-signed certificates,
250: leading to possible verification failures.
251: <br>
252: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/014_libcrypto.patch.sig">
253: A source code patch exists which remedies this problem.</a>
254: <p>
255:
1.18 tj 256: <li id="p015_sigio">
257: <font color="#009000">
258: <strong>015: RELIABILITY FIX: August 3, 2017</strong></font>
259: <i>All architectures</i>
260: <br>
261: A SIGIO-related use-after-free can occur in two drivers.
262: <br>
263: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/015_sigio.patch.sig">
264: A source code patch exists which remedies this problem.</a>
265: <p>
266:
267: <li id="p016_sendsyslog">
268: <font color="#009000">
269: <strong>016: RELIABILITY FIX: August 3, 2017</strong></font>
270: <i>All architectures</i>
271: <br>
272: A missing length check in sendsyslog() may result in a kernel panic.
273: <br>
274: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/016_sendsyslog.patch.sig">
275: A source code patch exists which remedies this problem.</a>
276: <p>
277:
278: <li id="p017_fuse">
279: <font color="#009000">
280: <strong>017: SECURITY FIX: August 3, 2017</strong></font>
281: <i>All architectures</i>
282: <br>
283: An out-of-bound read in vfs_getcwd_scandir() (mainly used for FUSE)
284: may result in a kernel panic or info leak.
285: <br>
286: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/017_fuse.patch.sig">
287: A source code patch exists which remedies this problem.</a>
288: <p>
289:
290: <li id="p018_recv">
291: <font color="#009000">
292: <strong>018: SECURITY FIX: August 3, 2017</strong></font>
293: <i>All architectures</i>
294: <br>
295: An alignment issue in recv() may result in an info leak via ktrace().
296: <br>
297: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/018_recv.patch.sig">
298: A source code patch exists which remedies this problem.</a>
299: <p>
300:
301: <li id="p019_tcp_usrreq">
302: <font color="#009000">
303: <strong>019: SECURITY FIX: August 3, 2017</strong></font>
304: <i>All architectures</i>
305: <br>
306: With an invalid address family, tcp_usrreq() may take an unintended code path.
307: <br>
308: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/019_tcp_usrreq.patch.sig">
309: A source code patch exists which remedies this problem.</a>
310: <p>
311:
312: <li id="p020_sockaddr">
313: <font color="#009000">
314: <strong>020: SECURITY FIX: August 3, 2017</strong></font>
315: <i>All architectures</i>
316: <br>
317: Missing socket address validation from userland may result in an info leak.
318: <br>
319: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/020_sockaddr.patch.sig">
320: A source code patch exists which remedies this problem.</a>
321: <p>
322:
323: <li id="p021_ptrace">
324: <font color="#009000">
325: <strong>021: SECURITY FIX: August 3, 2017</strong></font>
326: <i>All architectures</i>
327: <br>
328: An uninitialized variable in ptrace() may result in an info leak.
329: <br>
330: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/021_ptrace.patch.sig">
331: A source code patch exists which remedies this problem.</a>
332: <p>
333:
334: <li id="p022_fcntl">
335: <font color="#009000">
336: <strong>022: SECURITY FIX: August 3, 2017</strong></font>
337: <i>All architectures</i>
338: <br>
339: An uninitialized variable in fcntl() may result in an info leak.
340: <br>
341: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/022_fcntl.patch.sig">
342: A source code patch exists which remedies this problem.</a>
343: <p>
344:
345: <li id="p023_wsdisplay">
346: <font color="#009000">
347: <strong>023: RELIABILITY FIX: August 3, 2017</strong></font>
348: <i>All architectures</i>
349: <br>
350: An integer overflow in wsdisplay_cfg_ioctl() may result in an out-of-bounds
351: read.
352: <br>
353: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/023_wsdisplay.patch.sig">
354: A source code patch exists which remedies this problem.</a>
355: <p>
356:
357: <li id="p024_sosplice">
358: <font color="#009000">
359: <strong>024: SECURITY FIX: August 3, 2017</strong></font>
360: <i>All architectures</i>
361: <br>
362: A race condition in sosplice() may result in a kernel memory leak.
363: <br>
364: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/024_sosplice.patch.sig">
365: A source code patch exists which remedies this problem.</a>
366: <p>
367:
368: <li id="p025_ieee80211">
369: <font color="#009000">
370: <strong>025: SECURITY FIX: August 3, 2017</strong></font>
371: <i>All architectures</i>
372: <br>
373: An out of bounds read could occur during processing of EAPOL frames in
374: the wireless stack. Information from kernel memory could be leaked to
375: root in userland via an ieee80211(9) ioctl.
376: <br>
377: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/025_ieee80211.patch.sig">
378: A source code patch exists which remedies this problem.</a>
379: <p>
380:
1.19 tj 381: <li id="p026_smap">
382: <font color="#009000">
383: <strong>026: SECURITY FIX: August 26, 2017</strong></font>
384: <i>amd64 and i386</i>
385: <br>
386: SMAP enforcement could be bypassed by userland code.
387: <br>
388: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/026_smap.patch.sig">
389: A source code patch exists which remedies this problem.</a>
390: <p>
391:
1.20 tj 392: <li id="p027_net80211_replay">
393: <font color="#009000">
394: <strong>027: SECURITY FIX: August 30, 2017</strong></font>
395: <i>All architectures</i>
396: <br>
397: State transition errors could cause reinstallation of old WPA keys.
398: <br>
399: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/027_net80211_replay.patch.sig">
400: A source code patch exists which remedies this problem.</a>
401: <p>
402:
1.21 tj 403: <li id="p028_perl">
404: <font color="#009000">
405: <strong>028: SECURITY FIX: September 22, 2017</strong></font>
406: <i>All architectures</i>
407: <br>
408: A buffer over-read and heap overflow in perl's regexp may result in
409: a crash or memory leak.
410: <br>
411: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/028_perl.patch.sig">
412: A source code patch exists which remedies this problem.</a>
413: <p>
414:
1.22 ! tj 415: <li id="p029_tcb">
! 416: <font color="#009000">
! 417: <strong>029: RELIABILITY FIX: September 27, 2017</strong></font>
! 418: <i>amd64</i>
! 419: <br>
! 420: Out of bounds TCB settings may result in a kernel panic.
! 421: <br>
! 422: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.1/common/029_tcb.patch.sig">
! 423: A source code patch exists which remedies this problem.</a>
! 424: <p>
! 425:
1.1 tj 426: </ul>
427:
428: <hr>
429:
430: </body>
431: </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