Allan Jude has issued us with a FreeBSD Errata Notice. Please check the article to take proper corrective measures.

Original post:

Hash: SHA512

FreeBSD-EN-15:04.freebsd-update Errata Notice
The FreeBSD Project

Topic: freebsd-update(8) does not ensure the previous upgrade was

Category: core
Module: freebsd-update
Announced: 2015-05-13
Credits: Allan Jude
Affects: All supported versions of FreeBSD.
Corrected: 2015-05-13 22:36:00 UTC (stable/10, 10.1-STABLE)
2015-05-13 22:52:35 UTC (releng/10.1, 10.1-RELEASE-p10)
2015-05-13 22:36:52 UTC (stable/9, 9.3-STABLE)
2015-05-13 22:52:51 UTC (releng/9.3, 9.3-RELEASE-p14)
2015-05-13 22:39:29 UTC (stable/8, 8.4-STABLE)
2015-05-13 22:52:51 UTC (releng/8.4, 8.4-RELEASE-p28)

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

The freebsd-update(8) utility is used to apply binary patches to FreeBSD
systems installed from official release images, as an alternative to
rebuilding from source. A freebsd-update(8) build server generates the
signed update packages, consisting of an index of files and directories
with checksums before the update, a set of binary patches, and an
index of files and directories with checksums after the update. The
client downloads the indexes, verifies the signatures and checksums,
then downloads and applies the required patches.

II. Problem Description

Binary upgrades using the freebsd-update(8) utility consist of several
invocations of the freebsd-update(8) utility itself. Each invocation
performs a different task that depends on the previous invocation being
successfully completed.

If an upgrade is not thoroughly completed, it is possible for the
freebsd-update(8) utility to download a subsequent patchset to a system
with an inconsistent userland and/or kernel. In the case of such an
incomplete upgrade, the freebsd-update(8) utility may incorrectly
evaluate the running userland and/or kernel, which can cause binary
patches to be incorrectly applied. In some situations, it is possible
for patches to be applied for the incorrect FreeBSD version.

III. Impact

If incorrect patches are applied to the system as a result of a previous
incomplete upgrade, it is possible that some system services may fail to
start after rebooting the system, such as if the service is started by an
executable that depends on a shared library that has been relocated as
part of the upgrade.

IV. Workaround

No workaround is available, but systems that do not use FreeBSD-provided
binary updates to upgrade 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.

2) To update your present 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

3) To update your present 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.

[FreeBSD 9.3 and 10.1]
# fetch
# fetch
# gpg –verify freebsd-update.patch.asc

[FreeBSD 8.4]
# fetch
# fetch
# gpg –verify freebsd-update-8.patch.asc

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

# cd /usr/src
# patch .

VI. Correction details

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

Branch/path Revision
– ————————————————————————-
stable/8/ r282872
releng/8.4/ r282874
stable/9/ r282871
releng/9.3/ r282874
stable/10/ r282870
releng/10.1/ r282873
– ————————————————————————-

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://

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

VII. References

The latest revision of this Errata Notice is available at