Skip to content
Noroxi
CVE.org (no NVD analysis yet)· CNA Linux

CVE-2026-98320: netfilter: flowtable: hold reference on ct until flow is released

Noroxi assessment

Priority: Monitor (action score 31/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.13% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 12c1ac230f4ca16e0017b62a963ab75e0b48074f, 61c6688be282277c6e91ab286a7acd0ae8681ac6, 8274cdc5f9c57e17ed77fc4ba76212536c840f25; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.

Low priority for now. Upgrade to Linux Linux 12c1ac230f4ca16e0017b62a963ab75e0b48074f, 61c6688be282277c6e91ab286a7acd0ae8681ac6, 8274cdc5f9c57e17ed77fc4ba76212536c840f25; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.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: netfilter: flowtable: hold reference on ct until flow is released nf_ct_put() releases the ct->ext area inmediately, the rcu typesafe semantics also allow to refer to the wrong conntrack from the flowtable datapath. Hold reference on ct until flow is released after rcu grace period. Add rcu_barrier() on module exit path, to ensure pending flow entries are release before module goes away.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Oct 6, 2026
Updated
Oct 19, 2026
EPSS
0.1% · 3th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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.

Follow CVE-2026-98320

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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

    • 4.16affected
    • 0ff90b6c20340e57616a51ae1a1bf18156d6638a and later · before 93ff1594be1aad4da364462dd8db050ebcfda2deaffected · git
    • 0ff90b6c20340e57616a51ae1a1bf18156d6638a and later · before eed6997e8dc40593a539fcc722e7ed51b18db86caffected · git
    • 0ff90b6c20340e57616a51ae1a1bf18156d6638a and later · before 61c6688be282277c6e91ab286a7acd0ae8681ac6affected · git
    • 0ff90b6c20340e57616a51ae1a1bf18156d6638a and later · before a43cd2b67b91e943273c913237a7a88c50cdcfbcaffected · git
    • 0ff90b6c20340e57616a51ae1a1bf18156d6638a and later · before 8274cdc5f9c57e17ed77fc4ba76212536c840f25affected · git
    • 0ff90b6c20340e57616a51ae1a1bf18156d6638a and later · before 12c1ac230f4ca16e0017b62a963ab75e0b48074faffected · git
    • 0ff90b6c20340e57616a51ae1a1bf18156d6638a and later · before d9e6175a3ee48209ee65f294fc567b4e16b29b74affected · git
    • 0ff90b6c20340e57616a51ae1a1bf18156d6638a and later · before e75a9fa1d44bcbd66ea02e8781bcca6ea4076e0daffected · git
    • before 4.16not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.176.1.el8_104.18.0-553.176.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.176.1.rt7.517.el8_104.18.0-553.176.1.rt7.517.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.176.1.rt7.517.el8_104.18.0-553.176.1.rt7.517.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.176.1.rt7.517.el8_104.18.0-553.176.1.rt7.517.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.176.1.rt7.517.el8_104.18.0-553.176.1.rt7.517.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.176.1.rt7.517.el8_104.18.0-553.176.1.rt7.517.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.176.1.rt7.517.el8_104.18.0-553.176.1.rt7.517.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.176.1.rt7.517.el8_104.18.0-553.176.1.rt7.517.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.176.1.rt7.517.el8_104.18.0-553.176.1.rt7.517.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.176.1.rt7.517.el8_104.18.0-553.176.1.rt7.517.el8_10

+66

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-98318Oct 6, 2026 · smb: client: validate absolute native symlink targets before NT fixups
    31Monitor
  • ← EarlierCVE-2026-98319Oct 6, 2026 · drm: Fix drm_pending_vblank_event leak in error path for out_fence_ptr
    0Monitor
  • Later →CVE-2026-98321Oct 6, 2026 · netfilter: nf_nat: unregister and release hooks on error
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux12c1ac230f4ca16e0017b62a963ab75e0b48074fVendor (CNA)
Linux Linux61c6688be282277c6e91ab286a7acd0ae8681ac6Vendor (CNA)
Linux Linux8274cdc5f9c57e17ed77fc4ba76212536c840f25Vendor (CNA)
Linux Linux93ff1594be1aad4da364462dd8db050ebcfda2deVendor (CNA)
Linux Linuxa43cd2b67b91e943273c913237a7a88c50cdcfbcVendor (CNA)
Linux Linuxd9e6175a3ee48209ee65f294fc567b4e16b29b74Vendor (CNA)
Linux Linuxe75a9fa1d44bcbd66ea02e8781bcca6ea4076e0dVendor (CNA)
Linux Linuxeed6997e8dc40593a539fcc722e7ed51b18db86cVendor (CNA)
azl3 kernel 6.6.157.1-1 on Azure Linux 3.06.6.158.1-1 · Release NotesMicrosoft (MSRC)
almalinux:bpftool4.18.0-553.176.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.176.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.176.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.176.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.176.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.176.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.176.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.176.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.176.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.176.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.176.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.176.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.190-1 · Debian:12Package registry (OSV)
debian:linux6.12.113-1 · Debian:13Package registry (OSV)
debian:linux7.2.8-1 · Debian:14Package registry (OSV)
debian:linux-6.126.12.113-1~deb12u1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.176.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.176.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.176.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.176.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.176.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+9

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.

  1. Published
  2. Fix recordedsame day
  3. TodayOct 27, 2026+21 d
EPSS, last 120 days

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 researchers

Finders, 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

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

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

  1. CVSS— → 7.8
  2. Severity— → high
  3. Exploit maturity— → none
  4. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records