Home | Notifications | New Note | Local | Federated | Search | Logout

Note Detail

Reply to @musl@social.treehouse.systems
musl libc@musl@social.treehouse.systems (2026-10-22 00:49:51)
The patch in the advisory email adds checking for the overflows and also establishes improved early bounds intended to prevent the overflow conditions from being reachable in the first place.
---Reply---
musl libc@musl@social.treehouse.systems (2026-10-22 00:54:02)
As an issue that can lead to writes outside of an allocated object, overflowing into other objects on the heap, this should be taken with appropriate seriousness.

However, as far as we know at this time, without concurrent accesses from another thread to objects which might be stomped during regcomp, or unsafe SIGSEGV handler code, a predictable crash should happen before any further code runs that could use the clobbered objects in a way yielding control over the flow of execution to an attacker.

---Replies---

musl libc@musl@social.treehouse.systems (2026-10-22 00:55:35)
Programs which might pass attacker-controlled regular expressions to the libc regcomp function are affected.

Programs not using these interfaces are not affected.