Skip to content
Threat Brief

← All advisories

CVE-2026-99636

Severity unknownNo known exploitationFix available

net: reject a negative TCP header offset in qdisc_pkt_len_segs_init()

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 6% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

In the Linux kernel, the following vulnerability has been resolved: net: reject a negative TCP header offset in qdisc_pkt_len_segs_init() qdisc_pkt_len_segs_init() stores skb_transport_offset(), or the inner offset, in the unsigned hdr_len. A header in front of skb->data gives a negative offset. For an offset a little below zero, pskb_may_pull() gets a small length and succeeds. Then a 64-bit kernel reads the TCP header far after the skb and can crash. Further below zero pskb_may_pull() fails. Commit 28a57fb2c5df ("net: iptunnel: fix stale transport header during tunnel decapsulation") fixed one source of such offsets. Other code that removes bytes from the front of a packet can leave the same stale header. Return SKB_DROP_REASON_SKB_BAD_GSO for a negative offset in the TCP branch. SKB_GSO_UDP_L4 and the other GSO types read no header and still get a wrong qdisc_pkt_len(). On a 64-bit kernel only packets that cause the read after the skb today get a new result. Then __dev_queue_xmit() drops them and returns -EINVAL, but sch_handle_ingress() ignores the result. Their content can be valid. Thus the code that leaves the header stale needs its own fix.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 6.12.114 before 6.12.1186.12.118CVE Program
LinuxLinuxfrom 6.6.160 before 6.76.7CVE Program
LinuxLinuxfrom 7.0.10 before 7.17.1CVE Program
LinuxLinuxfrom 7564dc804d8289d2e5c6edb8173754051b71bff4 before d88be0067857b68df06a33cc056c9f05101c09d4d88be0067857b68df06a33cc056c9f05101c09d4CVE Program
LinuxLinuxfrom 7fb4c19670110f052c04e1ec1d2b953b9f4f57e4 before 35d2d6e5ac0d22428b2a0216061f3330c095393c35d2d6e5ac0d22428b2a0216061f3330c095393cCVE Program
LinuxLinuxfrom 7fb4c19670110f052c04e1ec1d2b953b9f4f57e4 before 765af9e95c840fcbbecf34ca1e787daba8eac569765af9e95c840fcbbecf34ca1e787daba8eac569CVE Program
LinuxLinux5895cfc76924a629c6eaa5e5f049de642860045fNot documentedCVE Program
LinuxLinux7.1Not documentedCVE Program
LinuxLinux9d4f5c68f5ad4ab425f3ce1500c97c9f9743999aNot documentedCVE Program
LinuxLinux (unaffected)from 6.12.118 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.5 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc2Not documentedCVE Program
LinuxLinux (unaffected)all versions before 7.1Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references