Re:Susctl CVE-2024-54507: A particularly 'sus' sysctl in the...
by nxobject on Thursday January 23, 2025 @05:43PM
(#42808837)
Did you get a bounty payout for this? I got the impression that Apple wasn't particularly on the ball with those.
[ Parent
| on HN ]
Re:Susctl CVE-2024-54507: A particularly 'sus' sysctl in the...
by ChocolateGod on Thursday January 23, 2025 @06:23PM
(#42809098)
Is it even exploitable in the real world?
Correct me if I'm wrong but you get 2 bytes of kernel data (potentially blank padding) and the same two bytes each time?
Re:Susctl CVE-2024-54507: A particularly 'sus' sysctl in the...
by bean-weevil on Thursday January 23, 2025 @06:45PM
(#42809213)
If the linker puts a pointer there, this would let you leak part of the pointer which could let you bypass kaslr. Not too likely for that to occur. If I were submitting this bug I would feel complete if they bought me a sandwich.
Re:Susctl CVE-2024-54507: A particularly 'sus' sysctl in the...
by axoltl on Thursday January 23, 2025 @07:49PM
(#42809533)
The bottom 2 bytes of a pointer contain two bits of the slide, assuming it's even a pointer into the kernelcache itself.
I'd take half a sandwich.
Re:Susctl CVE-2024-54507: A particularly 'sus' sysctl in the...
by the-rc on Friday January 24, 2025 @09:32AM
(#42813351)
Little endianness considered harmful
Re:Susctl CVE-2024-54507: A particularly 'sus' sysctl in the...
by bean-weevil on Saturday January 25, 2025 @09:32PM
(#42827185)
Yeah, you could probably contrive a situation where you get more interesting information (page numbers maybe?), but it definitely doesn't seem likely to me-
Re:Susctl CVE-2024-54507: A particularly 'sus' sysctl in the...
by buzzergfxkjkl on Thursday January 23, 2025 @07:32PM
(#42809450)
Good to find the bug regardless! I appreciated the succinct and not overly dramatic write-up. I don't think anything significant was claimed other than the fact that it is a kernel bug (which is significant in itself don't get me wrong).