CVE-2026-90078 — net/sched: act_skbmod: fix length calculations and avoid invalid header warnings
In the Linux kernel, the following vulnerability has been resolved: net/sched: act_skbmod: fix length calculations and avoid invalid header warnings syzbot reported a warning in skb_network_header_len() triggered by tcf_skbmod_act(): !skb_transport_header_was_set(skb) WARNING: CPU: 0 PID: 14949 at include/linux/skbuff.h:3243 skb_network_header_len include/linux/skbuff.h:3243 [inline] WARNING: CPU: 0 PID: 14949 at net/sched/act_skbmod.c:55 tcf_skbmod_act+0xfe8/0x1810 net/sched/act_skbmod.c:55 There are a few issues in tcf_skbmod_act(): 1. Calling skb_network_header_len() assumes skb->transport_header is set, which is not guaranteed when tcf_skbmod_act() runs at TC ingress. 2. Unconditionally calling skb_mac_header_len() at the beginning of tcf_skbmod_act() triggers a warning on L3 devices (e.g. TUN) where the MAC header is unset, evaluating to an underflowed garbage length. 3. On TC ingress, skb->data points to the network header. Adding the MAC header length to the IP header length causes skb_ensure_writable() to request more bytes than the actual IP packet length, dropping valid short packets (e.g. 28-byte UDP/IPv4 packets). Fix these by: - Using skb_network_offset(skb) + sizeof(struct iphdr/ipv6hdr) for SKBMOD_F_ECN so that the required length is correctly calculated on both ingress (offset == 0) and egress (offset == mac_len). - Setting max_edit_len to ETH_HLEN for Ethernet header modifications after validating ARPHRD_ETHER.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux | ≥ 56af5e749f20c3a540310c207dcc373f4f09156e and < 985a37781ade19061400100c2ba0f43979dd4d63≥ 56af5e749f20c3a540310c207dcc373f4f09156e and < d896843d8d925f0adbba319020595cfb1a7bcd57≥ 56af5e749f20c3a540310c207dcc373f4f09156e and < 0675cff3c2924eb9b80d9dd250cf56a1140af157≥ 56af5e749f20c3a540310c207dcc373f4f09156e and < e8a2027b7e686784a69b2dfcee841d779919f313≥ 56af5e749f20c3a540310c207dcc373f4f09156e and < 1719865b20b22c88d2a55e922eff5ca31b0841f6≥ 56af5e749f20c3a540310c207dcc373f4f09156e and < 62126464f3a6159c0a3dd89e196ba65bfeb0afc6≥ 56af5e749f20c3a540310c207dcc373f4f09156e and < 81d0d1e64f30d9989c829c0953cd6e6c68d9c5fbversion 5.15 | Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 18, 2026 · 3 reading(s) · max 0.21%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
9 on the record
- git.kernel.org/stable/c/d896843d8d925f0adbba319020595cfb1a7bcd57
- github.com/advisories/GHSA-4hxp-vhhr-h77f
- git.kernel.org/stable/c/985a37781ade19061400100c2ba0f43979dd4d63
- nvd.nist.gov/vuln/detail/CVE-2026-90078
- git.kernel.org/stable/c/0675cff3c2924eb9b80d9dd250cf56a1140af157
- git.kernel.org/stable/c/81d0d1e64f30d9989c829c0953cd6e6c68d9c5fb
- git.kernel.org/stable/c/e8a2027b7e686784a69b2dfcee841d779919f313
- git.kernel.org/stable/c/1719865b20b22c88d2a55e922eff5ca31b0841f6
- git.kernel.org/stable/c/62126464f3a6159c0a3dd89e196ba65bfeb0afc6
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-98866 sched/cache: Introduce task_struct->sched_cache_grp to fix UAF 1d
- Unknown CVE-2026-98867 dm-pcache: bound the logical key offset from persistent memory 1d
- Unknown CVE-2026-98868 dm-pcache: reject a kset that overruns its segment 1d
- Unknown CVE-2026-98856 kprobes: Skip disarmed probes when checking optkprobe overlap 1d
- Unknown CVE-2026-98857 ipvs: bound LBLCR and LBLC cache growth 1d
- Unknown CVE-2026-98858 io_uring: fix task_work add use-after-free with SQPOLL 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-90078 is "net/sched: act_skbmod: fix length calculations and avoid invalid header warnings", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.