Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-98793 Overview
CVE-2026-98793 is a Linux kernel vulnerability in the netfilter BPF subsystem. The function bpf_ct_set_nat_info() fails to validate the NAT manipulation type before passing it to nf_nat_setup_info(). A BPF program can supply an invalid manipulation value, triggering a WARN_ON() in nf_nat_setup_info(). When panic_on_warn is not set, the kernel continues execution with IPS_SRC_NAT_DONE set but without adding nat_bysource. Subsequent conntrack cleanup then attempts to unlink an uninitialized hlist node, leading to kernel memory corruption or denial of service.
Critical Impact
An unprivileged or privileged local actor loading a crafted BPF program can trigger kernel memory corruption through conntrack cleanup against an uninitialized hash list node.
Affected Products
- Linux kernel netfilter subsystem (net/netfilter/nf_nat_bpf.c)
- Kernel versions prior to the fix commits referenced in stable branches
- Distributions shipping affected kernel versions with BPF and netfilter NAT enabled
Discovery Timeline
- 2026-10-18 - CVE-2026-98793 published to NVD
- 2026-10-21 - Last updated in NVD database
Technical Details for CVE-2026-98793
Vulnerability Analysis
The flaw resides in the netfilter BPF helper bpf_ct_set_nat_info(), which configures NAT manipulation on a conntrack entry from within a BPF program. The helper accepts a manipulation type argument but does not validate that the value is a legitimate enum member before forwarding it to the core NAT setup routine nf_nat_setup_info().
When an invalid manipulation type reaches nf_nat_setup_info(), the kernel hits a WARN_ON() safety check. Rather than aborting, execution continues: IPS_SRC_NAT_DONE is set on the conntrack flags, but the nat_bysource hash list entry is never populated. The conntrack entry is left in an inconsistent state where metadata claims NAT configuration completed, but the backing data structures were never initialized.
The damage materializes during conntrack cleanup. The destructor path trusts IPS_SRC_NAT_DONE and calls hlist_nulls_del_rcu() on nat_bysource. Because that node was never added to any hash chain, the operation dereferences and writes to uninitialized hlist pointers, corrupting adjacent kernel memory or triggering a kernel oops.
Root Cause
The root cause is missing Input Validation in bpf_ct_set_nat_info(). The function trusts BPF-supplied arguments and relies on a downstream WARN_ON() as a safety net rather than enforcing enum bounds at the entry point. The downstream warning is not a terminating check, allowing a partially-initialized conntrack entry to persist.
Attack Vector
Exploitation requires the ability to load a BPF program that invokes bpf_ct_set_nat_info() with a crafted NAT manipulation type outside the valid enum range. On kernels that permit unprivileged BPF, or within containers granted CAP_BPF or CAP_NET_ADMIN, a local actor can trigger the inconsistent state. The resulting cleanup against an uninitialized hlist node produces either a kernel warning and denial of service, or memory corruption usable as a primitive for further privilege escalation.
No verified public proof-of-concept code is available. See the upstream patch commits for implementation-level detail: Kernel Patch Commit 16d4640, Kernel Patch Commit 7524929, and Kernel Patch Commit f6143ae.
Detection Methods for CVE-2026-98793
Indicators of Compromise
- Kernel log entries containing WARN_ON traces originating from nf_nat_setup_info() or nf_nat_bpf.c
- Kernel oops or general protection fault referencing hlist_nulls_del_rcu during conntrack destruction
- Unexpected loading of BPF programs attaching to netfilter hooks via BPF_PROG_TYPE_SCHED_CLS or BPF_PROG_TYPE_NETFILTER
Detection Strategies
- Audit bpf() syscall activity for programs that call bpf_ct_set_nat_info() with uncommon manipulation type values
- Correlate kernel warnings in dmesg and /var/log/kern.log with recent BPF program loads from non-root UIDs or container contexts
- Monitor for abnormal conntrack entry churn or cleanup errors reported through nf_conntrack statistics
Monitoring Recommendations
- Enable panic_on_warn=1 in non-production environments to surface the warning path immediately during testing
- Instrument auditd rules to log bpf() syscall arguments and program types for forensic reconstruction
- Collect kernel ring buffer data centrally and alert on WARN_ON patterns tied to netfilter and conntrack symbols
How to Mitigate CVE-2026-98793
Immediate Actions Required
- Apply the upstream kernel patches referenced in the stable commits as soon as vendor rebuilds are available
- Restrict CAP_BPF and CAP_NET_ADMIN to trusted workloads and disable unprivileged BPF where feasible using kernel.unprivileged_bpf_disabled=1
- Review container runtime policies to ensure untrusted containers cannot load netfilter BPF programs
Patch Information
The fix adds validation of the NAT manipulation type in bpf_ct_set_nat_info() before calling nf_nat_setup_info(), and returns NF_DROP if the WARN_ON is hit to prevent the inconsistent-state path. Fix commits are available at Kernel Patch Commit 16d4640, Kernel Patch Commit 58108f0, Kernel Patch Commit 7524929, Kernel Patch Commit ea777dc, and Kernel Patch Commit f6143ae.
Workarounds
- Set kernel.unprivileged_bpf_disabled=1 via sysctl to prevent unprivileged users from loading BPF programs
- Remove CAP_BPF and CAP_NET_ADMIN from container security profiles that do not require netfilter programmability
- Where netfilter BPF is unused, build or boot kernels without CONFIG_NF_CONNTRACK BPF helpers enabled
# Configuration example
# Disable unprivileged BPF program loading
sysctl -w kernel.unprivileged_bpf_disabled=1
echo 'kernel.unprivileged_bpf_disabled=1' >> /etc/sysctl.d/90-bpf-hardening.conf
# Verify current kernel version against patched builds
uname -r
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

