Custom Search
Navigation: Linux Kernel Driver DataBase - web LKDDB: Main index - D index
The Linux kernel configuration item CONFIG_DEBUG_WX has multiple definitions:
mm/Kconfig.debugThe configuration item CONFIG_DEBUG_WX:
( CONFIG_ARCH_HAS_DEBUG_WX ) && ( CONFIG_MMU )Generate a warning if any W+X mappings are found at boot.
This is useful for discovering cases where the kernel is leaving W+X mappings after applying NX, as such mappings are a security risk.
Look for a message in dmesg output like this:
<arch>/mm: Checked W+X mappings: passed, no W+X pages found.
or like this, if the check failed:
<arch>/mm: Checked W+X mappings: failed, <N> W+X pages found.
Note that even if the check fails, your kernel is possibly still fine, as W+X mappings are not a security hole in themselves, what they do is that they make the exploitation of other unfixed kernel bugs easier.
There is no runtime or memory usage effect of this option once the kernel has booted up - it's a one time check.
If in doubt, say "Y".
arch/arm/Kconfig.debugThe configuration item CONFIG_DEBUG_WX:
CONFIG_MMUGenerate a warning if any W+X mappings are found at boot.
This is useful for discovering cases where the kernel is leaving W+X mappings after applying NX, as such mappings are a security risk.
Look for a message in dmesg output like this:
arm/mm: Checked W+X mappings: passed, no W+X pages found.
or like this, if the check failed:
arm/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
Note that even if the check fails, your kernel is possibly still fine, as W+X mappings are not a security hole in themselves, what they do is that they make the exploitation of other unfixed kernel bugs easier.
There is no runtime or memory usage effect of this option once the kernel has booted up - it's a one time check.
If in doubt, say "Y".
arch/x86/Kconfig.debugThe configuration item CONFIG_DEBUG_WX:
(none)Generate a warning if any W+X mappings are found at boot.
This is useful for discovering cases where the kernel is leaving W+X mappings after applying NX, as such mappings are a security risk.
Look for a message in dmesg output like this:
x86/mm: Checked W+X mappings: passed, no W+X pages found.
or like this, if the check failed:
x86/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
Note that even if the check fails, your kernel is possibly still fine, as W+X mappings are not a security hole in themselves, what they do is that they make the exploitation of other unfixed kernel bugs easier.
There is no runtime or memory usage effect of this option once the kernel has booted up - it's a one time check.
If in doubt, say "Y".
arch/arm64/Kconfig.debugThe configuration item CONFIG_DEBUG_WX:
(none)Generate a warning if any W+X mappings are found at boot.
This is useful for discovering cases where the kernel is leaving W+X mappings after applying NX, as such mappings are a security risk. This check also includes UXN, which should be set on all kernel mappings.
Look for a message in dmesg output like this:
arm64/mm: Checked W+X mappings: passed, no W+X pages found.
or like this, if the check failed:
arm64/mm: Checked W+X mappings: FAILED, <N> W+X pages found.
Note that even if the check fails, your kernel is possibly still fine, as W+X mappings are not a security hole in themselves, what they do is that they make the exploitation of other unfixed kernel bugs easier.
There is no runtime or memory usage effect of this option once the kernel has booted up - it's a one time check.
If in doubt, say "Y".
Raw data from LKDDb:
(none)This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).
The data is retrived from:
Popular queries:
Navigation: Linux Kernel Driver DataBase - web LKDDB: main index - D index
Automatically generated (in year 2024). See also LKDDb sources on GitLab