CONFIG_LEGACY_VSYSCALL_EMULATE: Full emulation

General informations

The Linux kernel configuration item CONFIG_LEGACY_VSYSCALL_EMULATE has multiple definitions:

Full emulation found in arch/x86/Kconfig

The configuration item CONFIG_LEGACY_VSYSCALL_EMULATE:

• prompt: Full emulation
• type: bool
• depends on: (none)
• defined in arch/x86/Kconfig
• found in Linux kernels: 5.3–5.18, 5.18+HEAD

Help text

The kernel traps and emulates calls into the fixed vsyscall address mapping. This makes the mapping non-executable, but it still contains readable known contents, which could be used in certain rare security vulnerability exploits. This configuration is recommended when using legacy userspace that still uses vsyscalls along with legacy binary instrumentation tools that require code to be readable.

An example of this type of legacy userspace is running Pin on an old binary that still uses vsyscalls.

Emulate found in arch/x86/Kconfig

The configuration item CONFIG_LEGACY_VSYSCALL_EMULATE:

• prompt: Emulate
• type: bool
• depends on: (none)
• defined in arch/x86/Kconfig
• found in Linux kernels: 4.4–4.20, 5.0–5.2

Help text

The kernel traps and emulates calls into the fixed vsyscall address mapping. This makes the mapping non-executable, but it still contains known contents, which could be used in certain rare security vulnerability exploits. This configuration is recommended when userspace still uses the vsyscall area.

Hardware

LKDDb

Raw data from LKDDb:

• (none)

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: