[FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-16:08.zfs

FreeBSD Errata Notices errata-notices at freebsd.org
Wed May 4 22:56:40 UTC 2016

Hash: SHA512

FreeBSD-EN-16:08.zfs                                            Errata Notice
                                                          The FreeBSD Project

Topic:          Memory leak in ZFS

Category:       contrib
Module:         zfs
Announced:      2016-05-04
Credits:        Eric Borisch
Affects:        All supported versions of FreeBSD.
Corrected:      2016-03-18 13:32:00 UTC (stable/10, 10.3-STABLE)
                2016-05-04 15:25:47 UTC (releng/10.3, 10.3-RELEASE-p2)
                2016-05-04 15:26:23 UTC (releng/10.2, 10.2-RELEASE-p16)
                2016-05-04 15:27:09 UTC (releng/10.1, 10.1-RELEASE-p33)
                2016-03-18 13:32:37 UTC (stable/9, 9.3-STABLE)
                2016-05-04 15:27:09 UTC (releng/9.3, 9.3-RELEASE-p41)

For general information regarding FreeBSD Errata Notices and Security
Advisories, including descriptions of the fields above, security
branches, and the following sections, please visit

I.   Background

ZFS is one of several filesystems available on FreeBSD.  ZFS supports many
advanced features, including snapshots, which provides a frozen read-only
image of file system at a given time.

File system snapshots can be accessed under the .zfs/snapshot directory
in the root of the file system.

II.  Problem Description

There is a memory leak in the error path when mounting a snapshot via the
automatic .zfs/snapshot directory, which can be triggered when the snapshot
was once mounted, but later deleted by the system administrator.

III. Impact

A local user may be able to trigger the memory leak multiple times and
eventually exhaust kernel memory, if the user knows a snapshot and access
it before the system administrator deletes it.

IV.  Workaround

No workaround is available, but systems that do not use ZFS snapshots are
not affected.

V.   Solution

Perform one of the following:

1) Upgrade your system to a supported FreeBSD stable or release / security
branch (releng) dated after the correction date.

Reboot is required.

2) To update your system via a binary patch:

Systems running a RELEASE version of FreeBSD on the i386 or amd64
platforms can be updated via the freebsd-update(8) utility:

# freebsd-update fetch
# freebsd-update install

Reboot is required.

3) To update your system via a source code patch:

The following patches have been verified to apply to the applicable
FreeBSD release branches.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch https://security.FreeBSD.org/patches/EN-16:08/zfs.patch
# fetch https://security.FreeBSD.org/patches/EN-16:08/zfs.patch.asc
# gpg --verify zfs.patch.asc

b) Apply the patch.  Execute the following commands as root:

# cd /usr/src
# patch < /path/to/patch

c) Recompile your kernel as described in
<URL:https://www.FreeBSD.org/handbook/kernelconfig.html> and reboot the

VI.  Correction details

The following list contains the correction revision numbers for each
affected branch.

Branch/path                                                      Revision
- -------------------------------------------------------------------------
stable/9/                                                         r297022
releng/9.3/                                                       r299068
stable/10/                                                        r297021
releng/10.1/                                                      r299068
releng/10.2/                                                      r299067
releng/10.3/                                                      r299066
- -------------------------------------------------------------------------

To see which files were modified by a particular revision, run the
following command, replacing NNNNNN with the revision number, on a
machine with Subversion installed:

# svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base

Or visit the following URL, replacing NNNNNN with the revision number:


VII. References

The latest revision of this advisory is available at


More information about the freebsd-announce mailing list