/explore
|
You are here 
|
alfiecg.uk | ||
| | | | |
krinkinmu.github.io
|
|
| | | | | I'm continuing my exploration of the AArch64 architecture and this time I will touch on the AArch64 priviledge levels. Note that AArch64 priviledge model is not exactly the same as the previous iterations of ARM. While there are plenty of similarities, and there is a level of backward compatibility, at the same time, there are some differences as well. So do not assume that things covered here will work the same way for all ARMs. Finally, I assume that you're familiar with general GNU Assembler synatax or willing to figure things out as you go. Familiarity with ARM assmebly language will help, though I try to explain all the things I use. As always the code is available on GitHub. | |
| | | | |
blog.nelhage.com
|
|
| | | | | tl;dr "Transparent Hugepages" is a Linux kernel feature intended to improve performance by making more efficient use of your processor's memory-mapping hardware. It is enabled ("enabled=always") by default in most Linux distributions. Transparent Hugepages gives some applications a small performance improvement (~ 10% at best, 0-3% more typically), but can cause significant performance problems, or even apparent memory leaks at worst. To avoid these problems, you should set enabled=madvise on your server... | |
| | | | |
cpu.land
|
|
| | | | | Curious exactly what happens when you run a program on your computer? Learn how multiprocessing works, what system calls really are, how computers manage memory with hardware interrupts, and how Linux loads executables. | |
| | | | |
a13xp0p0v.tech
|
|
| | | CVE-2021-26708 is assigned to five race condition bugs in the virtual socket implementation of the Linux kernel. I discovered and fixed them in January 2021. In this article I describe how to exploit them for local privilege escalation on Fedora 33 Server for x86_64, bypassing SMEP and SMAP. | ||
