Debian Patches

Status for golang-github-dlclark-regexp2/1.11.0+ds1-2

Patch Description Author Forwarded Bugs Origin Last update
0001-increase-timeout-to-10ms.patch Increase timeout from 1 ms to 10 ms to prevent test errors For example:
=== RUN TestDeadline
fastclock_test.go:31: deadline (1ms) expired too soon (after 1.415402ms)
=== RUN TestStopTimeoutClock
fastclock_test.go:53: Expected duration less than 2ms, got 2.504717ms
Anthony Fok <foka@debian.org> not-needed vendor 2023-10-11
CVE-2026-77299.patch Fix unbounded memory growth on large repeats of zero-width expressions A pattern such as (?:){50000000} makes the match engine run the empty loop
body once per mandatory iteration, pushing onto the backtracking stack each
time. The parser accepts repeat counts up to math.MaxInt32 and the stack grows
without bound, so a pattern of a few bytes can OOM-kill the process.
MatchTimeout does not reliably help, as memory is allocated faster than the
timeout clock fires.
.
Backport of the upstream fix, adapted to the 1.x code base:
* syntax: a repeat of a literal empty expression is reduced to the empty
expression at compile time, so it needs no backtracking frames at all.
* runner: the backtracking stack is bounded. A match that needs more than
Regexp.MaxBacktrackingStackSize integer slots (default
DefaultMaxBacktrackingStackSize = 100000, negative for no limit) stops with
the new ErrBacktrackingStackLimit. This covers the other zero-width
variants, e.g. (?:^){50000000} and (){50000000}. The limit is never set
below the initial stack size of the pattern itself.
.
The v2 option API (OptionMaxBacktrackingStackSize) does not exist in 1.x, so
the limit is exposed the same way MatchTimeout is: a package default and a
per-Regexp field.
Damian Daniel <damian@danielovci.net> not-needed debian upstream backport, https://github.com/dlclark/regexp2/commit/6e446cb3a57a0f20112bc24353604fd00bdb309a 2026-11-14

All known versions for source package 'golang-github-dlclark-regexp2'

Links