CVE-2026-72338: net/sched: act_pedit: fix TOCTOU heap OOB write in tc offload
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.16% (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 0d8532a5e972a5351cf4ee4a435e0d65cbba8f23, 1afdf2268b71251ea70d80bd8232a2f022e62a73, 27488e1a7f19757e6146edca9458ed4ffc545557.
Low priority for now. Upgrade to Linux Linux 0d8532a5e972a5351cf4ee4a435e0d65cbba8f23, 1afdf2268b71251ea70d80bd8232a2f022e62a73, 27488e1a7f19757e6146edca9458ed4ffc545557 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_pedit: fix TOCTOU heap OOB write in tc offload There is a TOCTOU race condition in flower lockless approach between sizing a flow_rule buffer and filling it. zdi-disclosures@trendmicro.com reports: The cls_flower classifier operates with TCF_PROTO_OPS_DOIT_UNLOCKED (fl_change runs without RTNL), while RTM_NEWACTION holds RTNL, so the independent locking domains make the race reachable in practice. KASAN confirms: BUG: KASAN: slab-out-of-bounds in tcf_pedit_offload_act_setup+0x81b/0x930 Write of size 4 at addr ffff888001f27520 by task poc-toctou/312 The buggy address is located 0 bytes to the right of allocated 288-byte region [ffff888001f27400, ffff888001f27520) (cache kmalloc-512) Note: The result is a heap OOB write attacker-controlled content into the adjacent slab object (requires CAP_NET_ADMIN). The fix introduces reading tcfp_nkeys under act->tcfa_lock in all places using a new tcf_pedit_nkeys_locked() which replaces the old tcf_pedit_nkeys(). Additionally we close the remaining TOCTOU window between the sizing read and the fill reads by more careful accounting. Rather than silently truncating the key count, which leads to incorrect action semantics offloaded to hardware and secondary OOB writes if the remaining capacity is zero or consumed by prior actions, we enforce remaining capacity checks and return -ENOSPC if the required space exceeds the remaining capacity.
- Published
- Aug 15, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
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.
Is your version affected? Check itNoroxi 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
- 4.11affected
- 71d0ed7079dffbc5cd0941d77d9b84e04109c9bb and later · before 1afdf2268b71251ea70d80bd8232a2f022e62a73affected · git
- 71d0ed7079dffbc5cd0941d77d9b84e04109c9bb and later · before 0d8532a5e972a5351cf4ee4a435e0d65cbba8f23affected · git
- 71d0ed7079dffbc5cd0941d77d9b84e04109c9bb and later · before 27488e1a7f19757e6146edca9458ed4ffc545557affected · git
- 71d0ed7079dffbc5cd0941d77d9b84e04109c9bb and later · before 6f9b23eb92a894ae1118893996943990ee0b860eaffected · git
- 71d0ed7079dffbc5cd0941d77d9b84e04109c9bb and later · before 8e49cd891bda447c68122d672510a604a8bb6b24affected · git
- 71d0ed7079dffbc5cd0941d77d9b84e04109c9bb and later · before 8b519cbcabe836a441369fbec1a8a6518a709251affected · git
- before 4.11not affected · semver
- 6.1.191 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 | from 0 | — |
| 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-72336Aug 15, 2026 · Bluetooth: 6lowpan: hold L2CAP conn across debugfs control0Monitor
- ← EarlierCVE-2026-72337Aug 15, 2026 · Bluetooth: 6lowpan: avoid untracked enable work0Monitor
- Later →CVE-2026-72339Aug 15, 2026 · qede: fix off-by-one in BD ring consumption on build_skb failure39Monitor
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 | 0d8532a5e972a5351cf4ee4a435e0d65cbba8f23 | Vendor (CNA) |
| Linux Linux | 1afdf2268b71251ea70d80bd8232a2f022e62a73 | Vendor (CNA) |
| Linux Linux | 27488e1a7f19757e6146edca9458ed4ffc545557 | Vendor (CNA) |
| Linux Linux | 6f9b23eb92a894ae1118893996943990ee0b860e | Vendor (CNA) |
| Linux Linux | 8b519cbcabe836a441369fbec1a8a6518a709251 | Vendor (CNA) |
| Linux Linux | 8e49cd891bda447c68122d672510a604a8bb6b24 | Vendor (CNA) |
| debian:linux | 6.12.100-1 · Debian:13 | 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).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/1afdf2268b71251ea70d80bd8232a2f022e62a73
- git.kernel.org/stable/c/27488e1a7f19757e6146edca9458ed4ffc545557
- git.kernel.org/stable/c/6f9b23eb92a894ae1118893996943990ee0b860e
- git.kernel.org/stable/c/8b519cbcabe836a441369fbec1a8a6518a709251
- git.kernel.org/stable/c/8e49cd891bda447c68122d672510a604a8bb6b24
Vendor advisories and official records. Exploit/PoC links are deliberately left out.