Strix
26.1K

CVE-2025-40078

UnknownEPSS 0.20%

Last modified

CVE-2025-40078 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.20% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.20%

9.6th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 1cedee13d25ab118d325f95588c1a084e9317229, < de44cdc50d2dce8718cb57deddf9cf1be9a7759f; >= 1cedee13d25ab118d325f95588c1a084e9317229, < 76e04bbb4296fb6eac084dbfc27e02ccc744db3e; >= 1cedee13d25ab118d325f95588c1a084e9317229, < 6d8b1a21fd5c34622b0c3893c61e4a38d8ba53ec; >= 1cedee13d25ab118d325f95588c1a084e9317229, < 4f00858cd9bbbdf67159e28b85a8ca9e77c83622; >= 1cedee13d25ab118d325f95588c1a084e9317229, < cdeafacb4f9ff261a96baef519e29480fd7b1019; >= 1cedee13d25ab118d325f95588c1a084e9317229, < fe9d33f0470350558cb08cecb54cf2267b3a45d2; >= 1cedee13d25ab118d325f95588c1a084e9317229, < ad8b4fe5617e3c85fc23267f02500c4f3bf0ff69; >= 1cedee13d25ab118d325f95588c1a084e9317229, < 6fabca2fc94d33cdf7ec102058983b086293395f
LinuxLinux4.18

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-40078?
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.
How severe is CVE-2025-40078?
Severity scoring for CVE-2025-40078 is pending analysis. The EPSS model estimates a 0.20% probability of exploitation in the next 30 days.
How do I fix CVE-2025-40078?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

View all 2025CVEs →

Are you affected by CVE-2025-40078?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST