FreeBSD 10.4-RELEASE Errata
Abstract
This document lists errata items for FreeBSD 10.4-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.4-RELEASE will be maintained until the release of FreeBSD 10.4-RELEASE.
Table of Contents
Introduction
This errata document contains "late-breaking news" about FreeBSD 10.4-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 https://www.FreeBSD.org/releases/, plus any sites which keep up-to-date mirrors of this location.
Source and binary snapshots of FreeBSD 10.4-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 https://www.FreeBSD.org/security/.
Security Advisories
Advisory | Date | Topic |
---|---|---|
10 August 2017 |
Denial of Service vulnerability |
|
16 October 2017 |
WPA2 protocol vulnerability |
|
15 November 2017 |
Kernel data leak via
|
|
15 November 2017 |
POSIX shm allows jails to access global namespace |
|
15 November 2017 |
Information leak |
|
29 November 2017 |
Multiple vulnerabilities |
|
09 December 2017 |
Multiple vulnerabilities |
|
07 March 2018 |
Fix IPSEC validation and use-after-free |
|
07 March 2018 |
Multiple vulnerabilities |
|
04 April 2018 |
Fix vt(4) console memory disclosure |
|
04 April 2018 |
Fix denial of service |
|
08 May 2018 |
Mishandling of x86 debug exceptions |
|
06 August 2018 |
Resource exhaustion in TCP reassembly |
|
14 August 2018 |
L1 Terminal Fault (L1TF) Kernel Information Disclosure |
|
14 August 2018 |
Resource exhaustion in IP fragment reassembly |
|
14 August 2018 |
Unauthenticated EAPOL-Key Decryption Vulnerability |
|
12 September 2018 |
Improper ELF header parsing |
Errata Notices
Errata | Date | Topic |
---|---|---|
2 November 2017 |
Timezone database information update |
|
07 March 2018 |
Timezone database information update |
|
07 March 2018 |
Stack-based buffer overflow |
|
04 April 2018 |
Update timezone database information |
|
04 April 2018 |
Multiple small kernel memory disclosures |
|
08 May 2018 |
Multiple small kernel memory disclosures |
|
08 May 2018 |
Update timezone database information |
|
27 September 2018 |
Denial of service in |
|
27 September 2018 |
Small kernel memory disclosures in two system calls |
Open Issues
-
FreeBSD/i386 10.4-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 anOK
:set vfs.unmapped_buf_allowed=0 boot
Note that the following line has to be added to
/boot/loader.conf
after a boot. It disables unmapped I/O at every boot:vfs.unmapped_buf_allowed=0
-
FreeBSD/i386 10.4-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
entry20121223
, rebuilding the kernel withoptions KSTACK_PAGES=4
has been observed to resolve the boot-time crash. This, however, is not an ideal solution for inclusion in theGENERIC
kernel configuration, as increasingKSTACK_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 .
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 https://svn.freebsd.org/base/releng/10.4 /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
Warning:
It is extremely important to take note that, by default, freebsd-update(8) will install theGENERIC
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 thedvd1.iso
ISO:# mkdir -p /dist # mount -t cd9660 /dev/cd0 /dist
Note:
Be sure to use the correct/dev
device path for thedvd1.iso
ISO installer.Next, set
REPOS_DIR
to the path of therepos/
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
Note:
Keep in mind thatREPOS_DIR
will need to be set again after the current shell session is terminated, if continuing to use the packages provided on thedvd1.iso
installer.Finally, bootstrap pkg(8) from the ISO, and install required packages:
# pkg bootstrap # pkg install xorg-server xorg gnome3 [...]
-
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 viavagrant ssh
.
Late-Breaking News
No news.
Last modified on: January 26, 2021 by Sergio Carlavilla Delgado