CVE-2025-38591
Last modified
CVE-2025-38591 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: bpf: Reject narrower access to pointer ctx fields The following BPF program, simplified from a syzkaller repro, causes a kernel warning: r0 = *(u8 *)(r1 + 169); exit; With pointer field sk being at offset 168 in __sk_buff. This access is detected as a narrower read in bpf_skb_is_valid_access because it doesn't match offsetof(struct __sk_buff, sk). EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: bpf: Reject narrower access to pointer ctx fields The following BPF program, simplified from a syzkaller repro, causes a kernel warning: r0 = *(u8 *)(r1 + 169); exit; With pointer field sk being at offset 168 in __sk_buff. This access is detected as a narrower read in bpf_skb_is_valid_access because it doesn't match offsetof(struct __sk_buff, sk). It is therefore allowed and later proceeds to bpf_convert_ctx_access. Note that for the "is_narrower_load" case in the convert_ctx_accesses(), the insn->off is aligned, so the cnt may not be 0 because it matches the offsetof(struct __sk_buff, sk) in the bpf_convert_ctx_access. However, the target_size stays 0 and the verifier errors with a kernel warning: verifier bug: error during ctx access conversion(1) This patch fixes that to return a proper "invalid bpf_context access off=X size=Y" error on the load instruction. The same issue affects multiple other fields in context structures that allow narrow access. Some other non-affected fields (for sk_msg, sk_lookup, and sockopt) were also changed to use bpf_ctx_range_ptr for consistency. Note this syzkaller crash was reported in the "Closes" link below, which used to be about a different bug, fixed in commit fce7bd8e385a ("bpf/verifier: Handle BPF_LOAD_ACQ instructions in insn_def_regno()"). Because syzbot somehow confused the two bugs, the new crash and repro didn't get reported to the mailing list.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 4.13, < 6.16.1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2025-38591?
How severe is CVE-2025-38591?
How do I fix CVE-2025-38591?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-38586In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38587In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38588In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38589In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3859Websites directing users to long URLs that caused eliding to…6.1
- CVE-2025-38590In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-38592In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2025-38593In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38594In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38595In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38596In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-38597In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2025-38591?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
