CVE-2026-90078net/sched: act_skbmod: fix length calculations and avoid invalid header warnings
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- Not yet scored
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Sep 17, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 56af5e749f20c3a540310c207dcc373f4f09156e before 985a37781ade19061400100c2ba0f43979dd4d63; from 56af5e749f20c3a540310c207dcc373f4f09156e before d896843d8d925f0adbba319020595cfb1a7bcd57; from 56af5e749f20c3a540310c207dcc373f4f09156e before 0675cff3c2924eb9b80d9dd250cf56a1140af157; from 56af5e749f20c3a540310c207dcc373f4f09156e before e8a2027b7e686784a69b2dfcee841d779919f313; from 56af5e749f20c3a540310c207dcc373f4f09156e before 1719865b20b22c88d2a55e922eff5ca31b0841f6; from 56af5e749f20c3a540310c207dcc373f4f09156e before 62126464f3a6159c0a3dd89e196ba65bfeb0afc6; from 56af5e749f20c3a540310c207dcc373f4f09156e before 81d0d1e64f30d9989c829c0953cd6e6c68d9c5fb | CNA record |
References
- https://git.kernel.org/stable/c/985a37781ade19061400100c2ba0f43979dd4d63
- https://git.kernel.org/stable/c/d896843d8d925f0adbba319020595cfb1a7bcd57
- https://git.kernel.org/stable/c/0675cff3c2924eb9b80d9dd250cf56a1140af157
- https://git.kernel.org/stable/c/e8a2027b7e686784a69b2dfcee841d779919f313
- https://git.kernel.org/stable/c/1719865b20b22c88d2a55e922eff5ca31b0841f6
- https://git.kernel.org/stable/c/62126464f3a6159c0a3dd89e196ba65bfeb0afc6
- https://git.kernel.org/stable/c/81d0d1e64f30d9989c829c0953cd6e6c68d9c5fb
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.