Read the docs

Double free after allocation failure in glibc regcomp and regexec

Priority LOW 18CWE-415Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
—
Confidentiality · integrity · availability
None · None · Low
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

The GNU C Library (glibc) from 2.3 through 2.44 can read freed memory and free the same heap block twice in regcomp and regexec (CWE-415). When a memory allocation fails while a regular expression is compiled or matched, the error cleanup frees blocks that were already freed. An attacker who supplies the pattern or subject string has little control over which allocation fails, so the expected impact is a process crash under memory pressure.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Description from the CNA

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.

Why it matters now

EPSS 0.00336 27th percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
GNUglibc2.3 – 2.44—No fix listedCNA
  • glibc VendorGNU Affected 2.3 – 2.44 Fixed in — No fix listed CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:*——GNU
  • cpe:2.3:a:gnu:glibc:*:*:*:*:*:*:*:* Versions — — ·GNU

Remediation

The sources list no fixed version for glibc.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Timeline

  1. 2026-11-11 Threatist record created from CVE-2026-100290
  2. 2026-11-11 Alias added: GHSA-qvhh-2rc2-h32w

References

  • TI-2026-19388 Authentication bypass in GNU Inetutils telnetd via USER variable KEVCVSS 3.1CRITICAL 9.8
  • TI-2014-05975 GNU Bash environment variable parsing flaw lets attackers write files KEVCVSS 3.1CRITICAL 9.8
  • TI-2014-05157 Code execution in GNU Bash through crafted environment variables KEVCVSS 3.1CRITICAL 9.8
  • TI-2014-05164 Command injection in GNU Bash via crafted environment variables KEVCVSS 3.1HIGH 8.8
  • TI-2023-04522 Buffer overflow in glibc ld.so allows privilege escalation KEVCVSS 3.1HIGH 7.8
  • TI-2009-03392 The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft… CVSS 3.1CRITICAL 9.8
See all 1274 →

Sources