Annotation of www/errata66.html, Revision 1.21
1.1 deraadt 1: <!doctype html>
2: <html lang=en id=errata>
3: <meta charset=utf-8>
4:
5: <title>OpenBSD 6.6 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/errata66.html">
10:
11: <!--
12: IMPORTANT REMINDER
13: IF YOU ADD A NEW ERRATUM, MAIL THE PATCH TO TECH AND ANNOUNCE
14: -->
15:
16: <h2 id=OpenBSD>
17: <a href="index.html">
18: <i>Open</i><b>BSD</b></a>
19: 6.6 Errata
20: </h2>
21: <hr>
22:
23: For errata on a certain release, click below:<br>
1.21 ! schwarze 24: <a href="errata20.html">2.0</a>,
1.1 deraadt 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.21 ! schwarze 40: <br>
1.1 deraadt 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.21 ! schwarze 57: <br>
1.1 deraadt 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>,
66: <a href="errata60.html">6.0</a>,
67: <a href="errata61.html">6.1</a>,
68: <a href="errata62.html">6.2</a>,
69: <a href="errata63.html">6.3</a>,
70: <a href="errata64.html">6.4</a>,
1.3 deraadt 71: <a href="errata65.html">6.5</a>.
1.1 deraadt 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
77: <a href="https://man.openbsd.org/OpenBSD-6.6/signify.1">signify(1)</a> tool and contains
78: usage instructions.
79: All the following patches are also available in one
80: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6.tar.gz">tar.gz file</a>
81: for convenience.
82:
83: <p>
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:
86: amd64, i386, arm64.
87:
88: <p>
89: Patches for supported releases are also incorporated into the
90: <a href="stable.html">-stable branch</a>, which is maintained for one year
91: after release.
92:
93: <hr>
94:
95: <ul>
96:
1.2 tj 97: <li id="p001_bpf">
98: <strong>001: RELIABILITY FIX: October 28, 2019</strong>
99: <i>All architectures</i>
100: <br>
101: bpf(4) has a race condition during device removal.
102: <br>
103: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/001_bpf.patch.sig">
104: A source code patch exists which remedies this problem.</a>
105: <p>
106:
107: <li id="p002_ber">
108: <strong>002: RELIABILITY FIX: October 28, 2019</strong>
109: <i>All architectures</i>
110: <br>
111: Various third party applications may crash due to symbol collision.
112: <br>
113: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/002_ber.patch.sig">
114: A source code patch exists which remedies this problem.</a>
115: <p>
1.1 deraadt 116:
1.4 tj 117: <li id="p003_bgpd">
118: <strong>003: RELIABILITY FIX: October 31, 2019</strong>
119: <i>All architectures</i>
120: <br>
121: bgpd(8) can crash on nexthop changes or during startup in certain
122: configurations.
123: <br>
124: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/003_bgpd.patch.sig">
125: A source code patch exists which remedies this problem.</a>
126: <p>
127:
1.5 tj 128: <li id="p004_net80211">
129: <strong>004: RELIABILITY FIX: November 16, 2019</strong>
130: <i>All architectures</i>
131: <br>
132: The kernel could crash due to a NULL pointer dereference in net80211.
133: <br>
134: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/004_net80211.patch.sig">
135: A source code patch exists which remedies this problem.</a>
136: <p>
137:
138: <li id="p005_sysupgrade">
139: <strong>005: RELIABILITY FIX: November 16, 2019</strong>
140: <i>All architectures</i>
141: <br>
142: A new kernel may require newer firmware images when using sysupgrade.
143: <br>
144: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/005_sysupgrade.patch.sig">
145: A source code patch exists which remedies this problem.</a>
146: <p>
147:
148: <li id="p006_ifioctl">
149: <strong>006: SECURITY FIX: November 16, 2019</strong>
150: <i>All architectures</i>
151: <br>
152: A regular user could change some network interface parameters due
153: to missing checks in the ioctl(2) system call.
154: <br>
155: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/006_ifioctl.patch.sig">
156: A source code patch exists which remedies this problem.</a>
157: <p>
158:
1.6 tj 159: <li id="p007_inteldrm">
160: <strong>007: SECURITY FIX: November 22, 2019</strong>
161: <i>i386 and amd64</i>
162: <br>
163: A local user could cause the system to hang by reading specific
164: registers when Intel Gen8/Gen9 graphics hardware is in a low power state.
165: A local user could perform writes to memory that should be blocked with
166: Intel Gen9 graphics hardware.
167: <br>
168: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/007_inteldrm.patch.sig">
169: A source code patch exists which remedies this problem.</a>
170: <p>
171:
172: <li id="p008_mesa">
173: <strong>008: SECURITY FIX: November 22, 2019</strong>
174: <i>All architectures</i>
175: <br>
176: Shared memory regions used by some Mesa drivers had permissions which
177: allowed others to access that memory.
178: <br>
179: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/008_mesa.patch.sig">
180: A source code patch exists which remedies this problem.</a>
181: <p>
182:
1.7 tb 183: <li id="p009_mesaxlock">
184: <strong>009: SECURITY FIX: December 4, 2019</strong>
185: <i>All architectures</i>
186: <br>
187: Environment-provided paths are used for dlopen() in mesa, resulting in
188: escalation to the auth group in xlock(1).
189: <br>
190: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/009_mesaxlock.patch.sig">
191: A source code patch exists which remedies this problem.</a>
192: <p>
193:
194: <li id="p010_libcauth">
195: <strong>010: SECURITY FIX: December 4, 2019</strong>
196: <i>All architectures</i>
197: <br>
198: libc's authentication layer performed insufficient username validation.
199: <br>
200: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/010_libcauth.patch.sig">
201: A source code patch exists which remedies this problem.</a>
202: <p>
203:
204: <li id="p011_xenodm">
205: <strong>011: SECURITY FIX: December 4, 2019</strong>
206: <i>All architectures</i>
207: <br>
208: xenodm uses the libc authentication layer incorrectly.
209: <br>
210: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/011_xenodm.patch.sig">
211: A source code patch exists which remedies this problem.</a>
212: <p>
213:
1.8 tj 214: <li id="p012_suauth">
215: <strong>012: SECURITY FIX: December 8, 2019</strong>
216: <i>All architectures</i>
217: <br>
218: A user can log in with a different user's login class.
219: <br>
220: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/012_suauth.patch.sig">
221: A source code patch exists which remedies this problem.</a>
222: <p>
223:
1.9 tj 224: <li id="p013_ldso">
225: <strong>013: SECURITY FIX: December 11, 2019</strong>
226: <i>All architectures</i>
227: <br>
228: ld.so may fail to remove the LD_LIBRARY_PATH environment variable for
229: set-user-ID and set-group-ID executables in low memory conditions.
230: <br>
231: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/013_ldso.patch.sig">
232: A source code patch exists which remedies this problem.</a>
233: <p>
234:
1.10 tj 235: <li id="p014_eret">
236: <strong>014: SECURITY FIX: December 18, 2019</strong>
237: <i>arm64</i>
238: <br>
239: ARM64 CPUs speculatively execute instructions after ERET.
240: <br>
241: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/014_eret.patch.sig">
242: A source code patch exists which remedies this problem.</a>
243: <p>
244:
1.11 tj 245: <li id="p015_ftp">
246: <strong>015: SECURITY FIX: December 20, 2019</strong>
247: <i>All architectures</i>
248: <br>
249: ftp(1) will follow remote redirects to local files.
250: <br>
251: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/015_ftp.patch.sig">
252: A source code patch exists which remedies this problem.</a>
253: <p>
254:
255: <li id="p016_ripd">
256: <strong>016: SECURITY FIX: December 20, 2019</strong>
257: <i>All architectures</i>
258: <br>
259: ripd(8) fails to validate authentication lengths.
260: <br>
261: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/016_ripd.patch.sig">
262: A source code patch exists which remedies this problem.</a>
263: <p>
264:
1.12 tj 265: <li id="p017_inteldrmctx">
266: <strong>017: SECURITY FIX: January 17, 2020</strong>
267: <i>i386 and amd64</i>
268: <br>
269: Execution Unit state was not cleared on context switch with Intel Gen9
270: graphics hardware.
271: <br>
272: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/017_inteldrmctx.patch.sig">
273: A source code patch exists which remedies this problem.</a>
274: <p>
275:
1.13 tj 276: <li id="p018_smtpd_tls">
277: <strong>018: RELIABILITY FIX: January 30, 2020</strong>
278: <i>All architectures</i>
279: <br>
280: smtpd can crash on opportunistic TLS downgrade, causing a denial of service.
281: <br>
282: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/018_smtpd_tls.patch.sig">
283: A source code patch exists which remedies this problem.</a>
284: <p>
285:
286: <li id="p019_smtpd_exec">
287: <strong>019: SECURITY FIX: January 30, 2020</strong>
288: <i>All architectures</i>
289: <br>
290: An incorrect check allows an attacker to trick mbox delivery into executing
291: arbitrary commands as root and lmtp delivery into executing arbitrary commands
292: as an unprivileged user.
293: <br>
294: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/019_smtpd_exec.patch.sig">
295: A source code patch exists which remedies this problem.</a>
296: <p>
297:
1.14 tj 298: <li id="p020_vmm_pvclock">
299: <strong>020: SECURITY FIX: February 17, 2020</strong>
300: <i>amd64</i>
301: <br>
302: A missing range check in the vmm pvclock allows a guest to write
303: to host memory.
304: <br>
305: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/020_vmm_pvclock.patch.sig">
306: A source code patch exists which remedies this problem.</a>
307: <p>
308:
1.15 tj 309: <li id="p021_smtpd_envelope">
310: <strong>021: SECURITY FIX: February 24, 2020</strong>
311: <i>All architectures</i>
312: <br>
313: An out of bounds read in smtpd allows an attacker to inject arbitrary
314: commands into the envelope file which are then executed as root.
315: Separately, missing privilege revocation in smtpctl allows arbitrary
316: commands to be run with the _smtpq group.
317: <br>
318: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/021_smtpd_envelope.patch.sig">
319: A source code patch exists which remedies this problem.</a>
320: <p>
1.14 tj 321:
1.16 tj 322: <li id="p022_sysctl">
323: <strong>022: RELIABILITY FIX: March 10, 2020</strong>
324: <i>All architectures</i>
325: <br>
326: Missing input validation in sysctl(2) can be used to crash the kernel.
327: <br>
328: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/022_sysctl.patch.sig">
329: A source code patch exists which remedies this problem.</a>
330: <p>
331:
1.17 tj 332: <li id="p023_sosplice">
333: <strong>023: RELIABILITY FIX: March 13, 2020</strong>
334: <i>All architectures</i>
335: <br>
336: Local outbound UDP broadcast or multicast packets sent by a spliced
337: socket can crash the kernel.
338: <br>
339: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/023_sosplice.patch.sig">
340: A source code patch exists which remedies this problem.</a>
341: <p>
342:
1.18 tj 343: <li id="p024_dhcpd">
344: <strong>024: SECURITY FIX: April 7, 2020</strong>
345: <i>All architectures</i>
346: <br>
347: dhcpd could reference freed memory after releasing a lease with an
348: unusually long uid.
349: <br>
350: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/024_dhcpd.patch.sig">
351: A source code patch exists which remedies this problem.</a>
352: <p>
353:
1.19 tj 354: <li id="p025_drm">
355: <strong>025: SECURITY FIX: April 19, 2020</strong>
356: <i>i386, amd64, arm64, loongson, macppc, sparc64</i>
357: <br>
1.20 tj 358: There was an incorrect test for root in the DRM Linux compatibility code.
1.19 tj 359: <br>
360: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.6/common/025_drm.patch.sig">
361: A source code patch exists which remedies this problem.</a>
362: <p>
363:
1.1 deraadt 364: </ul>
365:
1.17 tj 366: <hr>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata66.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www