bpf: Avoid splat in pskb_pull_reason
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Avoid splat in pskb_pull_reason
syzkaller builds (CONFIG_DEBUG_NET=y) frequently trigger a debug hint in pskb_may_pull.
We'd like to retain this debug check because it might hint at integer overflows and other issues (kernel code should pull headers, not huge value).
In bpf case, this splat isn't interesting at all: such (nonsensical) bpf programs are typically generated by a fuzzer anyway.
Do what Eric suggested and suppress such warning.
For CONFIG_DEBUG_NET=n we don't need the extra check because pskb_may_pull will do the right thing: return an error without the WARN() backtrace.
From the CVE record · Linux
In Linux kernel builds with CONFIG_DEBUG_NET=y, a BPF program that requests an excessive packet-header pull can trigger a debug warning and backtrace. The input does not establish whether this requires local access, authentication, or user interaction.
Engineers running Linux kernel builds with CONFIG_DEBUG_NET=y should check their versions; affected versions are not specified.