FreeBSD 10.3-RELEASE Errata

The FreeBSD Project

FreeBSD is a registered trademark of the FreeBSD Foundation.

Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

SPARC, SPARC64, and UltraSPARC are trademarks of SPARC International, Inc in the United States and other countries. SPARC International, Inc owns all of the SPARC trademarks and under licensing agreements allows the proper use of these trademarks by its members.

Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the or the ® symbol.

Last modified on 2017-05-31 14:33:12 EDT by gjb.

This document lists errata items for FreeBSD 10.3-RELEASE, containing significant information discovered after the release or too late in the release cycle to be otherwise included in the release documentation. This information includes security advisories, as well as news relating to the software or documentation that could affect its operation or usability. An up-to-date version of this document should always be consulted before installing this version of FreeBSD.

This errata document for FreeBSD 10.3-RELEASE will be maintained until the release of FreeBSD 10.3-RELEASE.

Table of Contents
1. Introduction
2. Security Advisories
3. Errata Notices
4. Open Issues
5. Late-Breaking News

1. Introduction

This errata document contains late-breaking news about FreeBSD 10.3-RELEASE Before installing this version, it is important to consult this document to learn about any post-release discoveries or problems that may already have been found and fixed.

Any version of this errata document actually distributed with the release (for example, on a CDROM distribution) will be out of date by definition, but other copies are kept updated on the Internet and should be consulted as the current errata for this release. These other copies of the errata are located at, plus any sites which keep up-to-date mirrors of this location.

Source and binary snapshots of FreeBSD 10.3-STABLE also contain up-to-date copies of this document (as of the time of the snapshot).

For a list of all FreeBSD CERT security advisories, see

2. Security Advisories

FreeBSD-SA-16:09.ntp29 April 2016

Multiple ntp vulnerabilities.

FreeBSD-SA-16:17.openssl29 April 2016

Multiple OpenSSL vulnerabilities.

FreeBSD-SA-16:18.atkbd17 May 2016

Keyboard driver buffer overflow

FreeBSD-SA-16:19.sendmsg17 May 2016

Incorrect argument handling in sendmsg(2)

FreeBSD-SA-16:20.linux31 May 2016

Kernel stack disclosure in Linux compatibility layer

FreeBSD-SA-16:21.43bsd31 May 2016

Kernel stack disclosure in 4.3BSD compatibility layer

FreeBSD-SA-16:22.libarchive31 May 2016

Absolute path traversal vulnerability

FreeBSD-SA-16:23.libarchive31 May 2016

Absolute path traversal vulnerability

FreeBSD-SA-16:24.ntp3 June 2016

Multiple ntp vulnerabilties

FreeBSD-SA-16:25.bspatch25 July 2016

heap overflow vulnerability

FreeBSD-SA-16:26.openssl23 September 2016

Multiple vulnerabilities

FreeBSD-SA-16:27.openssl26 September 2016

Regression in OpenSSL suite

FreeBSD-SA-16:29.bspatch10 October 2016

Heap overflow vulnerability

FreeBSD-SA-16:30.portsnap10 October 2016

Multiple vulnerabilities

FreeBSD-SA-16:31.libarchive10 October 2016

Multiple vulnerabilities

FreeBSD-SA-16:33.openssh2 November 2016

Remote Denial of Service vulnerability

FreeBSD-SA-16:35.openssl2 November 2016

Remote Denial of Service vulnerability

FreeBSD-SA-16:36.telnetd6 December 2016

Possible login(1) argument injection

FreeBSD-SA-16:37.libc6 December 2016

link_ntoa(3) buffer overflow

FreeBSD-SA-16:38.bhyve6 December 2016

Possible escape from bhyve(8) virtual machine

FreeBSD-SA-16:39.ntp22 December 2016

Multiple vulnerabilities

FreeBSD-SA-17:01.openssh10 January 2017

Multiple vulnerabilities

FreeBSD-SA-17:02.openssl23 February 2017

Fix OpenSSL RC4_MD5 cipher vulnerability

FreeBSD-SA-17:03.ntp12 April 2017

Multiple vulnerabilities

FreeBSD-SA-17:04.ipfilter27 April 2017

Fix fragment handling panic

FreeBSD-SA-17:05.heimdal12 July 2017

Fix KDC-REP service name validation vulnerability

3. Errata Notices

FreeBSD-EN-16:06.libc4 May 2016

Performance regression in libc hash(3)

FreeBSD-EN-16:07.ipi4 May 2016

Excessive latency in x86 IPI delivery

FreeBSD-EN-16:08.zfs4 May 2016

Memory leak in ZFS

FreeBSD-EN-16:09.freebsd-update25 July 2016

Fix freebsd-update(8) support of FreeBSD 11.0-RELEASE

FreeBSD-EN-16:10.dhclient11 August 2016

Better handle unknown options received from aDHCP server

FreeBSD-EN-16:11.vmbus11 August 2016

Avoid using spin locks for channel message locks

FreeBSD-EN-16:12.hv_storvsc11 August 2016

Enable INQUIRY result check only on Windows 10 host systems

FreeBSD-EN-16:13.vmbus11 August 2016

Register time counter early enough for TSC freq calibration

FreeBSD-EN-16:14.hv_storvsc11 August 2016

Disable incorrect callout in hv_storvsc(4)

FreeBSD-EN-16:15.vmbus11 August 2016

Better handle the GPADL setup failure in Hyper-V

FreeBSD-EN-16:16.hv_storvsc11 August 2016

Fix SCSI INQUIRY checks and error handling

FreeBSD-EN-16:17.vm25 October 2016

