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-99767xfrm4: use a full socket for local errors

Description

In the Linux kernel, the following vulnerability has been resolved: xfrm4: use a full socket for local errors xfrm4_local_error() passes skb->sk to inet_sk() and ip_local_error() without ensuring it points to a full socket. TCP SYN-ACK skbs can be owned by TCP_NEW_SYN_RECV request sockets. xfrm4_tunnel_check_size() already checks sk_fullsock() since commit 1620c88887b1 ("xfrm: Fix the usage of skb->sk"), so iptfs_is_too_big() is the only remaining IPv4 caller passing a request socket here: the sk it tests is the listener, while skb->sk is the request socket. When IP-TFS rejects such an skb because it exceeds its payload MTU, the local error path treats the request socket as a struct inet_sock. KASAN reports a slab-out-of-bounds read in ip_local_error() beyond the request_sock_TCP allocation. Resolve the skb owner with skb_to_full_sk() before accessing inet_sock state or reporting the error. This maps a request socket to its listener and rejects sockets that cannot be used as full sockets, matching what commit 6973a21ee73c ("ipv6: xfrm: use full sockets in local error paths") did for xfrm6_local_error().

Timeline

  1. ID reserved

    By Linux

  2. · 56 days later

    Published

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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE.

EPSS (exploitation in 30 days)
Not scored

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

Affected products

  • Linux · Linux

    • affected 0e4fbf013fa566f274ce9b4ce698c75b1f998c52 – < 21ba931b2eec642b1c440e0b6eccc2d80f945060
    • affected 0e4fbf013fa566f274ce9b4ce698c75b1f998c52 – < e465b8f50337d0fb3b9753be6cb9fcac79800046
    • affected 0e4fbf013fa566f274ce9b4ce698c75b1f998c52 – < 5def91015ba7b59de62a81384572da7281b8a033
  • Linux · Linux

    • affected 6.14
    • unaffected < 6.14
    • unaffected 6.18.64 – ≤ 6.18.*
    • unaffected 7.3.5 – ≤ 7.3.*
    • unaffected 7.4-rc2 – ≤ *

References

References3

Sources

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

Badge for a README or a ticket

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

Record last updated .