Kernel memory corruption via neighbor-reply headroom race
Published Oct 18, 2026 · Updated Oct 18, 2026
A headroom race in Linux VXLAN allows attackers to corrupt kernel memory while neighbor replies overlap link reconfiguration. The vxlan_na_create() function reads LL_RESERVED_SPACE() separately for buffer allocation and headroom reservation; vxlan_changelink() can increase needed_headroom between those reads, causing an out-of-bounds Ethernet-header write. Triggering requires concurrent VXLAN neighbor-reply generation and link-headroom changes; the published evidence demonstrates memory corruption, not code execution or privilege escalation.
Summary
What happened
A headroom race in Linux VXLAN allows attackers to corrupt kernel memory while neighbor replies overlap link reconfiguration. The vxlan_na_create() function reads LL_RESERVED_SPACE() separately for buffer allocation and headroom reservation; vxlan_changelink() can increase needed_headroom between those reads, causing an out-of-bounds Ethernet-header write. Triggering requires concurrent VXLAN neighbor-reply generation and link-headroom changes; the published evidence demonstrates memory corruption, not code execution or privilege escalation.
The record
- CVE
- CVE-2026-98568
- Published
- Oct 18, 2026
- Updated
- Oct 18, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 18, 2026CVE publishedPublication date reported by the CVE source.
- Oct 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.12.18 <3.13
- Affected versionversion=3.13.10 <3.14
- Affected versionversion=3.14
- Affected versionversion=3927dace523706cc00f808520eaf2125dd7c07b5
- Affected versionversion=4b29dba9c085a4fb79058fb1c45a2f6257ca3dfa <315d42ca39f69846662961c25dcf2bb07c350d14
- Affected versionversion=4b29dba9c085a4fb79058fb1c45a2f6257ca3dfa <45a67662bf8ce3aa5643accf98d328dfbb47eaf6
- Affected versionversion=4b29dba9c085a4fb79058fb1c45a2f6257ca3dfa <481506a756dcd828ef42391cb08f38d8d96d38fc
- Affected versionversion=4b29dba9c085a4fb79058fb1c45a2f6257ca3dfa <a3c5eb6e382dd426a5e7eb08608897ed57167ff7
- Affected versionversion=4b29dba9c085a4fb79058fb1c45a2f6257ca3dfa <ff022fd9d0f0282c575e11778b96bd1b637503eb
- Affected versionversion=d8be18c52dbc94989f6d74637b731af39cd3d902
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started