High [CVE-2026-53000] use kfree_rcu to release ops
This high-severity Red Hat Linux advisory covers CVE-2026-53000 affecting Red Hat Enterprise Linux 10.0 Extended Update Support, Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions, Red Hat Enterprise Linux 9.6 Extended Update Support.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
In the Linux kernel, the following vulnerability has been resolved: netfilter: nat: use kfree_rcu to release ops Florian Westphal says: "Historically this is not an issue, even for normal base hooks: the data path doesn't use the original nf_hook_ops that are used to register the callbacks.
However, in v5.14 I added the ability to dump the active netfilter hooks from userspace. This code will peek back into the nf_hook_ops that are available at the tail of the pointer-array blob used by the datapath.
The nat hooks are special, because they are called indirectly from the central nat dispatcher hook. They are currently invisible to the nfnl hook dump subsystem though.
But once that changes the nat ops structures have to be deferred too." Update nf_nat_register_fn() to deal with partial exposition of the hooks from error path which can be also an issue for nfnetlink_hook. A flaw was found in the Linux kernel's netfilter component, specifically within the Network Address Translation (NAT) subsystem.
This vulnerability involves improper memory management when releasing network filter operation structures. This could potentially allow an attacker to cause a system crash, leading to a Denial of Service (DoS), or to gain unauthorized access to sensitive information due to the partial exposure of internal hook data during error handling.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
- kernel-0:6.12.0-55.98.1.el10_0
- kernel-0:5.14.0-687.45.1.el9_8
- kernel-0:5.14.0-427.150.1.el9_4
- kernel-0:5.14.0-570.141.1.el9_6
- RHSA-2026:55445
- RHSA-2026:64808
- RHSA-2026:68100
- RHSA-2026:67720
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
Mitigation
Upgrade to a fixed release: kernel-0:6.12.0-55.98.1.el10_0, kernel-0:5.14.0-687.45.1.el9_8, kernel-0:5.14.0-427.150.1.el9_4, kernel-0:5.14.0-570.141.1.el9_6, RHSA-2026:55445, RHSA-2026:64808. That is the remediation for this advisory.
The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.
Official advisory · high-confidence parse· fetched 21 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.