ARM64: Enable Kernel Address Space Randomization #1792
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
|
Of course - i don't see any reason not to merge, now the firmware is going to support it. Let's have it in 4.9 as well. |
popcornmix
pushed a commit
that referenced
this pull request
Jan 14, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 16, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 18, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 21, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 23, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 30, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 30, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 1, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 4, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 6, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 10, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 13, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 16, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 20, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 20, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 20, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
ED6E0F17
pushed a commit
to ED6E0F17/linux
that referenced
this pull request
Feb 24, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
HiassofT
pushed a commit
to HiassofT/rpi-linux
that referenced
this pull request
Feb 24, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Mar 1, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
ED6E0F17
pushed a commit
to ED6E0F17/linux
that referenced
this pull request
Mar 12, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Mar 12, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Mar 13, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Mar 17, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Mar 17, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Mar 18, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Nov 24, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Dec 1, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Dec 5, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Dec 12, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Dec 12, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Dec 14, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Dec 18, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Dec 18, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Dec 29, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Dec 29, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Dec 31, 2017
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 2, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 8, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 8, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 10, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 15, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 17, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 22, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 25, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 29, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Jan 31, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
TiejunChina
pushed a commit
to TiejunChina/linux
that referenced
this pull request
Feb 2, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 5, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 5, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 5, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 9, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
popcornmix
pushed a commit
that referenced
this pull request
Feb 12, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
TiejunChina
pushed a commit
to TiejunChina/linux
that referenced
this pull request
Feb 14, 2018
Randomization allows the mapping between virtual addresses and physical address to be different on each boot. This makes it more difficult to exploit security vulnerabilities that require knowledge of fixed hardware addresses. The firmware generates a 8 byte random number during bootup and stores it in the device tree under chosen/kaslr-seed. This number is used to randomize the address mapping. This change enables this feature in the build configuration for ARM64. Signed-off-by: Michael Zoran <mzoran@crowfest.net>
aswild
added a commit
to aswild/meta-newbs
that referenced
this pull request
Jan 19, 2019
Finally, a semi-not-hacky fix for the iptables bugs! After some googling I found a couple powerpc bug reports with the same alloc_counters bug stack trace [1]. Seems the issue is related to PREL32 (place-relative) relocations; somehow the 32-bit offset must be overflowing. That's not supposed to happen on arm64, but I guess somehow the Yocto gcc toolchain is doing it anyway. Disabling KASLR (CONFIG_RANDOMIZE_BASE=n, which turns off CONFIG_RELOCATABLE) removes those broken relocs and allows modules to link properly. I still don't really know why this is broken on the Pi or why I only ever saw the issue with iptables modules. I can't find anything different in these areas in the Pi downstream kernel. My Pis generally aren't hooked up to the internet so KASLR doesn't give much practical benefit, and sometimes the DT chosen/kaslr-seed was all zeros anyway. As a bonus, this change reduces the kernel Image size by almost 2 MB. [1] https://www.spinics.net/lists/netdev/msg520391.html [2] https://lore.kernel.org/lkml/20180704083651.24360-4-ard.biesheuvel@linaro.org [3] raspberrypi/firmware#694 [4] raspberrypi/linux#1792
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change enable address space randomization which is a great security feature in the ARM64 default build configuration. Testing was done with the firmware given at raspberrypi/firmware#694 which I understand will be included in the next public drop on github. Testing included testing a randomization enabled kernel on an old firmware version to make sure nothing breaks when randomization isn't available.
It would be awesome if this change could also be applied to 4.9 and possibly 4.8 so that I don't have to create a new pull request just to update older branches.