Several virtual memory issues

FreeBSD-EN-16:19.tzcode6 December 2016

Fix warnings about invalid timezone abbreviations

FreeBSD-EN-16:20.tzdata6 December 2016

Update timezone database information

FreeBSD-EN-17:05.xen23 February 2017

Xen migration enhancements

FreeBSD-EN-17:06.hyperv12 July 2017

Boot compatibility improvements with Azure virtual machines

4. Open Issues

  • FreeBSD/i386 10.3-RELEASE running as a guest operating system on VirtualBox can have a problem with disk I/O access. It depends on some specific hardware configuration and does not depend on a specific version of VirtualBox or host operating system.

    It has been reported that instability may be present on virtual machines running on other hypervisors, such as Xen or KVM.

    It causes various errors and makes FreeBSD quite unstable. Although the cause is still unclear, disabling unmapped I/O works as a workaround. To disable it, choose Escape to loader prompt in the boot menu and enter the following lines from loader(8) prompt, after an OK:

    set vfs.unmapped_buf_allowed=0

    Note that the following line has to be added to /boot/loader.conf after a boot. It disables unmapped I/O at every boot:

  • FreeBSD/i386 10.3-RELEASE installed on ZFS may crash during boot when the ZFS pool mount is attempted while booting an unmodified GENERIC kernel.

    As described in /usr/src/UPDATING entry 20121223, rebuilding the kernel with options KSTACK_PAGES=4 has been observed to resolve the boot-time crash. This, however, is not an ideal solution for inclusion in the GENERIC kernel configuration, as increasing KSTACK_PAGES implicitly decreases available usermode threads in an environment that is already resource-starved.

    Taking into account the heavy resource requirements of ZFS, in addition to the i386-specific tuning requirements for general workloads, using ZFS with the FreeBSD/i386 GENERIC kernel is strongly discouraged.

    If installing FreeBSD/i386 on ZFS, it is possible to configure the system after installation to increase the KSTACK_PAGES.

    When prompted by bsdinstall(8) to perform additional post-installation configuration to the system, select [ YES ].

    This procedure requires the system sources available locally. If the System source code distribution was not selected during installation, it can be obtained using svnlite:

    # mkdir -p /usr/src
    # svnlite co svn:// /usr/src

    Build the kernel-toolchain required to rebuild the kernel:

    # make -C /usr/src kernel-toolchain

    Next, create a kernel configuration file to increase the KSTACK_PAGES option:

    # printf "include GENERIC\noptions KSTACK_PAGES=4\n" > /usr/src/sys/i386/conf/ZFS

    Then build and install the ZFS kernel:

    # make -C /usr/src buildkernel KERNCONF=ZFS
    # make -C /usr/src installkernel KERNCONF=ZFS


    It is extremely important to take note that, by default, freebsd-update(8) will install the GENERIC kernel configuration, and as such, freebsd-update(8) consumers are strongly encouraged to avoid FreeBSD-provided kernel binary upgrades with such configurations.

  • Due to an incompatibility between bsdconfig(8) and pkg(8), packages included on the FreeBSD dvd installer will not be recognized by bsdconfig(8).

    To install packages from the dvd1.iso installer, create the /dist target directory, and manually mount the dvd1.iso ISO:

    # mkdir -p /dist
    # mount -t cd9660 /dev/cd0 /dist


    Be sure to use the correct /dev device path for the dvd1.iso ISO installer.

    Next, set REPOS_DIR to the path of the repos/ directory within the installer so pkg(8) will use the correct repository metadata.

    If using sh(1):

    # export REPOS_DIR=/dist/packages/repos

    If using csh(1):

    # setenv REPOS_DIR /dist/packages/repos


    Keep in mind that REPOS_DIR will need to be set again after the current shell session is terminated, if continuing to use the packages provided on the dvd1.iso installer.

    Finally, bootstrap pkg(8) from the ISO, and install required packages:

    # pkg bootstrap
    # pkg install xorg-server xorg gnome3 [...]
  • An issue was discovered where the netstat(1) -s option will cause a segmentation fault on systems with IPSEC compiled into the kernel. The issue was resolved in the stable/10 branch, and an Errata Notice is planned after 10.3-RELEASE is released.

    [2015-08-19] Resolved as FreeBSD-EN-15:12.

  • An issue was discovered that causes make(1) to generate noisy output when doing source-based upgrades from FreeBSD 9.3 and earlier. The issue was reported in PR 202277, and after investigation and determining the issue does not cause source-based upgrades to fail, a post-release Errata Notice is planned.

    [2015-08-19] Resolved as FreeBSD-EN-15:11.

  • An issue with FreeBSD virtual machines with vagrant was discovered that affects the VirtualBox where the virtual machine will not start on the initial boot invoked with vagrant up.

    The issue is due to the virtual machine MAC being unset, as FreeBSD does not provide a default Vagrantfile.

    It has been observed, however, that a subsequent invocation of vagrant up will allow the virtual machine to successfully boot, allowing access via vagrant ssh.

  • [2015-08-16] An error was discovered in the release notes for FreeBSD 10.3-RELEASE regarding the drm device driver. The entry for r282199 states the driver was updated to match the version Linux® 3.8.13 version, however the entry should have noted the change affects device-independent code, and does not bring the drm driver fully in line with the stated Linux® version.

5. Late-Breaking News

No news.

This file, and other release-related documents, can be downloaded from

For questions about FreeBSD, read the documentation before contacting <>.

All users of FreeBSD 10.3-STABLE should subscribe to the <> mailing list.

For questions about this documentation, e-mail <>.