CVSS 3.1
8.2 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:HHigh (8.2) in linux linux. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:HExplain CVE-2026-80615 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-80615?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-80615?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-80615 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 7.0 and later |
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 7.1 | 7.1.5 |
| Linux | later releases | 7.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 14 | linux | 7.1.5-1 | DEBIAN-CVE-2026-80615 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-80615 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-80615 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-80615 |
| Ubuntu | 22.04:LTS | linux-riscv, linux-aws-6.2, linux-aws-6.5 and 30 more | no fix listed | UBUNTU-CVE-2026-80615 |
| Ubuntu | 24.04:LTS | linux-aws-7.0, linux-gcp-7.0 | 7.0.0-1014.14~24.04.1 | UBUNTU-CVE-2026-80615 USN-8887-2 USN-8887-3 |
| Ubuntu | 24.04:LTS | linux-azure-7.0 | 7.0.0-1017.17~24.04.1 | UBUNTU-CVE-2026-80615 USN-8888-2 |
| Ubuntu | 24.04:LTS | linux-azure-fde-7.0 | 7.0.0-1016.16~24.04.1 | UBUNTU-CVE-2026-80615 USN-8888-2 |
| Ubuntu | 24.04:LTS | linux-hwe-7.0 | 7.0.0-38.38~24.04.4 | UBUNTU-CVE-2026-80615 USN-8887-3 |
| Ubuntu | 24.04:LTS | linux-nvidia-7.0 | 7.0.0-1024.25~24.04.1 | UBUNTU-CVE-2026-80615 USN-9003-1 |
| Ubuntu | 24.04:LTS | linux-oracle-7.0 | 7.0.0-1013.13~24.04.1 | UBUNTU-CVE-2026-80615 USN-8887-3 |
| Ubuntu | 24.04:LTS | linux-riscv, linux-oem-6.8, linux-aws-6.14 and 22 more | no fix listed | UBUNTU-CVE-2026-80615 |
| Ubuntu | 24.04:LTS | linux-riscv-7.0 | 7.0.0-38.38.1~24.04.1 | UBUNTU-CVE-2026-80615 |
| 12 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Red Hat rates this Moderate.
A moderate-impact flaw was found in the Linux kernel's dst_metadata tunnel metadata handling, affecting the kernel and kernel-rt packages in Red Hat Enterprise Linux 9.9, 9.10, 10.3, and 10.4, and the kernel packages in Red Hat In-Vehicle OS 2.0 and 2.1. When a kernel is built with clang and source fortification enabled, tun_dst_unclone() initializes tunnel metadata by copying the tunnel information together with its options in a single memcpy. Because the flexible-array member's __counted_by length (options_len) is still zero at that point, the fortified memcpy logic reports a potential buffer overflow, even though the memory for the options was correctly allocated; the reported overflow is a false positive and no out-of-bounds write actually occurs. The practical consequence is a misleading kernel fortify WARNING and diagnostics (for example when transmitting through a geneve tunnel) rather than memory corruption, which Red Hat's moderate rating (CVSS 5.5, local vector, availability-only impact) reflects. The CVE.org score of 8.2 with a network attack vector overstates the risk because the underlying condition is a compiler-side false positive rather than a remotely exploitable overflow. Fixes for the affected streams are currently deferred because the issue does not cause actual memory corruption, and the residual risk of deferral is limited to spurious fortify warnings in the kernel log when tunnel options are cloned on affected build configurations. RHEL 7, RHEL 8, the RHEL 9.2 through 9.8 z-streams, RHEL 10.0.z and 10.2.z, and the OpenShift Container Platform RHCOS streams are marked not affected because the vulnerable code is not present, and RHEL 6 ELS is out of support scope.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 6 | kernel | Out of support scope | |
| Red Hat Enterprise Linux 7 | kernel | Not affected | |
| Red Hat Enterprise Linux 7 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 8 | kernel | Not affected | |
| Red Hat Enterprise Linux 8 | kernel-rt | Not affected | |
| Red Hat Enterprise Linux 9 | kernel | Fix deferred | |
| Red Hat Enterprise Linux 9 | kernel-rt | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Not affected | |
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Not affected | |
| Red Hat OpenShift Container Platform 5 | openshift/ose-rhel-coreos-9 | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-80615.