CVE-2026-80615
Last modified
CVE-2026-80615 is a high-severity vulnerability rated 8.2/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: net: dst_metadata: fix false-positive memcpy overflow in tun_dst_unclone kmalloc_flex() in metadata_dst_alloc() sets __counted_by for the structure to the options_len, which is then initialized to zero. Later, we're initializing the structure by copying the tunnel info together with the options, and this triggers a warning for a potential memcpy overflow, since the compiler estimates that the options can't fit into the structure, even though the memory for them is actually allocated. memcpy: detected buffer overflow: 104 byte write of buffer size 96 WARNING: CPU: X PID: Y at lib/string_helpers.c:1036 __fortify_report skb_tunnel_info_unclone+0x179/0x190 geneve_xmit+0x7fe/0xe00 The issue is triggered when built with clang and source fortification. Fix that by doing the copy in two stages: first - the main data with the options_len, then the options. This way the correct length should be known at the time of the copy. It would be better if the options_len never changed after allocation, but the allocation code is a little separate from the initialization and it would be awkward and potentially dangerous to return a struct with options_len set to a non-zero value from the metadata_dst_alloc(). Another option would be to use ip_tunnel_info_opts_set(), but it is doing too many unnecessary operations for the use case here.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: net: dst_metadata: fix false-positive memcpy overflow in tun_dst_unclone kmalloc_flex() in metadata_dst_alloc() sets __counted_by for the structure to the options_len, which is then initialized to zero. Later, we're initializing the structure by copying the tunnel info together with the options, and this triggers a warning for a potential memcpy overflow, since the compiler estimates that the options can't fit into the structure, even though the memory for them is actually allocated. memcpy: detected buffer overflow: 104 byte write of buffer size 96 WARNING: CPU: X PID: Y at lib/string_helpers.c:1036 __fortify_report skb_tunnel_info_unclone+0x179/0x190 geneve_xmit+0x7fe/0xe00 The issue is triggered when built with clang and source fortification. Fix that by doing the copy in two stages: first - the main data with the options_len, then the options. This way the correct length should be known at the time of the copy. It would be better if the options_len never changed after allocation, but the allocation code is a little separate from the initialization and it would be awkward and potentially dangerous to return a struct with options_len set to a non-zero value from the metadata_dst_alloc(). Another option would be to use ip_tunnel_info_opts_set(), but it is doing too many unnecessary operations for the use case here.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 69050f8d6d075dc01af7a5f2f550a8067510366f, < 7ce31739fe88a558370135db95bbeec1e7ddfc29; >= 69050f8d6d075dc01af7a5f2f550a8067510366f, < 4c6d43db2a4d2cef3921e885cf34798f790d34ea |
| Linux | Linux | 7.0 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-80615?
How severe is CVE-2026-80615?
How do I fix CVE-2026-80615?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-80609In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-80610In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80611In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80612In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-80613In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-80614In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-80616In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80617In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-80618In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80619In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-80620In the Linux kernel, the following vulnerability has been re…
- CVE-2026-80621In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-80615?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
