3 ms·
Cool detail, in the section where they reverse-engineer the presence of an LVP on the M3: Remarkably, while all other load widths activate the LVP on a
by tptacek 2y ago
Cool detail, in the section where they reverse-engineer the presence of an LVP on the M3:
Remarkably, while all other load widths activate the LVP
on any constant value fitting that width, we observe that acti-
vation on 8-byte wide loads occurs only when the load value
is zero. We conjecture that this may be a countermeasure for
memory safety such that the LVP will not learn values of
pointers. That is, with the M3 being a 64-bit CPU, pointers
are 8 bytes wide. Furthermore, on 64-bit macOS executables,
any virtual address below 0x100, 000, 000 is invalid.
- ijustlovemath 2y agowait, so does this mean that if an exploit tries to use a 32 bit address it's immediately shut down?
- anyfoo 2y agoThere are usually no valid 32 bit addresses, i.e. the first 4GB are not mapped.
- avianlyric 2y agoThat might be their point. As the OP quoted > any virtual address below 0x100, 000, 000 is invalid. That kinda suggests that all 32bit addresses are inherently invalid on 64bit MacOS
- saagarjha 2y agoGrouping a hex address by threes is crazy