Annotation of www/errata64.html, Revision 1.15
1.1 deraadt 1: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2: <html>
3: <head>
4: <title>OpenBSD 6.4 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">
1.7 deraadt 9: <link rel="canonical" href="https://www.openbsd.org/errata64.html">
1.1 deraadt 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.4 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: <a href="errata61.html">6.1</a>,
69: <a href="errata62.html">6.2</a>,
1.15 ! deraadt 70: <a href="errata63.html">6.3</a>,
! 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
1.3 tb 77: <a href="https://man.openbsd.org/OpenBSD-6.4/signify.1">signify(1)</a> tool and contains
1.1 deraadt 78: usage instructions.
79: All the following patches are also available in one
80: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4.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.4 tj 97: <li id="p001_xserver">
98: <font color="#009000">
99: <strong>001: SECURITY FIX: October 25, 2018</strong></font>
100: <i>All architectures</i>
101: <br>
102: The Xorg X server incorrectly validates certain options, allowing arbitrary
103: files to be overwritten.
104: As an immediate (temporary) workaround, the Xorg binary can be disabled
105: by running: <code>chmod u-s /usr/X11R6/bin/Xorg</code>
106: <br>
107: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/001_xserver.patch.sig">
108: A source code patch exists which remedies this problem.</a>
109: <p>
1.1 deraadt 110:
1.5 tj 111: <li id="p002_syspatch">
112: <font color="#009000">
113: <strong>002: RELIABILITY FIX: November 2, 2018</strong></font>
114: <i>i386, amd64, arm64</i>
115: <br>
116: The syspatch utility incorrectly handles symbolic links.
117: <br>
118: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/002_syspatch.patch.sig">
119: A source code patch exists which remedies this problem.</a>
120: <p>
121:
1.6 tj 122: <li id="p003_portsmash">
123: <font color="#009000">
124: <strong>003: SECURITY FIX: November 17, 2018</strong></font>
125: <i>All architectures</i>
126: <br>
127: The portsmash vulnerability allows exfiltration of elliptic curve keys.
128: <br>
129: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/003_portsmash.patch.sig">
130: A source code patch exists which remedies this problem.</a>
131: <p>
132:
133: <li id="p004_lockf">
134: <font color="#009000">
135: <strong>004: RELIABILITY FIX: November 17, 2018</strong></font>
136: <i>All architectures</i>
137: <br>
138: A recent change to POSIX file locks could cause incorrect results
139: during lock acquisition.
140: <br>
141: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/004_lockf.patch.sig">
142: A source code patch exists which remedies this problem.</a>
143: <p>
144:
1.8 tj 145: <li id="p005_perl">
146: <font color="#009000">
147: <strong>005: SECURITY FIX: November 29, 2018</strong></font>
148: <i>All architectures</i>
149: <br>
150: Various overflows exist in perl.
151: <br>
152: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/005_perl.patch.sig">
153: A source code patch exists which remedies this problem.</a>
154: <p>
155:
156: <li id="p006_uipc">
157: <font color="#009000">
158: <strong>006: RELIABILITY FIX: November 29, 2018</strong></font>
159: <i>All architectures</i>
160: <br>
161: UNIX domain sockets leak kernel memory with MSG_PEEK on SCM_RIGHTS, or can
162: attempt excessive memory allocations leading to a crash.
163: <br>
164: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/006_uipc.patch.sig">
165: A source code patch exists which remedies this problem.</a>
166: <p>
167:
168: <li id="p007_smtpd">
169: <font color="#009000">
170: <strong>007: RELIABILITY FIX: November 29, 2018</strong></font>
171: <i>All architectures</i>
172: <br>
173: The mail.mda and mail.lmtp delivery agents were not reporting temporary
174: failures correctly, causing smtpd to bounce messages in some cases where
175: it should have retried them.
176: <br>
177: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/007_smtpd.patch.sig">
178: A source code patch exists which remedies this problem.</a>
179: <p>
180:
181: <li id="p008_qcow2">
182: <font color="#009000">
183: <strong>008: RELIABILITY FIX: November 29, 2018</strong></font>
184: <i>amd64 and i386</i>
185: <br>
186: Writing more than 4GB to a qcow2 volume corrupts the virtual disk.
187: <br>
188: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/008_qcow2.patch.sig">
189: A source code patch exists which remedies this problem.</a>
190: <p>
191:
1.9 tj 192: <li id="p009_recvwait">
193: <font color="#009000">
194: <strong>009: RELIABILITY FIX: December 20, 2018</strong></font>
195: <i>All architectures</i>
196: <br>
197: While recv(2) with the MSG_WAITALL flag was receiving control
198: messages from a socket, the kernel could panic.
199: <br>
200: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/009_recvwait.patch.sig">
201: A source code patch exists which remedies this problem.</a>
202: <p>
203:
1.10 tj 204: <li id="p010_pcbopts">
205: <font color="#009000">
206: <strong>010: SECURITY FIX: December 22, 2018</strong></font>
207: <i>All architectures</i>
208: <br>
209: The setsockopt(2) system call could overflow mbuf cluster kernel
210: memory by 4 bytes.
211: <br>
212: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/010_pcbopts.patch.sig">
213: A source code patch exists which remedies this problem.</a>
214: <p>
215:
1.11 tj 216: <li id="p011_mincore">
217: <font color="#009000">
218: <strong>011: SECURITY FIX: January 27, 2019</strong></font>
219: <i>All architectures</i>
220: <br>
221: The mincore() system call can be used to observe memory access patterns
222: of other processes.
223: <br>
224: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/011_mincore.patch.sig">
225: A source code patch exists which remedies this problem.</a>
226: <p>
227:
228: <li id="p012_nfs">
229: <font color="#009000">
230: <strong>012: RELIABILITY FIX: January 27, 2019</strong></font>
231: <i>All architectures</i>
232: <br>
233: Missing length checks in the NFS server and client can lead to crashes
234: and other errors.
235: <br>
236: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/012_nfs.patch.sig">
237: A source code patch exists which remedies this problem.</a>
238: <p>
239:
240: <li id="p013_unveil">
241: <font color="#009000">
242: <strong>013: SECURITY FIX: January 27, 2019</strong></font>
243: <i>All architectures</i>
244: <br>
245: The unveil() system call can leak memory.
246: <br>
247: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/013_unveil.patch.sig">
248: A source code patch exists which remedies this problem.</a>
249: <p>
250:
1.12 tj 251: <li id="p014_pf6frag">
252: <font color="#009000">
253: <strong>014: SECURITY FIX: March 1, 2019</strong></font>
254: <i>All architectures</i>
255: <br>
256: Fragmented IPv6 packets may be erroneously passed by pf or lead to a crash.
257: <br>
258: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/014_pf6frag.patch.sig">
259: A source code patch exists which remedies this problem.</a>
260: <p>
261:
1.13 tj 262: <li id="p015_pficmp">
263: <font color="#009000">
264: <strong>015: SECURITY FIX: March 22, 2019</strong></font>
265: <i>All architectures</i>
266: <br>
267: A state in pf could pass ICMP packets to a destination IP address
268: that did not match the state.
269: <br>
270: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/015_pficmp.patch.sig">
271: A source code patch exists which remedies this problem.</a>
272: <p>
273:
1.14 tj 274: <li id="p016_vmmints">
275: <font color="#009000">
276: <strong>016: SECURITY FIX: March 27, 2019</strong></font>
277: <i>amd64 and i386</i>
278: <br>
279: GDT and IDT limits were improperly restored during VMM context switches.
280: <br>
281: <a href="https://ftp.openbsd.org/pub/OpenBSD/patches/6.4/common/016_vmmints.patch.sig">
282: A source code patch exists which remedies this problem.</a>
283: <p>
284:
1.1 deraadt 285: </ul>
286:
287: <hr>
288:
289: </body>
290: </html>
![[BACK]](/icons/back.gif){kind=icon}
Return to errata64.html CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [local] / www