From: syzbot <syzbot+2c29addf92581b410079@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Forwarded: [PATCH] bpf: Fix double offset in check_reg_const_str()
Date: Mon, 05 Jan 2026 20:48:26 -0800 [thread overview]
Message-ID: <695c941a.050a0220.1c677c.0337.GAE@google.com> (raw)
In-Reply-To: <695bc686.050a0220.1c677c.032f.GAE@google.com>
For archival purposes, forwarding an incoming command email to
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com.
***
Subject: [PATCH] bpf: Fix double offset in check_reg_const_str()
Author: kartikey406@gmail.com
#syz test: git://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git master
map_direct_value_addr() returns the address already offset by map_off,
but check_reg_const_str() adds map_off again when calling strnchr().
This causes the null-termination check to read from the wrong address,
potentially past the end of the map value buffer.
This triggers a KASAN slab-out-of-bounds in strnchr() when a BPF program
passes a PTR_TO_MAP_VALUE to a helper expecting ARG_PTR_TO_CONST_STR,
as the verifier fails to properly validate the string is null-terminated
within bounds.
Remove the redundant offset addition since map_addr already points to
the correct location.
Reported-by: syzbot+2c29addf92581b410079@syzkaller.appspotmail.com
Fixes: 0b51940729150 ("bpf: Factor out helper check_reg_const_str()")
Signed-off-by: Deepanshu Kartikey <kartikey406@gmail.com>
---
kernel/bpf/verifier.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/bpf/verifier.c b/kernel/bpf/verifier.c
index f0ca69f888fa..b1cb501fb577 100644
--- a/kernel/bpf/verifier.c
+++ b/kernel/bpf/verifier.c
@@ -9638,7 +9638,7 @@ static int check_reg_const_str(struct bpf_verifier_env *env,
}
str_ptr = (char *)(long)(map_addr);
- if (!strnchr(str_ptr + map_off, map->value_size - map_off, 0)) {
+ if (!strnchr(str_ptr, map->value_size - map_off, 0)) {
verbose(env, "string is not zero-terminated\n");
return -EINVAL;
}
--
2.43.0
next prev parent reply other threads:[~2026-01-06 4:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 14:11 [syzbot] [bpf?] KASAN: slab-out-of-bounds Read in strnchr syzbot
2026-01-06 4:48 ` syzbot [this message]
2026-01-06 5:19 ` Forwarded: [PATCH] bpf: Fix double offset in insn_array_map_direct_value_addr() syzbot
2026-01-06 15:44 ` Forwarded: [PATCH] bpf: Reject BPF_MAP_TYPE_INSN_ARRAY in check_reg_const_str() syzbot
2026-01-07 8:47 ` [syzbot] [bpf?] KASAN: slab-out-of-bounds Read in strnchr Edward Adam Davis
2026-01-07 9:39 ` syzbot
2026-01-07 9:39 ` [PATCH] bpf: Format string can't be empty Edward Adam Davis
2026-01-08 3:02 ` Alexei Starovoitov
2026-01-08 3:52 ` Edward Adam Davis
2026-01-08 21:43 ` Alexei Starovoitov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=695c941a.050a0220.1c677c.0337.GAE@google.com \
--to=syzbot+2c29addf92581b410079@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®