Answer in brief
CVE-2026-74473 records a Unknown severity vulnerability in vxlan: use pskb_network_may_pull() in route_shortcircuit(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e4f67addf158f98f8197e08974966b18480dc751 <42887be7c4cf283cce02cd0fb6411221167c8b6c || >=e4f67addf158f98f8197e08974966b18480dc751 <aa0d31376d574ac858a40078431a77127bf04ee4 || >=e4f67addf158f98f8197e08974966b18480dc751 <ee799977d7941dbfb11049e17edd9eaf4f8820f7 || >=e4f67addf158f98f8197e08974966b18480dc751 <4f3f96e771a20263635bb5e1307c112d613b4bbd || >=e4f67addf158f98f8197e08974966b18480dc751 <26bb2dd0a8839617e2c79ffbbe1923f8e4bab9fb | 42887be7c4cf283cce02cd0fb6411221167c8b6c, aa0d31376d574ac858a40078431a77127bf04ee4, ee799977d7941dbfb11049e17edd9eaf4f8820f7, 4f3f96e771a20263635bb5e1307c112d613b4bbd, 26bb2dd0a8839617e2c79ffbbe1923f8e4bab9fb |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: vxlan: use pskb_network_may_pull() in route_shortcircuit() route_shortcircuit() currently calls pskb_may_pull(skb, sizeof(struct iphdr)) (or ipv6hdr), which checks if bytes are available starting from skb->data. However, in vxlan_xmit(), skb->data points to the MAC header, so skb_network_offset(skb) is ETH_HLEN (14 bytes). Using pskb_may_pull(skb, 20) only checks 20 bytes from skb->data (which is 14 bytes MAC header + 6 bytes of IP header), leaving the rest of the IP header potentially un-pulled in non-linear frags. Subsequent dereferences of ip_hdr(skb)->daddr can read beyond the pulled linear buffer length. Fix this by using pskb_network_may_pull(), which adds skb_network_offset(skb) to the length check to ensure the full network header is present in the linear buffer.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-74473 records a Unknown severity vulnerability in vxlan: use pskb_network_may_pull() in route_shortcircuit(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=e4f67addf158f98f8197e08974966b18480dc751 <42887be7c4cf283cce02cd0fb6411221167c8b6c || >=e4f67addf158f98f8197e08974966b18480dc751 <aa0d31376d574ac858a40078431a77127bf04ee4 || >=e4f67addf158f98f8197e08974966b18480dc751 <ee799977d7941dbfb11049e17edd9eaf4f8820f7 || >=e4f67addf158f98f8197e08974966b18480dc751 <4f3f96e771a20263635bb5e1307c112d613b4bbd || >=e4f67addf158f98f8197e08974966b18480dc751 <26bb2dd0a8839617e2c79ffbbe1923f8e4bab9fb | 42887be7c4cf283cce02cd0fb6411221167c8b6c, aa0d31376d574ac858a40078431a77127bf04ee4, ee799977d7941dbfb11049e17edd9eaf4f8820f7, 4f3f96e771a20263635bb5e1307c112d613b4bbd, 26bb2dd0a8839617e2c79ffbbe1923f8e4bab9fb |
| Linux/Linuxgeneric | 3.8 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
In the Linux kernel, the following vulnerability has been resolved: vxlan: use pskb_network_may_pull() in route_shortcircuit() route_shortcircuit() currently calls pskb_may_pull(skb, sizeof(struct iphdr)) (or ipv6hdr), which checks if bytes are available starting from skb->data. However, in vxlan_xmit(), skb->data points to the MAC header, so skb_network_offset(skb) is ETH_HLEN (14 bytes). Using pskb_may_pull(skb, 20) only checks 20 bytes from skb->data (which is 14 bytes MAC header + 6 bytes of IP header), leaving the rest of the IP header potentially un-pulled in non-linear frags. Subsequent dereferences of ip_hdr(skb)->daddr can read beyond the pulled linear buffer length. Fix this by using pskb_network_may_pull(), which adds skb_network_offset(skb) to the length check to ensure the full network header is present in the linear buffer.
Quoted source text, attributed separately from HOL analysis.