CVE-2026-53091
Linux Kernel vulnerability
- Published24 Jun 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:HAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:65334
- https://access.redhat.com/errata/RHSA-2026:66324
- https://access.redhat.com/errata/RHSA-2026:66325
- https://access.redhat.com/errata/RHSA-2026:67150
- https://access.redhat.com/security/cve/CVE-2026-53091
- https://bugzilla.redhat.com/show_bug.cgi?id=2492270
- https://git.kernel.org/stable/c/7fb4c19670110f052c04e1ec1d2b953b9f4f57e4
- https://git.kernel.org/stable/c/9d4f5c68f5ad4ab425f3ce1500c97c9f9743999a
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-53091.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-53091 being actively exploited?
CVE-2026-53091 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.14%.
How severe is CVE-2026-53091?
CVE-2026-53091 has a CVSS 3.1 base score of 8.4, rated high. EPSS estimates a 0.14% probability of exploitation.
Which products are affected by CVE-2026-53091?
Affected products include Linux Kernel.
How do I fix CVE-2026-53091?
Upgrade affected software to a fixed version, for example Linux Kernel 7.0.10 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-53091 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.