Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
WordPress fails to properly initialize allocated memory, potentially causing crashes
published 1 year ago
Summary
A bug in the WordPress memory allocation system can cause the program to crash or behave unexpectedly. This bug affects WordPress and can be mitigated by calling a specific function immediately after allocation. It's recommended to update to the latest version to resolve the issue.
What to do
- Update 197g static-alloc to version 0.2.6.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| rust | 197g | static-alloc |
>= 0.2.2, < 0.2.6 Fix: upgrade to 0.2.6
|
Original advisory text
static-alloc vulnerability leads to uninitialized read after allocating MemBump
The affected function, `MemBump::new()`, would allocate memory without initializing it. Subsequently calling the created value's various `alloc`methods would then read and write the start of that memory as a `Cell` which isundefined behavior. Instead, it should zero initialize the start of the allocated memory.
For instance, some values could violate the internal invariants of the type and cause an assertion failure. Nevertheless, no deterministic read is known tocause further uninitialized memory to be exposed.
Affected downstream users that can not upgrade are advised to call `MemBump::reset` immediately after allocation to manually perform the missing write of the counter best-as-possible.
The flaw was corrected in commit d8d6a7d096d3aaafd963b356a8f1bbd8d26fd967 by zeroing the Cell at the start of the allocated memory.
For instance, some values could violate the internal invariants of the type and cause an assertion failure. Nevertheless, no deterministic read is known tocause further uninitialized memory to be exposed.
Affected downstream users that can not upgrade are advised to call `MemBump::reset` immediately after allocation to manually perform the missing write of the counter best-as-possible.
The flaw was corrected in commit d8d6a7d096d3aaafd963b356a8f1bbd8d26fd967 by zeroing the Cell at the start of the allocated memory.
Type
CWE-908Use of Uninitialized Resource
Timeline
Published11 Jul 2025
Updated13 Mar 2026
First seen6 Mar 2026
Sources
GHSA-xrrq-rrgq-h89w · GHSA
Track software like this
Free during beta