Answer in brief
CVE-2025-40078 records a Unknown severity vulnerability in bpf: Explicitly check accesses to bpf_sock_addr. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (generic), Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=1cedee13d25ab118d325f95588c1a084e9317229 <de44cdc50d2dce8718cb57deddf9cf1be9a7759f || >=1cedee13d25ab118d325f95588c1a084e9317229 <76e04bbb4296fb6eac084dbfc27e02ccc744db3e || >=1cedee13d25ab118d325f95588c1a084e9317229 <6d8b1a21fd5c34622b0c3893c61e4a38d8ba53ec || >=1cedee13d25ab118d325f95588c1a084e9317229 <4f00858cd9bbbdf67159e28b85a8ca9e77c83622 || >=1cedee13d25ab118d325f95588c1a084e9317229 <cdeafacb4f9ff261a96baef519e29480fd7b1019 || >=1cedee13d25ab118d325f95588c1a084e9317229 <fe9d33f0470350558cb08cecb54cf2267b3a45d2 || >=1cedee13d25ab118d325f95588c1a084e9317229 <ad8b4fe5617e3c85fc23267f02500c4f3bf0ff69 || >=1cedee13d25ab118d325f95588c1a084e9317229 <6fabca2fc94d33cdf7ec102058983b086293395f | de44cdc50d2dce8718cb57deddf9cf1be9a7759f, 76e04bbb4296fb6eac084dbfc27e02ccc744db3e, 6d8b1a21fd5c34622b0c3893c61e4a38d8ba53ec, 4f00858cd9bbbdf67159e28b85a8ca9e77c83622, cdeafacb4f9ff261a96baef519e29480fd7b1019, fe9d33f0470350558cb08cecb54cf2267b3a45d2, ad8b4fe5617e3c85fc23267f02500c4f3bf0ff69, 6fabca2fc94d33cdf7ec102058983b086293395f |
| Linux/Linuxgeneric | 4.18 | Not reported |
| Siemens/SIMATIC S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIMATIC S7-1500 CPU 1518F-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
| Siemens/SIPLUS S7-1500 CPU 1518-4 PN/DP MFPgeneric | >=V3.1.6 <* | * |
Published upstream
Oct 28, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 14, 2026
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.
Quoted source text, attributed separately from HOL analysis.