CVE-2025-38591

bpf: Reject narrower access to pointer ctx fields

State
Published
Severity
Not scored
Published
Aug 19, 2025
Updated
Oct 15, 2026
Reserved
Apr 16, 2025

Read the record on cve.org

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • f96da09473b52c09125cc9bf7d7d4576ae8229e0 to before 7847c4140e06f6e87229faae22cc38525334c156Affected
  • f96da09473b52c09125cc9bf7d7d4576ae8229e0 to before feae34c992eb7191862fb1594c704fbbf650fef8Affected
  • f96da09473b52c09125cc9bf7d7d4576ae8229e0 to before 33660d44e789edb4f303210c813fc56d56377a90Affected
  • f96da09473b52c09125cc9bf7d7d4576ae8229e0 to before e2e9599f3503df7cf3569d2b6c50d5488fb59435Affected
  • f96da09473b52c09125cc9bf7d7d4576ae8229e0 to before 058a0da4f6d916a79b693384111bb80a90d73763Affected
  • f96da09473b52c09125cc9bf7d7d4576ae8229e0 to before 202900ceeef67458c964c2af6e1427c8e533ea7cAffected
  • f96da09473b52c09125cc9bf7d7d4576ae8229e0 to before e09299225d5ba3916c91ef70565f7d2187e4cca0Affected
LinuxLinux
  • 4.13Affected
  • before 4.13Not affected
  • 5.10.249 through 5.10.*Not affected
  • 5.15.199 through 5.15.*Not affected
  • 6.1.162 through 6.1.*Not affected
  • 6.6.157 through 6.6.*Not affected
  • 6.12.67 through 6.12.*Not affected
  • 6.16.1 through 6.16.*Not affected
  • 6.17 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.