CVE-2026-98794: ipvs: filter some flags received in the backup server
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 3a9f5459db60311643bfbadf019f6d5370f2f26a, 438a5335276614186d6a96b8e7bddce811ad4ad6, 45a93111835ccfea7d969ec73588e33745fd9834; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1.
Low priority for now. Upgrade to Linux Linux 3a9f5459db60311643bfbadf019f6d5370f2f26a, 438a5335276614186d6a96b8e7bddce811ad4ad6, 45a93111835ccfea7d969ec73588e33745fd9834; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes; azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 6.6.161.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: ipvs: filter some flags received in the backup server While the IPVS SYNC protocol is not secure by design we can still protect the backup server from messages that can wreak havoc. This commit addresses problems from received connection flags or their combinations. We now drop messages as follows: 1. the NO_CPORT+TEMPLATE combination allows lookups for normal connections to hit template which can break in many ways. While the master does not sync connections with NO_CPORT flag, i.e. before they are established, we still accept NO_CPORT without TEMPLATE. 2. ONE_PACKET: it is not sent by master, so we do not expect it in backup. Before now it was ignored by IP_VS_CONN_F_BACKUP_MASK for protocol v1 while protocol v0 created connections that are not hashed and dropped immediately. Better to apply the IP_VS_CONN_F_BACKUP_MASK also to the flags from v0 messages for consistency with v1.
- Published
- Oct 18, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.14affected
- 87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 and later · before ef3cd6c0b826e50dc21653b32552e258de6fd51caffected · git
- 87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 and later · before 3a9f5459db60311643bfbadf019f6d5370f2f26aaffected · git
- 87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 and later · before 438a5335276614186d6a96b8e7bddce811ad4ad6affected · git
- 87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 and later · before d7d33c9efa9d1a2f244a1a64ec9b540b0f8975a0affected · git
- 87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 and later · before f4cd1db7d421e82945713a36084bb0c35b75b27eaffected · git
- 87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 and later · before 55d033324f67a15ff56be6d38d6e87f644e0ed62affected · git
- 87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 and later · before 45a93111835ccfea7d969ec73588e33745fd9834affected · git
- 87375ab47cd0ba04124c6d3fd80db5c368f5dcb6 and later · before f96e91748f6304668fe647e686d199d7207d36f1affected · git
- before 2.6.14not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.10-1 | 7.2.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98792Oct 18, 2026 · netfilter: flowtable: generalize pending status bit0Monitor
- ← EarlierCVE-2026-98793Oct 18, 2026 · netfilter: bpf: reject invalid NAT manipulation types0Monitor
- Later →CVE-2026-98795Oct 18, 2026 · net: sparx5: skip ptp deinit if init was skipped0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3a9f5459db60311643bfbadf019f6d5370f2f26a | Vendor (CNA) |
| Linux Linux | 438a5335276614186d6a96b8e7bddce811ad4ad6 | Vendor (CNA) |
| Linux Linux | 45a93111835ccfea7d969ec73588e33745fd9834 | Vendor (CNA) |
| Linux Linux | 55d033324f67a15ff56be6d38d6e87f644e0ed62 | Vendor (CNA) |
| Linux Linux | d7d33c9efa9d1a2f244a1a64ec9b540b0f8975a0 | Vendor (CNA) |
| Linux Linux | ef3cd6c0b826e50dc21653b32552e258de6fd51c | Vendor (CNA) |
| Linux Linux | f4cd1db7d421e82945713a36084bb0c35b75b27e | Vendor (CNA) |
| Linux Linux | f96e91748f6304668fe647e686d199d7207d36f1 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| azl3 kernel 6.6.159.1-1 on Azure Linux 3.0 | 6.6.161.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 7, 2026+20 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/438a5335276614186d6a96b8e7bddce811ad4ad6
- git.kernel.org/stable/c/45a93111835ccfea7d969ec73588e33745fd9834
- git.kernel.org/stable/c/55d033324f67a15ff56be6d38d6e87f644e0ed62
- git.kernel.org/stable/c/d7d33c9efa9d1a2f244a1a64ec9b540b0f8975a0
- git.kernel.org/stable/c/ef3cd6c0b826e50dc21653b32552e258de6fd51c
- git.kernel.org/stable/c/f4cd1db7d421e82945713a36084bb0c35b75b27e
- git.kernel.org/stable/c/f96e91748f6304668fe647e686d199d7207d36f1
Vendor advisories and official records. Exploit/PoC links are deliberately left out.