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

musl libc@musl@social.treehouse.systems

Website: https://musl.libc.org
GIT: https://git.musl-libc.org/cgit/musl
Patreon: https://patreon.com/musl
Joined: 2026-09-23 22:43:46
5 notes, 0 following, 0 followers

Reply to @musl@social.treehouse.systems
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.

Reply to @musl@social.treehouse.systems
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.

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.

musl libc@musl@social.treehouse.systems (2026-10-22 00:48:09)
SECURITY ADVISORY: musl libc up through 1.2.6 (present version) is affected by integer overflows in regcomp (regular expression handling) leading to insufficient allocation of heap-based buffers for the compiled regex data structures.

CVE-2026-107891 has been assigned for this issue.

https://www.openwall.com/lists/musl/2026/10/21/1

musl libc@musl@social.treehouse.systems (2026-09-23 22:42:47)
Bikeshed time! The topic of default search path for musl locales is up for discussion: https://www.openwall.com/lists/musl/2026/09/23/6