News for hackers. Stuff that matters.
Re:CVE-2025-31160 Atop 2.11 heap problems by ianbutler on Saturday March 29, 2025 @07:03PM (#43519544)
Hey guys we commented on another thread from a few days ago about our tool Bismuth finding the bug (along with a sha of our reproducer script for proof) https://news.ycombinator.com/item?id=43489944

After disclosing and having correspondence with Gerlof and from his above post it looks like we did in fact nail it and I've just shared our write up on how we got it.

HN post detailing how we got it: https://news.ycombinator.com/item?id=43519522

Edit: Here's our reproducer and we've added it to the post too: https://gist.github.com/kallsyms/3acdf857ccc5c9fbaae7ed823be...

Re:CVE-2025-31160 Atop 2.11 heap problems by saagarjha on Saturday March 29, 2025 @07:08PM (#43519578)
What is that a hash of?
Re:CVE-2025-31160 Atop 2.11 heap problems by ianbutler on Saturday March 29, 2025 @07:08PM (#43519580)
As noted, our reproducer script
Re:CVE-2025-31160 Atop 2.11 heap problems by saagarjha on Saturday March 29, 2025 @07:10PM (#43519592)
Right, but where’s the script?
Re:CVE-2025-31160 Atop 2.11 heap problems by ianbutler on Saturday March 29, 2025 @07:17PM (#43519634)
Re:CVE-2025-31160 Atop 2.11 heap problems by saagarjha on Saturday March 29, 2025 @07:39PM (#43519752)
Cool, thanks for adding it. It would also be nice if you posted how you generated the hash :) I’m not trying to be annoying but this is a critical part of how these hashes work; you post the hash early to indicate you have some information early and then later you demonstrate that by actually presenting the artifact with that hash. If you don’t publish the artifact so people can check that it is actually what you claim it is then your hash is worthless (as nobody can prove it’s not, like, the hash of a cat photo). And you’d generally want to demonstrate how you generated the hash just so people don’t have to figure out whether to md5 or sha1sum it.
Re:CVE-2025-31160 Atop 2.11 heap problems by kallsyms on Saturday March 29, 2025 @07:53PM (#43519827)
Hey yeah got caught up in the excitement of finding it :)

It's a SHA256 - `shasum -a 256 server.py`

Re:CVE-2025-31160 Atop 2.11 heap problems by hannob on Sunday March 30, 2025 @03:41AM (#43522203)
> HN post detailing how we got it: https://news.ycombinator.com/item?id=43519522

I don't see any details there. Is there some link missing here, or is it the wrong link?

I'd be interested to read how your tool found it.

Re:CVE-2025-31160 Atop 2.11 heap problems by stavros on Sunday March 30, 2025 @06:29AM (#43523008)
It's just "we asked our LLM and it found the bug", as I understand it.