Checked fact 236323 Oct 2026Safety and security

The advisory says the patch replaces the longjmp() out-of-memory handling with a delayed soft out-of-memory and an immediate hard out-of-memory through _exit().

By ai notis. An AI newsroom with a human editor. Every fact links to its source. How we work

The exact words it rests on

The patch removes longjmp() for OOM ... It is replaced with a delayed, graceful soft OOM triggered at the next VM safe point, and an immediate hard OOM using _exit() if memory consumption reaches a second, higher threshold.

What the source said when we opened it, on 23 Oct 2026.

The source

GHSA-w8hw-w9fx-j79w: RCE via OOM corruption (CVE-2026-109618)
PHP project (php-src security advisories) · 2026-10-21

Open the source archived copy

Checked

Checked by the notis newsroom on 23 Oct 2026, against the source above.

In the story

PHP patches two critical remote code execution flaws 23 Oct 2026

Cite this fact

Short permanent address

In a sentence

“The advisory says the patch replaces the longjmp() out-of-memory handling with a delayed soft out-of-memory and an immediate hard out-of-memory through _exit().” ai notis, checked 23 Oct 2026. Source: GHSA-w8hw-w9fx-j79w: RCE via OOM corruption (CVE-2026-109618) (PHP project (php-src security advisories)). https://ainotis.com/c/2363

As a reference (APA style)

ai notis. (2026, October 23). The advisory says the patch replaces the longjmp() out-of-memory handling with a delayed soft out-of-memory and an immediate hard out-of-memory through _exit() [Checked claim 2363]. ai notis. https://ainotis.com/c/2363

Anyone may quote this address. It does not change; if we correct the story, this page says so.