Package: glibc Version: 2.43-7 X-Debbugs-CC: [email protected] Severity: important Tags: security upstream
Hi, The following vulnerability was published for glibc. CVE-2026-100290[0]: | The regcomp and regexec functions in the GNU C Library version 2.3 | to version 2.44 may read freed memory and free the same heap block | twice when a memory allocation fails while a regular expression is | compiled or matched. The re_dfa_add_node (the NFA node table) and | build_range_exp (bracket ranges) grow several arrays with | consecutive realloc calls and store the new pointers only after all | of them succeed. When a later call fails, the pattern buffer keeps | pointers to blocks that were already freed, and the error cleanup | frees them again. In regexec, the back-reference cache | (match_ctx_add_entry) frees its array when a realloc fails but keeps | the pointer, which is freed again on the error path. An attacker | does not need to supply a crafted regular expression: patterns large | enough to grow these arrays are common. The failure has to hit a | specific allocation, though, so the issue can only be reached when | the system is already under memory pressure. An attacker who | supplies the pattern or the subject string has little control over | which allocation fails, so the expected impact is a crash of the | process. This issue affects all architectures and ABIs supported by | the GNU C Library. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2026-100290 https://www.cve.org/CVERecord?id=CVE-2026-100290 [1] https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0028 Please adjust the affected versions in the BTS as needed. Regards, Salvatore

