CVE-2026-98622: net/sched: act_ct: don't WARN on benign flow_offload_alloc() failure
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 00734f3684fcec42c319bedfe68a5d357c720b53, 424ba52c0058deeb940d02cba52eb0aeb288db33, 47abe7a5c4eb53269aca3506446f851572a059a3; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 00734f3684fcec42c319bedfe68a5d357c720b53, 424ba52c0058deeb940d02cba52eb0aeb288db33, 47abe7a5c4eb53269aca3506446f851572a059a3; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.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: net/sched: act_ct: don't WARN on benign flow_offload_alloc() failure flow_offload_alloc() returns NULL when the conntrack entry is dying (e.g. raced with a conntrack flush) or when the GFP_ATOMIC allocation fails; both are expected under load and neither is a kernel bug. This path runs from softirq on every committed packet, so with panic_on_warn=1 an unprivileged user can panic the box just by racing a conntrack flush against a `tc ... action ct commit` classifier. Reproduced with a custom repro under QEMU: a small, fixed set of UDP flows through `tc filter ... action ct commit` on lo, raced against threads flooding bare ctnetlink CT_DELETE (flush) requests. Hits WARNING: net/sched/act_ct.c:437 (tcf_ct_flow_table_add(), inlined into tcf_ct_act() in this build) within ~15s on the unpatched kernel; same setup is clean on the patched kernel. The fix itself is behavior-preserving: both branches already did `goto err_alloc` before and after, only the WARN is removed.
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th 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.1%
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
- 5.7affected
- 64ff70b80fd403110b67dd9f7184a604fdb0da43 and later · before e8fcf3f08834e939b797311742ee72b1e2a08096affected · git
- 64ff70b80fd403110b67dd9f7184a604fdb0da43 and later · before af475f599270e59313552e6c6f3af8507da672b8affected · git
- 64ff70b80fd403110b67dd9f7184a604fdb0da43 and later · before 424ba52c0058deeb940d02cba52eb0aeb288db33affected · git
- 64ff70b80fd403110b67dd9f7184a604fdb0da43 and later · before d512c484bd93a5f2794aa03c9faeb7bcb82dbd4aaffected · git
- 64ff70b80fd403110b67dd9f7184a604fdb0da43 and later · before d805560ad69cb266d669341ca01e26bffb0d2c67affected · git
- 64ff70b80fd403110b67dd9f7184a604fdb0da43 and later · before 00734f3684fcec42c319bedfe68a5d357c720b53affected · git
- 64ff70b80fd403110b67dd9f7184a604fdb0da43 and later · before 650787233c2fd6e515a7c5f371019a9fa080ccd2affected · git
- 64ff70b80fd403110b67dd9f7184a604fdb0da43 and later · before 47abe7a5c4eb53269aca3506446f851572a059a3affected · git
- before 5.7not 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 | before 6.1.190-1 | 6.1.190-1 |
| 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.9-1 | 7.2.9-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-98620Oct 18, 2026 · net: ethernet: mtk_eth_soc: unregister net_devices in case of probe failure0Monitor
- ← EarlierCVE-2026-98621Oct 18, 2026 · net: gue: reject invalid REMCSUM offsets0Monitor
- Later →CVE-2026-98623Oct 18, 2026 · drm/nouveau/clk: fix list cursor use after loop in nvkm_clk_ustate_update0Monitor
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 | 00734f3684fcec42c319bedfe68a5d357c720b53 | Vendor (CNA) |
| Linux Linux | 424ba52c0058deeb940d02cba52eb0aeb288db33 | Vendor (CNA) |
| Linux Linux | 47abe7a5c4eb53269aca3506446f851572a059a3 | Vendor (CNA) |
| Linux Linux | 650787233c2fd6e515a7c5f371019a9fa080ccd2 | Vendor (CNA) |
| Linux Linux | af475f599270e59313552e6c6f3af8507da672b8 | Vendor (CNA) |
| Linux Linux | d512c484bd93a5f2794aa03c9faeb7bcb82dbd4a | Vendor (CNA) |
| Linux Linux | d805560ad69cb266d669341ca01e26bffb0d2c67 | Vendor (CNA) |
| Linux Linux | e8fcf3f08834e939b797311742ee72b1e2a08096 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1351 · Oct 19, 2026(Linux Kernel Güvenlik Bildirimi)
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/424ba52c0058deeb940d02cba52eb0aeb288db33
- git.kernel.org/stable/c/47abe7a5c4eb53269aca3506446f851572a059a3
- git.kernel.org/stable/c/650787233c2fd6e515a7c5f371019a9fa080ccd2
- git.kernel.org/stable/c/af475f599270e59313552e6c6f3af8507da672b8
- git.kernel.org/stable/c/d512c484bd93a5f2794aa03c9faeb7bcb82dbd4a
- git.kernel.org/stable/c/d805560ad69cb266d669341ca01e26bffb0d2c67
- git.kernel.org/stable/c/e8fcf3f08834e939b797311742ee72b1e2a08096
Vendor advisories and official records. Exploit/PoC links are deliberately left out.