bpf: Explicitly check accesses to bpf_sock_addr
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 5.10.246, 5.15.195, 5.4.301, 6.1.156, 6.12.53, 6.17.3, 6.6.112
- CVEs
- CVE-2025-40078
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 05:06 UTC · Revision 1
Source evidence
bpf: Explicitly check accesses to bpf_sock_addr
core-osv · Original sourcePublished 28 Oct 2025, 11:48 UTC
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.
osv:CVE-2025-40078
Kernel
Fixed versions: 5.4.301, 5.10.246, 5.15.195, 6.1.156, 6.6.112, 6.12.53, 6.17.3
Complete source record
{
"id": "93114348636b36d448ed502ce1c3538197f188a25b5f9534b6f892f10f48c35c",
"url": "https://osv.dev/vulnerability/CVE-2025-40078",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "bpf: Explicitly check accesses to bpf_sock_addr",
"summary": "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.",
"evidence": "osv:CVE-2025-40078",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.4.301",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.246",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.195",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.156",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.112",
"evidence": "/affected/1/ranges"
},
{
"value": "6.12.53",
"evidence": "/affected/1/ranges"
},
{
"value": "6.17.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2025-40078",
"aliases": [
"CVE-2025-40078"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "1cedee13d25ab118d325f95588c1a084e9317229"
},
{
"fixed": "de44cdc50d2dce8718cb57deddf9cf1be9a7759f"
},
{
"fixed": "76e04bbb4296fb6eac084dbfc27e02ccc744db3e"
},
{
"fixed": "6d8b1a21fd5c34622b0c3893c61e4a38d8ba53ec"
},
{
"fixed": "4f00858cd9bbbdf67159e28b85a8ca9e77c83622"
},
{
"fixed": "cdeafacb4f9ff261a96baef519e29480fd7b1019"
},
{
"fixed": "fe9d33f0470350558cb08cecb54cf2267b3a45d2"
},
{
"fixed": "ad8b4fe5617e3c85fc23267f02500c4f3bf0ff69"
},
{
"fixed": "6fabca2fc94d33cdf7ec102058983b086293395f"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-40078.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.18.0"
},
{
"fixed": "5.4.301"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.246"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.195"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.156"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.112"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.12.53"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.13.0"
},
{
"fixed": "6.17.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-40078.json"
}
}
],
"modified": "2026-10-28T02:30:26.076285648Z",
"provider": "osv",
"references": [
"https://cert-portal.siemens.com/productcert/html/ssa-019113.html",
"https://cert-portal.siemens.com/productcert/html/ssa-457936.html",
"https://git.kernel.org/stable/c/4f00858cd9bbbdf67159e28b85a8ca9e77c83622",
"https://git.kernel.org/stable/c/6d8b1a21fd5c34622b0c3893c61e4a38d8ba53ec",
"https://git.kernel.org/stable/c/6fabca2fc94d33cdf7ec102058983b086293395f",
"https://git.kernel.org/stable/c/76e04bbb4296fb6eac084dbfc27e02ccc744db3e",
"https://git.kernel.org/stable/c/ad8b4fe5617e3c85fc23267f02500c4f3bf0ff69",
"https://git.kernel.org/stable/c/cdeafacb4f9ff261a96baef519e29480fd7b1019",
"https://git.kernel.org/stable/c/de44cdc50d2dce8718cb57deddf9cf1be9a7759f",
"https://git.kernel.org/stable/c/fe9d33f0470350558cb08cecb54cf2267b3a45d2",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/40xxx/CVE-2025-40078.json",
"https://nvd.nist.gov/vuln/detail/CVE-2025-40078",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/40xxx/CVE-2025-40078.json"
}
},
"related_cves": [
{
"value": "CVE-2025-40078",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 492644,
"published_at": "2025-10-28T11:48:43.548+00:00"
}