CONFIG_RANDOMIZE_MODULE_REGION_FULL: Randomize the module region over a 2 GB range

General informations

The Linux kernel configuration item CONFIG_RANDOMIZE_MODULE_REGION_FULL has multiple definitions:

Randomize the module region over a 2 GB range found in arch/arm64/Kconfig

The configuration item CONFIG_RANDOMIZE_MODULE_REGION_FULL:

• prompt: Randomize the module region over a 2 GB range
• type: bool
• depends on: CONFIG_RANDOMIZE_BASE
• defined in arch/arm64/Kconfig
• found in Linux kernels: 5.14–5.19, 6.0–6.8, 6.9-rc+HEAD

Help text

Randomizes the location of the module region inside a 2 GB window covering the core kernel. This way, it is less likely for modules to leak information about the location of core kernel data structures but it does imply that function calls between modules and the core kernel will need to be resolved via veneers in the module PLT.

When this option is not set, the module region will be randomized over a limited range that contains the [_stext, _etext] interval of the core kernel, so branch relocations are almost always in range unless the region is exhausted. In this particular case of region exhaustion, modules might be able to fall back to a larger 2GB area.

Randomize the module region over a 4 GB range found in arch/arm64/Kconfig

The configuration item CONFIG_RANDOMIZE_MODULE_REGION_FULL:

• prompt: Randomize the module region over a 4 GB range
• type: bool
• depends on: CONFIG_RANDOMIZE_BASE
• defined in arch/arm64/Kconfig
• found in Linux kernels: 4.17–4.20, 5.0–5.13

Help text

Randomizes the location of the module region inside a 4 GB window covering the core kernel. This way, it is less likely for modules to leak information about the location of core kernel data structures but it does imply that function calls between modules and the core kernel will need to be resolved via veneers in the module PLT.

When this option is not set, the module region will be randomized over a limited range that contains the [_stext, _etext] interval of the core kernel, so branch relocations are always in range.

Randomize the module region independently from the core kernel found in arch/arm64/Kconfig

The configuration item CONFIG_RANDOMIZE_MODULE_REGION_FULL:

• prompt: Randomize the module region independently from the core kernel
• type: bool
• depends on: CONFIG_RANDOMIZE_BASE
• defined in arch/arm64/Kconfig
• found in Linux kernels: 4.6–4.16

Help text

Randomizes the location of the module region without considering the location of the core kernel. This way, it is impossible for modules to leak information about the location of core kernel data structures but it does imply that function calls between modules and the core kernel will need to be resolved via veneers in the module PLT.

When this option is not set, the module region will be randomized over a limited range that contains the [_stext, _etext] interval of the core kernel, so branch relocations are always in range.

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: