CVE-2026-80738 json
bpf: Check sk_state before sk_protocol in bpf_tcp_*_syncookie
published 2026-09-03 2 mo ago modified 2026-10-30 10 d ago also EUVD-2026-70342
- cvss
- 7.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
bpf: Check sk_state before sk_protocol in bpf_tcp_*_syncookie
bpf_tcp_gen_syncookie and bpf_tcp_check_syncookie accept a socket pointer 'sk' with argument type ARG_PTR_TO_BTF_ID_SOCK_COMMON. However, they access sk->sk_protocol without validating whether 'sk' represents a full socket.
Fix this issue by checking sk->sk_state != TCP_LISTEN before inspecting sk->sk_protocol in both bpf_tcp_gen_syncookie and bpf_tcp_check_syncookie. Since mini-sockets are never in the TCP_LISTEN state, the condition short-circuits and prevents dereferencing fullsock-specific fields.
Patch / fix
- Linux Linux 6.1.191, 6.6.160, 6.12.114, 6.18.57, 7.1.9, 7.2
- linux Debian 13 6.12.115-2
- linux Debian 14 7.1.9-1
debian advisories DEBIAN-CVE-2026-80738
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1017.17
- linux-riscv Ubuntu 26.04 LTS 7.0.0-42.42.1
- linux-oracle Ubuntu 26.04 LTS 7.0.0-1015.16
- linux-hwe-7.0 Ubuntu 24.04 LTS 7.0.0-42.42~24.04.1
- linux-oem-7.0 Ubuntu 26.04 LTS 7.0.0-1017.17
ubuntu advisories UBUNTU-CVE-2026-80738
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/b75f1c071f31be7f4b950721e04240c250091ad4 commit
- git.kernel.org/stable/c/5702e4c259809c760912c477c4ae34e9217bb4d9 commit
- git.kernel.org/stable/c/b5525e853a2a08a9559adb84b0616025958dc542 commit
- git.kernel.org/stable/c/22c2169770ad3b3595690e51caac875178cf496d commit
- git.kernel.org/stable/c/23f682083aa3fbc0c49667818efd6979a8bc5ac2 commit
- git.kernel.org/stable/c/31a420a822ff92e2090bd5d65efe8e34e2d6d9b8 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-80738 updated cvss 5.5
kernel: bpf: Check sk_state before sk_protocol in bpf_tcp_*_syncookie
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/b75f1c071f31be7f4b950721e04240c250091ad4
- git.kernel.org /stable/c/5702e4c259809c760912c477c4ae34e9217bb4d9
- git.kernel.org /stable/c/b5525e853a2a08a9559adb84b0616025958dc542
- git.kernel.org /stable/c/22c2169770ad3b3595690e51caac875178cf496d
- git.kernel.org /stable/c/23f682083aa3fbc0c49667818efd6979a8bc5ac2
- git.kernel.org /stable/c/31a420a822ff92e2090bd5d65efe8e34e2d6d9b8
Sources
- CVE List CVE-2026-80738
- NVD CVE-2026-80738
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.