CVE Tools

CVE-2026-80738

bpf: Check sk_state before sk_protocol in bpf_tcp_*_syncookie

No known exploitation. EPSS puts it in the 7th percentile. Fixed versions are out.

Check it yourself

No ready-made check. Neither Nuclei nor OpenVAS has one for this CVE yet.

Request a scan

Published Updated Sources: CVE.org, NVD

What to do

Find your product and version, then upgrade to the build on the right.

  • LinuxAffected: ≥ 399040847084a69f345e0a52fd62f04654e0fce3, < b75f1c071f31be7f4b950721e04240c250091ad4Upgrade to: b75f1c071f31be7f4b950721e04240c250091ad4Affected: ≥ 399040847084a69f345e0a52fd62f04654e0fce3, < 5702e4c259809c760912c477c4ae34e9217bb4d9Upgrade to: 5702e4c259809c760912c477c4ae34e9217bb4d9Affected: ≥ 399040847084a69f345e0a52fd62f04654e0fce3, < b5525e853a2a08a9559adb84b0616025958dc542Upgrade to: b5525e853a2a08a9559adb84b0616025958dc542Affected: ≥ 399040847084a69f345e0a52fd62f04654e0fce3, < 22c2169770ad3b3595690e51caac875178cf496dUpgrade to: 22c2169770ad3b3595690e51caac875178cf496d + 2 more branchesStated by: CVE record

Versions as the sources state them. Full version matrix after sign-in

What it is

From the CVE record

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.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS7th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.2% chance of exploitation activity in the next 30 days, which ranks it in the 7th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

6 events over 57 days, from the signal feeds we watch.

  1. Record updated
  2. Record updated
  3. Record updated
  4. Record updated
  5. Publishedrecord updated

Affected products

Technical detail

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Scored 7.3 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability LowReduced performance or intermittent disruption of service

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Linux, not every advisory.