FreeBSD 11.2-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 2018-10-18 17:33:31 UTC by gjb.

This document lists errata items for FreeBSD 11.2-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 11.2-RELEASE will be maintained until the release of FreeBSD 11.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 11.2-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 11.2-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-18:08.tcp06 August 2018

Resource exhaustion in TCP reassembly

FreeBSD-SA-18:09.l1tf14 August 2018

L1 Terminal Fault (L1TF) Kernel Information Disclosure

FreeBSD-SA-18:10.ip14 August 2018

Resource exhaustion in IP fragment reassembly

FreeBSD-SA-18:11.hostapd14 August 2018

Unauthenticated EAPOL-Key Decryption Vulnerability

FreeBSD-SA-18:12.elf12 September 2018

Improper ELF header parsing

FreeBSD-SA-18:13.nfs27 November 2018

Multiple vulnerabilities

FreeBSD-SA-18:14.bhyve4 December 2018

Insufficient bounds checking

FreeBSD-SA-18:15.bootpd19 December 2018

Buffer overflow

FreeBSD-SA-19:01.syscall5 February 2019

Kernel data register leak

FreeBSD-SA-19:02.fd5 February 2019

File description reference count leak

FreeBSD-SA-19:03.wpa14 May 2019

Multiple vulnerabilities

FreeBSD-SA-19:04.ntp14 May 2019

Authenticated denial of service in ntpd(8)

FreeBSD-SA-19:05.pf14 May 2019

IPv6 fragment reassembly panic in pf(4)

FreeBSD-SA-19:06.pf14 May 2019

ICMP/ICMP6 packet filter bypass in pf(4)

FreeBSD-SA-19:07.mds14 May 2019

Microarchitectural Data Sampling

FreeBSD-SA-19:09.iconv2 July 2019

iconv(3) buffer overflow

FreeBSD-SA-19:10.ufs2 July 2019

Kernel stack disclosure

FreeBSD-SA-19:11.cd_ioctl2 July 2019

Privilege escalation in cd(4)

3. Errata Notices

FreeBSD-EN-18:08.lazyfpu12 September 2018

Regression in Lazy FPU remediation

FreeBSD-EN-18:09.ip27 September 2018

IP fragment remediation causes IPv6 reassembly failure

FreeBSD-EN-18:10.syscall27 September 2018

Null pointer dereference in freebsd4_getfsstat system call

FreeBSD-EN-18:11.listen27 September 2018

Denial of service in listen system call

FreeBSD-EN-18:12.mem27 September 2018

Small kernel memory disclosures in two system calls

FreeBSD-EN-18:13.icmp27 November 2018

ICMP buffer underwrite

FreeBSD-EN-18:14.tzdata27 November 2018

Timezone database information update

FreeBSD-EN-18:15.loader27 November 2018

Deferred kernel loading breaks loader password

FreeBSD-EN-18:16.ptrace19 December 2018

Kernel panic when attaching to stopped process

FreeBSD-EN-18:17.vm19 December 2018

Kernel panic under load on Intel® Skylake™ CPUs

FreeBSD-EN-18:18.zfs19 December 2018

ZFS vnode reclaim deadlock

FreeBSD-EN-19:03.sqlite9 January 2019

sqlite update

FreeBSD-EN-19:04.tzdata9 January 2019

Timezone database information update

FreeBSD-EN-19:05.kqueue9 January 2019

kqueue race condition and kernel panic

FreeBSD-EN-19:08.tzdata14 May 2019

Timezone database information update

FreeBSD-EN-19:09.xinstall14 May 2019

install(1) broken with partially matching relative paths

FreeBSD-EN-19:12.tzdata2 July 2019

Timezone database information update

4. Open Issues

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

    A system tunable has been added as of revision r286584 to make the kern.kstack_pages tunable configurable without recompiling the kernel.

    To mitigate system crashes with such configurations, choose Escape to loader prompt in the boot menu and enter the following lines from loader(8) prompt, after an OK:

    set kern.kstack_pages=4

    Add this line to /boot/loader.conf for the change to persist across reboots:

  • [2017-07-25] FreeBSD/arm64 currently lacks EFI real-time clock (RTC) support, which may cause the system to boot with the wrong time set.

    As a workaround, either enable ntpdate(8) or include ntpd_sync_on_start="YES" in rc.conf(5).

  • [2017-07-25] A late issue was discovered with FreeBSD/arm64 and "root on ZFS" installations where the root ZFS pool would fail to be located.

    There currently is no workaround.

  • [2017-11-06] 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.

  • [2018-06-21] An issue had been discovered late in the release cycle where removing ZFS vdevs from a pool under certain conditions would cause a system crash when zfsd(8) is enabled in rc.conf(5).

    At present, it is believed to be limited to removal of a mirror vdev from a pool consisting of multiple mirror vdevs.

    See PR 228750 for more information and updates as the issue is investigated.

  • [2018-06-26] An issue had been discovered late in the release cycle where a system crash could occur after installing emulators/virtualbox-ose-kmod from upstream package mirrors via pkg(8).

    Building emulators/virtualbox-ose-kmod from the ports(7) collection has been observed to work around the crash.

    See PR 228535 for more information.

  • [2018-06-26] It was discovered after the releng/11.2 branch was tagged for FreeBSD 11.2-RELEASE that a few device drivers were missing from the hardware page. The missing drivers, alc(4), cxgbev(4), liquidio(4), and mos(4) were added to the 11-STABLE hardware page.

  • [2018-06-26] The URL to the instructions for source-based upgrades in UPDATING incorrectly points to a page that no longer exists. The correct URL is

  • [2018-06-27] The announcement email for FreeBSD 11.2 incorrectly states the ocs_fw(4) driver had been added; this should have stated ocs_fc(4).

  • [2018-06-28] An issue had been reported after the release of FreeBSD 11.2 with x11/nvidia-driver installed from the upstream package mirrors via pkg(8).

    Building x11/nvidia-driver from the ports(7) collection has been reported to resolve the issue.

    See PR 228536 for more information.

  • [2018-10-18] A FreeBSD system with a custom kernel configuration excluding NFS on 10.x did not explicitly require the krpc option to be included when booting via ZFS-on-root and, for example, setting MODULES_OVERRIDE="zfs opensolaris" in the kernel configuration.

    In 11.x, however, krpc is explicitly required if the kernel configuration excludes NFS.

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 11.2-STABLE should subscribe to the <> mailing list.

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