EUVD-2026-38959
GHSA-mjfm-6cr9-5cqx
Severity by source
AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:H
Local packet injection needing raw-socket privilege (AV:L/PR:L); over-read crosses the kernel boundary (S:C) leaking memory (C:H) and crashing the host (A:H) with no integrity impact.
Primary rating from Vendor (Linux).
CVSS VectorVendor: Linux
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:H
Lifecycle Timeline
5DescriptionCVE.org
In the Linux kernel, the following vulnerability has been resolved:
net: pull headers in qdisc_pkt_len_segs_init()
Most ndo_start_xmit() methods expects headers of gso packets to be already in skb->head.
net/core/tso.c users are particularly at risk, because tso_build_hdr() does a memcpy(hdr, skb->data, hdr_len);
qdisc_pkt_len_segs_init() already does a dissection of gso packets.
Use pskb_may_pull() instead of skb_header_pointer() to make sure drivers do not have to reimplement this.
Some malicious packets could be fed, detect them so that we can drop them sooner with a new SKB_DROP_REASON_SKB_BAD_GSO drop_reason.
AnalysisAI
Out-of-bounds memory access in the Linux kernel networking stack (net/core qdisc segmentation path) lets a local user feed malformed GSO (Generic Segmentation Offload) packets whose headers are not present in skb->head, causing drivers and net/core/tso.c (tso_build_hdr) to memcpy beyond valid bounds. The flaw can leak adjacent kernel memory and/or crash the system; it is not in CISA KEV and no public exploit has been identified, with a low EPSS of 0.15% (5th percentile) indicating low near-term exploitation likelihood. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires local access (AV:L) and the ability to inject malformed GSO/segmentation-offload packets whose headers are NOT linearized into skb->head - in practice this means privileged socket access such as CAP_NET_RAW (AF_PACKET), a tun/tap device, or a virtio/offload-capable transmit path, matching the PR:L requirement. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are mixed and lean toward a real but not urgent fix-on-cadence item. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A local user or compromised container with raw/packet socket access (CAP_NET_RAW) crafts a GSO packet whose protocol headers sit in paged fragments rather than the skb linear area, then transmits it through an interface so it hits the qdisc segmentation path. The kernel's tso_build_hdr() memcpy reads beyond the intended header bounds, leaking adjacent kernel memory back to the attacker or panicking the host; no public POC is currently referenced, and the local attack vector with low complexity (AV:L/AC:L) makes it reliable for an attacker who already holds the required socket privileges. |
| Remediation | Upstream fix available (commits 7fb4c19670110f052c04e1ec1d2b953b9f4f57e4 and 9d4f5c68f5ad4ab425f3ce1500c97c9f9743999a); the EUVD data indicates patched stable kernels in the 7.0.10 and 7.1 line - upgrade to your distribution's kernel build that incorporates these commits and reboot. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours: audit all Linux systems to identify affected kernel versions. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-131 – Incorrect Calculation of Buffer Size
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today