espintcp: use sk_msg_free_partial to fix partial send
Noroxi assessment
Priority: Monitor (action score 39/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.75% (FIRST EPSS); higher than 54.3% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: Linux Linux 007800408002d871f5699bdb944f985896730b8f, 14c0b42c8a2cd9b5361bbff45b52f69c62c6a286, 4ea8c051b4bd7feec7749a980f2f70e1782b84d7.
Low priority for now. Upgrade to Linux Linux 007800408002d871f5699bdb944f985896730b8f, 14c0b42c8a2cd9b5361bbff45b52f69c62c6a286, 4ea8c051b4bd7feec7749a980f2f70e1782b84d7 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: espintcp: use sk_msg_free_partial to fix partial send sk_msg_free_partial() ensures consistency of the skmsg at every iteration, without having to manually handle uncharges and offsets. This simplifies the code, and fixes some bugs in skmsg accounting when we don't send the full contents.
- Published
- Aug 15, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.7% · 54th percentile
- CWE
- CWE-664
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 9.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.
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.6affected
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 518dcb84b997dff461800b079e5f2596389f766aaffected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 4ea8c051b4bd7feec7749a980f2f70e1782b84d7affected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before a977f78adce40b39d90d9567e7987bb110102810affected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 54d73f18f8919735f4d04d6f43374f75756c0180affected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 14c0b42c8a2cd9b5361bbff45b52f69c62c6a286affected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before a66d45e0ce6d73cd79962d422388e61bfaf0cb50affected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before a338ce41bc933d8f74c39d9b3b6f1d8ca53d9714affected · git
- e27cca96cd68fa2c6814c90f9a1cfd36bb68c593 and later · before 007800408002d871f5699bdb944f985896730b8faffected · git
- before 5.6not 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.187-1 | 6.1.187-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-72035Aug 15, 2026 · net/sched: sch_taprio: Replace direct dequeue call with peek and qdisc_dequeue_peeked32Monitor
- ← EarlierCVE-2026-72036Aug 15, 2026 · net/sched: sch_multiq: Replace direct dequeue call with peek and qdisc_dequeue_peeked31Monitor
- Later →CVE-2026-72045Aug 15, 2026 · octeontx2-af: cn10k: restrict VF LMTLINE sharing to its own PF35Monitor
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 | 007800408002d871f5699bdb944f985896730b8f | Vendor (CNA) |
| Linux Linux | 14c0b42c8a2cd9b5361bbff45b52f69c62c6a286 | Vendor (CNA) |
| Linux Linux | 4ea8c051b4bd7feec7749a980f2f70e1782b84d7 | Vendor (CNA) |
| Linux Linux | 518dcb84b997dff461800b079e5f2596389f766a | Vendor (CNA) |
| Linux Linux | 54d73f18f8919735f4d04d6f43374f75756c0180 | Vendor (CNA) |
| Linux Linux | a338ce41bc933d8f74c39d9b3b6f1d8ca53d9714 | Vendor (CNA) |
| Linux Linux | a66d45e0ce6d73cd79962d422388e61bfaf0cb50 | Vendor (CNA) |
| Linux Linux | a977f78adce40b39d90d9567e7987bb110102810 | Vendor (CNA) |
| debian:linux | 6.1.187-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
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- 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
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-664 · Improper Control of a Resource Through its LifetimeCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/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.
Attack patterns (CAPEC)
- Session Credential Falsification through ForgingCAPEC-196likelihood: Medium · Medium
- Exploitation of Trusted IdentifiersCAPEC-21likelihood: High · High
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
- Session FixationCAPEC-61likelihood: Medium · High
- Cross Site Request ForgeryCAPEC-62likelihood: High · Very High
ATT&CK techniques
- Access Token ManipulationT1134
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Access Token Manipulation: Create Process with TokenT1134.002
- Access Token Manipulation: Make and Impersonate TokenT1134.003
- Steal Application Access TokenT1528
- Steal Web Session CookieT1539
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Forge Web CredentialsT1606
Change log
- SSVC exploitation— → 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/14c0b42c8a2cd9b5361bbff45b52f69c62c6a286
- git.kernel.org/stable/c/4ea8c051b4bd7feec7749a980f2f70e1782b84d7
- git.kernel.org/stable/c/518dcb84b997dff461800b079e5f2596389f766a
- git.kernel.org/stable/c/54d73f18f8919735f4d04d6f43374f75756c0180
- git.kernel.org/stable/c/a338ce41bc933d8f74c39d9b3b6f1d8ca53d9714
- git.kernel.org/stable/c/a66d45e0ce6d73cd79962d422388e61bfaf0cb50
- git.kernel.org/stable/c/a977f78adce40b39d90d9567e7987bb110102810
Vendor advisories and official records. Exploit/PoC links are deliberately left out.