Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80738bpf: Check sk_state before sk_protocol in bpf_tcp_*_syncookie

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 8 days later

    Published

  3. · 57 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-80738, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
NVDNVD · Received3.1High7.3CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.3.

Affected products

  • Linux · Linux

    • affected 399040847084a69f345e0a52fd62f04654e0fce3 – < b75f1c071f31be7f4b950721e04240c250091ad4
    • affected 399040847084a69f345e0a52fd62f04654e0fce3 – < 5702e4c259809c760912c477c4ae34e9217bb4d9
    • affected 399040847084a69f345e0a52fd62f04654e0fce3 – < b5525e853a2a08a9559adb84b0616025958dc542
    • affected 399040847084a69f345e0a52fd62f04654e0fce3 – < 22c2169770ad3b3595690e51caac875178cf496d
    • affected 399040847084a69f345e0a52fd62f04654e0fce3 – < 23f682083aa3fbc0c49667818efd6979a8bc5ac2
    • affected 399040847084a69f345e0a52fd62f04654e0fce3 – < 31a420a822ff92e2090bd5d65efe8e34e2d6d9b8
  • Linux · Linux

    • affected 5.2
    • unaffected < 5.2
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.1.9 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80738 badge
[![CVE-2026-80738](https://cveledger.app/badge/CVE-2026-80738.svg)](https://cveledger.app/cve/CVE-2026-80738)

Record last updated .