CVE-2026-74290: net/sched: cls_flow: Dont expose folded kernel pointers
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 0a8b5b74f0e6b6b9ce453bcfa4baa502c4c7577a, 19f2ecf8ea564562c7e7a919cf38068dd9aa1c96, 3d054001860270748405a3f9270c5fa0bf7ffc19.
Low priority for now. Upgrade to Linux Linux 0a8b5b74f0e6b6b9ce453bcfa4baa502c4c7577a, 19f2ecf8ea564562c7e7a919cf38068dd9aa1c96, 3d054001860270748405a3f9270c5fa0bf7ffc19 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: cls_flow: Dont expose folded kernel pointers The flow classifier falls back to addr_fold() for fields that are missing from packet headers. In map mode, userspace controls mask, xor, rshift, addend and divisor, and can observe the resulting classid through class statistics. This allows a tc classifier in a user/network namespace to recover the 32-bit folded value of skb->sk, skb_dst() or skb_nfct(). Align with standard kernel practices for pointer hashing and replace the XOR folding with a keyed siphash (which is cryptographically secure)
- Published
- Aug 15, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.1% · 6th 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
- 2.6.25affected
- e5dfb815181fcb186d6080ac3a091eadff2d98fe and later · before 19f2ecf8ea564562c7e7a919cf38068dd9aa1c96affected · git
- e5dfb815181fcb186d6080ac3a091eadff2d98fe and later · before 3d054001860270748405a3f9270c5fa0bf7ffc19affected · git
- e5dfb815181fcb186d6080ac3a091eadff2d98fe and later · before fb31fbe51c233f3bf47021121f63d2e42cac2d08affected · git
- e5dfb815181fcb186d6080ac3a091eadff2d98fe and later · before 0a8b5b74f0e6b6b9ce453bcfa4baa502c4c7577aaffected · git
- e5dfb815181fcb186d6080ac3a091eadff2d98fe and later · before 6151159618198675e01c391676e579738286c135affected · git
- e5dfb815181fcb186d6080ac3a091eadff2d98fe and later · before f294fc71c4a0fa4964f6428a1b4e7929c1d83125affected · git
- before 2.6.25not affected · semver
- 6.1.178 and later · up to and including 6.1.*not affected · semver
- 6.6.145 and later · up to and including 6.6.*not 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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-74285Aug 15, 2026 · net: Stop leased rxq before uninstalling its memory provider35Monitor
- ← EarlierCVE-2026-74286Aug 15, 2026 · net: pfcp: allocate per-cpu tstats for PFCP netdevs0Monitor
- Later →CVE-2026-74298Aug 15, 2026 · RDMA/core: Fix FRMR set pinned push error path0Monitor
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 | 0a8b5b74f0e6b6b9ce453bcfa4baa502c4c7577a | Vendor (CNA) |
| Linux Linux | 19f2ecf8ea564562c7e7a919cf38068dd9aa1c96 | Vendor (CNA) |
| Linux Linux | 3d054001860270748405a3f9270c5fa0bf7ffc19 | Vendor (CNA) |
| Linux Linux | 6151159618198675e01c391676e579738286c135 | Vendor (CNA) |
| Linux Linux | f294fc71c4a0fa4964f6428a1b4e7929c1d83125 | Vendor (CNA) |
| Linux Linux | fb31fbe51c233f3bf47021121f63d2e42cac2d08 | Vendor (CNA) |
| debian:linux | 6.1.180-1 · 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.
No dated events beyond publication.
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/19f2ecf8ea564562c7e7a919cf38068dd9aa1c96
- git.kernel.org/stable/c/3d054001860270748405a3f9270c5fa0bf7ffc19
- git.kernel.org/stable/c/6151159618198675e01c391676e579738286c135
- git.kernel.org/stable/c/f294fc71c4a0fa4964f6428a1b4e7929c1d83125
- git.kernel.org/stable/c/fb31fbe51c233f3bf47021121f63d2e42cac2d08
Vendor advisories and official records. Exploit/PoC links are deliberately left out.