===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/errata59.html,v
retrieving revision 1.16
retrieving revision 1.17
diff -u -r1.16 -r1.17
--- www/errata59.html 2016/06/27 19:58:07 1.16
+++ www/errata59.html 2016/07/14 18:17:19 1.17
@@ -213,6 +213,73 @@
A source code patch exists which remedies this problem.
+
+013: RELIABILITY FIX: July 14, 2016
+ All architectures
+Splicing sockets in a loop could cause a kernel spin.
+
+
+A source code patch exists which remedies this problem.
+
+
+
+014: RELIABILITY FIX: July 14, 2016
+ All architectures
+Multiple processes exiting with a fd-passing control message on a
+shared socket could crash the system.
+
+
+A source code patch exists which remedies this problem.
+
+
+
+015: RELIABILITY FIX: July 14, 2016
+ All architectures
+ufs_readdir failed to limit size of memory allocation, leading to panics.
+
+
+A source code patch exists which remedies this problem.
+
+
+
+016: SECURITY FIX: July 14, 2016
+ All architectures
+The mmap extension __MAP_NOFAULT could overcommit resources and crash
+the system.
+
+
+A source code patch exists which remedies this problem.
+
+
+
+017: RELIABILITY FIX: July 14, 2016
+ All architectures
+Tick counting overflows could cause a kernel crash.
+
+
+A source code patch exists which remedies this problem.
+
+
+
+018: RELIABILITY FIX: July 14, 2016
+ All architectures
+Invalid file descriptor use with kevent(2) could lead to a kernel crash.
+
+
+A source code patch exists which remedies this problem.
+
+
+
+019: RELIABILITY FIX: July 14, 2016
+ All architectures
+Unchecked parameters and integer overflows in the amap allocation routines
+could cause malloc(9) to either not allocate enough memory, leading to memory
+corruption, or to trigger a "malloc: allocation too large" panic.
+
+
+A source code patch exists which remedies this problem.
+
+