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-2025-40078bpf: Explicitly check accesses to bpf_sock_addr

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Explicitly check accesses to bpf_sock_addr Syzkaller found a kernel warning on the following sock_addr program: 0: r0 = 0 1: r2 = *(u32 *)(r1 +60) 2: exit which triggers: verifier bug: error during ctx access conversion (0) This is happening because offset 60 in bpf_sock_addr corresponds to an implicit padding of 4 bytes, right after msg_src_ip4. Access to this padding isn't rejected in sock_addr_is_valid_access and it thus later fails to convert the access. This patch fixes it by explicitly checking the various fields of bpf_sock_addr in sock_addr_is_valid_access. I checked the other ctx structures and is_valid_access functions and didn't find any other similar cases. Other cases of (properly handled) padding are covered in new tests in a subsequent patch.

Timeline

  1. ID reserved

    By Linux

  2. · 7 months later

    Published

  3. · 13 months 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

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

EPSS (exploitation in 30 days)
0.24% · top 84% of all CVEs (17 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1cedee13d25ab118d325f95588c1a084e9317229 – < de44cdc50d2dce8718cb57deddf9cf1be9a7759f
    • affected 1cedee13d25ab118d325f95588c1a084e9317229 – < 76e04bbb4296fb6eac084dbfc27e02ccc744db3e
    • affected 1cedee13d25ab118d325f95588c1a084e9317229 – < 6d8b1a21fd5c34622b0c3893c61e4a38d8ba53ec
    • affected 1cedee13d25ab118d325f95588c1a084e9317229 – < 4f00858cd9bbbdf67159e28b85a8ca9e77c83622
    • affected 1cedee13d25ab118d325f95588c1a084e9317229 – < cdeafacb4f9ff261a96baef519e29480fd7b1019
    • affected 1cedee13d25ab118d325f95588c1a084e9317229 – < fe9d33f0470350558cb08cecb54cf2267b3a45d2
    • affected 1cedee13d25ab118d325f95588c1a084e9317229 – < ad8b4fe5617e3c85fc23267f02500c4f3bf0ff69
    • affected 1cedee13d25ab118d325f95588c1a084e9317229 – < 6fabca2fc94d33cdf7ec102058983b086293395f
  • Linux · Linux

    • affected 4.18
    • unaffected < 4.18
    • unaffected 5.4.301 – ≤ 5.4.*
    • unaffected 5.10.246 – ≤ 5.10.*
    • unaffected 5.15.195 – ≤ 5.15.*
    • unaffected 6.1.156 – ≤ 6.1.*
    • unaffected 6.6.112 – ≤ 6.6.*
    • unaffected 6.12.53 – ≤ 6.12.*
    • unaffected 6.17.3 – ≤ 6.17.*
    • unaffected 6.18 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .