1.. _release_notes_3.0.2:
2
3ACRN v3.0.2 (Nov 2022)
4######################
5
6We are pleased to announce the release of the Project ACRN hypervisor
7version 3.0.2 with hot fixes to the v3.0 release.
8
9ACRN is a flexible, lightweight reference hypervisor that is built with
10real-time and safety-criticality in mind. It is optimized to streamline
11embedded development through an open-source platform. See the
12:ref:`introduction` introduction for more information.
13
14All project ACRN source code is maintained in the
15https://github.com/projectacrn/acrn-hypervisor repository and includes
16folders for the ACRN hypervisor, the ACRN device model, tools, and
17documentation. You can download this source code either as a zip or
18tar.gz file (see the `ACRN v3.0.2 GitHub release page
19<https://github.com/projectacrn/acrn-hypervisor/releases/tag/v3.0.2>`_) or
20use Git ``clone`` and ``checkout`` commands::
21
22   git clone https://github.com/projectacrn/acrn-hypervisor
23   cd acrn-hypervisor
24   git checkout v3.0.2
25
26The project's online technical documentation is also tagged to
27correspond with a specific release: generated v3.0 documents can be
28found at https://projectacrn.github.io/3.0/.  Documentation for the
29latest development branch is found at https://projectacrn.github.io/latest/.
30
31ACRN v3.0.2 requires Ubuntu 20.04 (as does v3.0).  Follow the instructions in the
32:ref:`gsg` to get started with ACRN.
33
34
35What's New in v3.0.2
36********************
37
38Passthrough PMU (performance monitor unit) to user VM only in debug builds
39  ACRN v2.6 introduced PMU passthrough to RT VMs that have LAPIC passthrough
40  enabled. This is useful for performance profiling at development time but can
41  cause workload interference in a production build. PMU passthrough is only
42  enabled now for a hypervisor debug mode build.
43
44Added tarfile member sanitization to Python tarfile package extractall() calls
45  A vulnerability in the ACRN Configurator is patched, where files extracted
46  from a maliciously crafted tarball could  be written to somewhere outside the
47  target directory and cause unsafe behavior.
48
49Run executables with absolute paths in board inspector
50  Using partial executable paths in the board inspector may cause unintended
51  results when another executable has the same name and is found via PATH
52  settings. The board inspector now uses absolute paths to executable.
53
54
55
56See :ref:`release_notes_3.0` and :ref:`release_notes_3.0.1` for additional release information.
57