Answer in brief
CVE-2026-98568 records a Unknown severity vulnerability in vxlan: use one headroom snapshot for neighbour replies. 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 | >=4b29dba9c085a4fb79058fb1c45a2f6257ca3dfa <45a67662bf8ce3aa5643accf98d328dfbb47eaf6 || >=4b29dba9c085a4fb79058fb1c45a2f6257ca3dfa <315d42ca39f69846662961c25dcf2bb07c350d14 || >=4b29dba9c085a4fb79058fb1c45a2f6257ca3dfa <a3c5eb6e382dd426a5e7eb08608897ed57167ff7 || >=4b29dba9c085a4fb79058fb1c45a2f6257ca3dfa <ff022fd9d0f0282c575e11778b96bd1b637503eb || >=4b29dba9c085a4fb79058fb1c45a2f6257ca3dfa <481506a756dcd828ef42391cb08f38d8d96d38fc || d8be18c52dbc94989f6d74637b731af39cd3d902 || 3927dace523706cc00f808520eaf2125dd7c07b5 || >=3.12.18 <3.13 || >=3.13.10 <3.14 | 45a67662bf8ce3aa5643accf98d328dfbb47eaf6, 315d42ca39f69846662961c25dcf2bb07c350d14, a3c5eb6e382dd426a5e7eb08608897ed57167ff7, ff022fd9d0f0282c575e11778b96bd1b637503eb, 481506a756dcd828ef42391cb08f38d8d96d38fc, 3.13, 3.14 |
| Linux/Linuxgeneric | 3.14 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
In the Linux kernel, the following vulnerability has been resolved: vxlan: use one headroom snapshot for neighbour replies vxlan_na_create() samples LL_RESERVED_SPACE() to size the reply skb and then samples it again to reserve headroom. A concurrent vxlan_changelink() can update needed_headroom between the two reads, creating a TOCTOU race. The second value can exceed the allocation and make the Ethernet header write out of bounds. The race is reproducible on the unpatched kernel. It occurred when vxlan_na_create() generated a neighbour reply while vxlan_changelink() changed the link headroom. KASAN caught a four-byte write two bytes beyond a 704-byte skbuff_small_head allocation. Snapshot the headroom once and use that value for both allocation and reservation.
Quoted source text, attributed separately from HOL analysis.