Security / News explained
Check Point’s kernel advisory separates affected code from exposure
November 12 hotfixes address the Linux flaw disclosed on October 15. Check Point’s assessment distinguishes affected releases, default protections and the configuration needed for the demonstrated attack path.
Check Point’s November 12, 2026 hotfix releases include a correction for CVE-2026-98432, a Linux kernel memory-lifetime flaw disclosed on October 15. This is an update to an existing vulnerability, with a vendor-specific assessment of affected releases and exposure. The useful question is how the vulnerable code, the appliance’s configuration and the installed fix fit together. [2] [3]
The vendor lists R82, R82.10 and R82.20, plus Spark R81.10.x and R82.00.x, as affected versions. It lists R81.20 and lower as unaffected. The product scope includes firewalls, management and log servers, and Maestro Orchestrators. [1]
The underlying fault involves memory still being read
The Linux-authored CVE record describes a race during IPv4 TCP connection handling. One processing path can free an IP-options buffer while another CPU is still using it to construct a response. The resulting use-after-free can expose or corrupt kernel memory. The documented correction delays freeing the affected objects until an RCU grace period has passed. [2]
RCU, short for Read, Copy, Update, is a kernel synchronization mechanism. Its documentation explains how removal and reclamation can be separated, allowing existing readers to finish before the old object is reclaimed. That timing is central here: a value can have been valid when a reader obtained it and invalid by the time the reader uses it. [6]
As an analogy, imagine two people consulting the same working document while a third person retires it. Marking it obsolete is one decision; reclaiming its storage while someone still reads it is another. The analogy explains the lifetime problem without describing an exploit. In kernel code, the consequences reach the memory used by the operating system itself.
Default protections qualify the demonstrated attack path
Check Point says its firewalls are not exploitable in their default configuration: MPTCP is disabled, and vulnerable IP-option packets are dropped by default. For management servers, it says MPTCP is disabled by default and no exploitation was demonstrated in testing. Spark does not support MPTCP. These are the vendor’s qualified findings about its products. [1]
Multipath TCP lets a connection use several underlying paths, potentially combining interfaces or continuing when a path fails. Linux’s documentation describes it as an extension to standard TCP. Its sysctl documentation separately defines a setting controlling whether MPTCP sockets may be created. A supported feature and its enabled state are separate facts about a running system. [7] [8]
Our reading of the advisory preserves its scope: the demonstrated remote-code-execution path requires an MPTCP listener, while the underlying kernel record describes the memory race more broadly. A statement about that demonstrated path should not be expanded into a claim that disabling MPTCP removes every possible consequence of the underlying bug. [1] [2]
That is why a default-configuration statement needs to travel with its conditions. An appliance may have a history of approved changes, inherited settings or troubleshooting adjustments. Our operational interpretation is to retain the observed configuration alongside the vendor assessment. A default is useful context; a current observation establishes what is actually running.
The fixed package remains specific to the product
The November 12 release notes list the correction in R82.20 Jumbo Hotfix Take 14, R82.10 Take 52 and R82 Take 132. The support advisory separately identifies fixed Spark builds: R82.00.11 starting at B998002843 and R81.10.17 starting at B996005005. These identifiers should remain attached to their respective release families. [1] [3] [4] [5]
Our interpretation is that upstream kernel version tables and an appliance vendor’s release guidance answer related questions at different layers. A vendor can integrate changes into its maintained package. An operator deciding which appliance update to install needs the vendor’s fixed build and compatibility guidance, rather than treating an upstream version string as a complete decision.
The distinction also matters for assets behind a gateway. The vendor describes packet filtering as one of its default protections. In our view, the gateway’s own patch state, its current filtering policy and the protected system’s patch state should remain visible as separate observations. Evidence about one layer does not establish every other layer.
For this advisory, the practical conclusion is measured: use the fixed package for the affected branch, assess the actual configuration against the vendor’s stated conditions, and keep the October disclosure distinct from the November update. That gives a system owner a defensible picture of both remediation and exposure, without turning a headline score into a diagnosis.
Sources + further reading
Source dates describe the original material. Publication above is the date this Zyel article went live.
- Check Point response to CVE-2026-98432, sk1000339Check Point · Checked Nov 14, 2026
- Linux-authored CVE-2026-98432 recordCVE Program / Linux · Checked Nov 14, 2026
- R82.20 Jumbo Hotfix Take 14 release notesCheck Point · Checked Nov 14, 2026
- R82.10 Jumbo Hotfix Take 52 release notesCheck Point · Checked Nov 14, 2026
- R82 Jumbo Hotfix Take 132 release notesCheck Point · Checked Nov 14, 2026
- What is RCU? Read, Copy, UpdateThe Linux Kernel documentation · Checked Nov 14, 2026
- Multipath TCP overviewThe Linux Kernel documentation · Checked Nov 14, 2026
- MPTCP sysctl variablesThe Linux Kernel documentation · Checked Nov 14, 2026
Reader discussion
What would you ask next?
Questions, useful corrections and thoughtful disagreement are welcome. Comments are reviewed before they appear.
No reader comments yet.