FreeBSD Security Information

Introduction

FreeBSD takes security very seriously and its developers are
constantly working on making the operating system as secure as
possible. This page will provide information about what to do in
the event of a security vulnerability affecting your system

Table of Contents

Recent FreeBSD security vulnerabilities

A full list of all security vulnerabilities can be found on this page.

How to update your system

For most users, the easiest way to update your supported FreeBSD
10.1 or 9.3 system is to use the following
commands:

# freebsd-update fetch
# freebsd-update install

If that fails, follow the other instructions in the security
advisory you care about.

Supported FreeBSD releases

The designation and expected lifetime of all currently supported
branches are given below. The Expected EoL (end-of-life)
column indicates the earliest date on which support for that
branch or release will end. Please note that these dates may be
pushed back if circumstances warrant it.

Branch

Release

Type

Release Date

Expected EoL

stable/9

n/a

n/a

n/a

December 31, 2016

releng/9.3

9.3-RELEASE

Extended

July 16, 2014

December 31, 2016

stable/10

n/a

n/a

n/a

last release + 2 years

releng/10.1

10.1-RELEASE

Extended

November 14, 2014

December 31, 2016

Older releases are not maintained and users are strongly
encouraged to upgrade to one of the supported releases mentioned
above. A list of unsupported releases can be found here.

Each branch is supported by the Security Officer for a limited
time only, and is designated as either Normal or
Extended. The designation is used as a guideline for
determining the lifetime of the branch as follows:

Normal

Releases which are published from a -STABLE branch will be
supported by the Security Officer for a minimum of 12 months after the
release, and for sufficient additional time (if needed) to ensure
that there is a newer release for at least 3 months before the
older Normal release expires.

Extended

Selected releases (normally every second release plus the last
release from each -STABLE branch) will be supported by the
Security Officer for a minimum of 24 months after the release,
and for sufficient additional time (if needed) to ensure that
there is a newer Extended release for at least 3 months before the
older Extended release expires.

In the run-up to a Normal or Extended release, a number of -BETA
and -RC releases may be published. These releases are only
supported for a few weeks, as resources permit, and will not be
listed as supported on this page. Users are strongly discouraged
from running these releases on production systems.