Linux kernel out-of-bounds read in packet scheduler TCP header parsing
- Exploited
- No known exploitation
- Fix
- Fixed in 6.12.118, 6.7, 7.1
- Who is exposed
- Not reported
Summary
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.
What to do
Upgrade to a fixed version: 6.12.118, 6.7, 7.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-99636 (net: reject a negative TCP header offset in qdisc_pkt_len_segs_init()), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-99636 (entry last updated 2026-11-20):
Affected:
- Linux Linux: from 6.12.114, fixed in 6.12.118; from 6.6.160, fixed in 6.7; from 7.0.10, fixed in 7.1
- Linux Linux: versions 7.1
Fixed versions: 6.12.118, 6.7, 7.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-99636 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-99636 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://git.kernel.org/stable/c/d88be0067857b68df06a33cc056c9f05101c09d4
- https://git.kernel.org/stable/c/765af9e95c840fcbbecf34ca1e787daba8eac569
- https://git.kernel.org/stable/c/35d2d6e5ac0d22428b2a0216061f3330c095393c
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-99636
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-99636"}.Affected versions
- Linux LinuxFrom 6.12.114 · fixed in 6.12.118; From 6.6.160 · fixed in 6.7; From 7.0.10 · fixed in 7.1
- Linux Linux7.1
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach20/20Affects Linux kernel (software on nearly every server, desktop or phone)
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 75 if added to CISA KEV
- Would score about 70 if CISA's SSVC rates exploitation active
- Would score about 42 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-99636 |
| Record | NVD · CVE-2026-99636 |
| Other links 3 | |
| Link | git.kernel.org · stable/c/d88be0067857b68df06a33cc056c9f05101c09d4 |
| Link | git.kernel.org · stable/c/765af9e95c840fcbbecf34ca1e787daba8eac569 |
| Link | git.kernel.org · stable/c/35d2d6e5ac0d22428b2a0216061f3330c095393c |
Questions about CVE-2026-99636
Is CVE-2026-99636 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-99636?
Linux: from 6.12.114 before 6.12.118; from 6.6.160 before 6.7; from 7.0.10 before 7.1. Linux: version 7.1.
Source: cve.now feed data
How do I fix CVE-2026-99636?
Upgrade to a fixed version: 6.12.118, 6.7, 7.1.
Source: cve.now feed data
Related
- CVE-2026-99804io_uring/io-wq: save worker type before dropping its reference
- CVE-2026-99803io_uring/net: mask socket type with SOCK_TYPE_MASK in io_socket_bpf_populate()
- CVE-2026-99802io_uring/register: enforce per-task restrictions in io_uring_register_blind()
- CVE-2026-99801io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
- CVE-2026-99800io_uring: free the task context after a grace period
- CVE-2026-99799io_uring/sqpoll: don't wait for the thread to exit
No corrections so far. Something wrong on this page? Report an error.