=================================================================== RCS file: /cvsrepo/anoncvs/cvs/www/errata59.html,v retrieving revision 1.17 retrieving revision 1.18 diff -c -r1.17 -r1.18 *** www/errata59.html 2016/07/14 18:17:19 1.17 --- www/errata59.html 2016/07/14 18:55:29 1.18 *************** *** 251,282 **** 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.

    --- 251,292 ---- A source code patch exists which remedies this problem.

    !

  • 017: RELIABILITY FIX: July 14, 2016   All architectures
    ! A race occuring in the unlocked ARP input path can lead to a kernel ! NULL dereference.
    ! A source code patch exists which remedies this problem.

    !

  • 018: RELIABILITY FIX: July 14, 2016   All architectures
    ! Tick counting overflows could cause a kernel crash.
    ! A source code patch exists which remedies this problem.

    !

  • 019: 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. +

    + +

  • + 020: 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.