CVE-2026-98793: Linux kernel · netfilter: bpf: reject invalid NAT manipulation types
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in f6143ae109df56d51d5536e813deb19eee7a6205 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:18 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in f6143ae109df56d51d5536e813deb19eee7a6205, ea777dc90ab37e64fa4b92f6fcf3b5edcef5e058, 752492947be3123ea6c689e2f93ae04ecd675d42 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
In the Linux kernel, the following vulnerability has been resolved: netfilter: bpf: reject invalid NAT manipulation types As bpf_ct_set_nat_info() is not validating the NAT manipulation type a wrong value can be passed directly to nf_nat_setup_info(). This triggers the WARN_ON() at nf_nat_setup_info() and if panic_on_warn isn't set, then IPS_SRC_NAT_DONE is set without adding nat_bysource and conntrack cleanup tries to unlink an uninitialized hlist node. Fix this by checking that NAT manipulation type is correct before calling nf_nat_setup_info(). In addition, if the WARN_ON is hit, return NF_DROP instead of continuing with the processing to avoid similar situations in the future.
References
- git.kernel.org/stable/c/752492947be3123ea6c689e2f93ae04ecd675d42 (opens in a new tab)
- git.kernel.org/stable/c/ea777dc90ab37e64fa4b92f6fcf3b5edcef5e058 (opens in a new tab)
- git.kernel.org/stable/c/f6143ae109df56d51d5536e813deb19eee7a6205 (opens in a new tab)
- git.kernel.org/stable/c/58108f05b0502448f6bb612ee2eccc63bd6449cb (opens in a new tab)
- git.kernel.org/stable/c/16d464013ec2267b00a83f4bfbb97b3ecc63bfa7 (opens in a new tab)