2017-08-07 17:26:19 +03:00
|
|
|
/* tnum: tracked (or tristate) numbers
|
|
|
|
*
|
|
|
|
* A tnum tracks knowledge about the bits of a value. Each bit can be either
|
|
|
|
* known (0 or 1), or unknown (x). Arithmetic operations on tnums will
|
|
|
|
* propagate the unknown bits such that the tnum result represents all the
|
|
|
|
* possible results for possible values of the operands.
|
|
|
|
*/
|
2019-08-19 19:10:35 +03:00
|
|
|
|
|
|
|
#ifndef _LINUX_TNUM_H
|
|
|
|
#define _LINUX_TNUM_H
|
|
|
|
|
2017-08-07 17:26:19 +03:00
|
|
|
#include <linux/types.h>
|
|
|
|
|
|
|
|
struct tnum {
|
|
|
|
u64 value;
|
|
|
|
u64 mask;
|
|
|
|
};
|
|
|
|
|
|
|
|
/* Constructors */
|
|
|
|
/* Represent a known constant as a tnum. */
|
|
|
|
struct tnum tnum_const(u64 value);
|
|
|
|
/* A completely unknown value */
|
|
|
|
extern const struct tnum tnum_unknown;
|
2017-08-07 17:26:36 +03:00
|
|
|
/* A value that's unknown except that @min <= value <= @max */
|
|
|
|
struct tnum tnum_range(u64 min, u64 max);
|
2017-08-07 17:26:19 +03:00
|
|
|
|
|
|
|
/* Arithmetic and logical ops */
|
|
|
|
/* Shift a tnum left (by a fixed shift) */
|
|
|
|
struct tnum tnum_lshift(struct tnum a, u8 shift);
|
bpf/verifier: improve register value range tracking with ARSH
When helpers like bpf_get_stack returns an int value
and later on used for arithmetic computation, the LSH and ARSH
operations are often required to get proper sign extension into
64-bit. For example, without this patch:
54: R0=inv(id=0,umax_value=800)
54: (bf) r8 = r0
55: R0=inv(id=0,umax_value=800) R8_w=inv(id=0,umax_value=800)
55: (67) r8 <<= 32
56: R8_w=inv(id=0,umax_value=3435973836800,var_off=(0x0; 0x3ff00000000))
56: (c7) r8 s>>= 32
57: R8=inv(id=0)
With this patch:
54: R0=inv(id=0,umax_value=800)
54: (bf) r8 = r0
55: R0=inv(id=0,umax_value=800) R8_w=inv(id=0,umax_value=800)
55: (67) r8 <<= 32
56: R8_w=inv(id=0,umax_value=3435973836800,var_off=(0x0; 0x3ff00000000))
56: (c7) r8 s>>= 32
57: R8=inv(id=0, umax_value=800,var_off=(0x0; 0x3ff))
With better range of "R8", later on when "R8" is added to other register,
e.g., a map pointer or scalar-value register, the better register
range can be derived and verifier failure may be avoided.
In our later example,
......
usize = bpf_get_stack(ctx, raw_data, max_len, BPF_F_USER_STACK);
if (usize < 0)
return 0;
ksize = bpf_get_stack(ctx, raw_data + usize, max_len - usize, 0);
......
Without improving ARSH value range tracking, the register representing
"max_len - usize" will have smin_value equal to S64_MIN and will be
rejected by verifier.
Acked-by: Alexei Starovoitov <ast@kernel.org>
Signed-off-by: Yonghong Song <yhs@fb.com>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
2018-04-29 08:28:11 +03:00
|
|
|
/* Shift (rsh) a tnum right (by a fixed shift) */
|
2017-08-07 17:26:19 +03:00
|
|
|
struct tnum tnum_rshift(struct tnum a, u8 shift);
|
bpf/verifier: improve register value range tracking with ARSH
When helpers like bpf_get_stack returns an int value
and later on used for arithmetic computation, the LSH and ARSH
operations are often required to get proper sign extension into
64-bit. For example, without this patch:
54: R0=inv(id=0,umax_value=800)
54: (bf) r8 = r0
55: R0=inv(id=0,umax_value=800) R8_w=inv(id=0,umax_value=800)
55: (67) r8 <<= 32
56: R8_w=inv(id=0,umax_value=3435973836800,var_off=(0x0; 0x3ff00000000))
56: (c7) r8 s>>= 32
57: R8=inv(id=0)
With this patch:
54: R0=inv(id=0,umax_value=800)
54: (bf) r8 = r0
55: R0=inv(id=0,umax_value=800) R8_w=inv(id=0,umax_value=800)
55: (67) r8 <<= 32
56: R8_w=inv(id=0,umax_value=3435973836800,var_off=(0x0; 0x3ff00000000))
56: (c7) r8 s>>= 32
57: R8=inv(id=0, umax_value=800,var_off=(0x0; 0x3ff))
With better range of "R8", later on when "R8" is added to other register,
e.g., a map pointer or scalar-value register, the better register
range can be derived and verifier failure may be avoided.
In our later example,
......
usize = bpf_get_stack(ctx, raw_data, max_len, BPF_F_USER_STACK);
if (usize < 0)
return 0;
ksize = bpf_get_stack(ctx, raw_data + usize, max_len - usize, 0);
......
Without improving ARSH value range tracking, the register representing
"max_len - usize" will have smin_value equal to S64_MIN and will be
rejected by verifier.
Acked-by: Alexei Starovoitov <ast@kernel.org>
Signed-off-by: Yonghong Song <yhs@fb.com>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
2018-04-29 08:28:11 +03:00
|
|
|
/* Shift (arsh) a tnum right (by a fixed min_shift) */
|
bpf: Fix incorrect verifier simulation of ARSH under ALU32
Anatoly has been fuzzing with kBdysch harness and reported a hang in one
of the outcomes:
0: R1=ctx(id=0,off=0,imm=0) R10=fp0
0: (85) call bpf_get_socket_cookie#46
1: R0_w=invP(id=0) R10=fp0
1: (57) r0 &= 808464432
2: R0_w=invP(id=0,umax_value=808464432,var_off=(0x0; 0x30303030)) R10=fp0
2: (14) w0 -= 810299440
3: R0_w=invP(id=0,umax_value=4294967295,var_off=(0xcf800000; 0x3077fff0)) R10=fp0
3: (c4) w0 s>>= 1
4: R0_w=invP(id=0,umin_value=1740636160,umax_value=2147221496,var_off=(0x67c00000; 0x183bfff8)) R10=fp0
4: (76) if w0 s>= 0x30303030 goto pc+216
221: R0_w=invP(id=0,umin_value=1740636160,umax_value=2147221496,var_off=(0x67c00000; 0x183bfff8)) R10=fp0
221: (95) exit
processed 6 insns (limit 1000000) [...]
Taking a closer look, the program was xlated as follows:
# ./bpftool p d x i 12
0: (85) call bpf_get_socket_cookie#7800896
1: (bf) r6 = r0
2: (57) r6 &= 808464432
3: (14) w6 -= 810299440
4: (c4) w6 s>>= 1
5: (76) if w6 s>= 0x30303030 goto pc+216
6: (05) goto pc-1
7: (05) goto pc-1
8: (05) goto pc-1
[...]
220: (05) goto pc-1
221: (05) goto pc-1
222: (95) exit
Meaning, the visible effect is very similar to f54c7898ed1c ("bpf: Fix
precision tracking for unbounded scalars"), that is, the fall-through
branch in the instruction 5 is considered to be never taken given the
conclusion from the min/max bounds tracking in w6, and therefore the
dead-code sanitation rewrites it as goto pc-1. However, real-life input
disagrees with verification analysis since a soft-lockup was observed.
The bug sits in the analysis of the ARSH. The definition is that we shift
the target register value right by K bits through shifting in copies of
its sign bit. In adjust_scalar_min_max_vals(), we do first coerce the
register into 32 bit mode, same happens after simulating the operation.
However, for the case of simulating the actual ARSH, we don't take the
mode into account and act as if it's always 64 bit, but location of sign
bit is different:
dst_reg->smin_value >>= umin_val;
dst_reg->smax_value >>= umin_val;
dst_reg->var_off = tnum_arshift(dst_reg->var_off, umin_val);
Consider an unknown R0 where bpf_get_socket_cookie() (or others) would
for example return 0xffff. With the above ARSH simulation, we'd see the
following results:
[...]
1: R1=ctx(id=0,off=0,imm=0) R2_w=invP65535 R10=fp0
1: (85) call bpf_get_socket_cookie#46
2: R0_w=invP(id=0) R10=fp0
2: (57) r0 &= 808464432
-> R0_runtime = 0x3030
3: R0_w=invP(id=0,umax_value=808464432,var_off=(0x0; 0x30303030)) R10=fp0
3: (14) w0 -= 810299440
-> R0_runtime = 0xcfb40000
4: R0_w=invP(id=0,umax_value=4294967295,var_off=(0xcf800000; 0x3077fff0)) R10=fp0
(0xffffffff)
4: (c4) w0 s>>= 1
-> R0_runtime = 0xe7da0000
5: R0_w=invP(id=0,umin_value=1740636160,umax_value=2147221496,var_off=(0x67c00000; 0x183bfff8)) R10=fp0
(0x67c00000) (0x7ffbfff8)
[...]
In insn 3, we have a runtime value of 0xcfb40000, which is '1100 1111 1011
0100 0000 0000 0000 0000', the result after the shift has 0xe7da0000 that
is '1110 0111 1101 1010 0000 0000 0000 0000', where the sign bit is correctly
retained in 32 bit mode. In insn4, the umax was 0xffffffff, and changed into
0x7ffbfff8 after the shift, that is, '0111 1111 1111 1011 1111 1111 1111 1000'
and means here that the simulation didn't retain the sign bit. With above
logic, the updates happen on the 64 bit min/max bounds and given we coerced
the register, the sign bits of the bounds are cleared as well, meaning, we
need to force the simulation into s32 space for 32 bit alu mode.
Verification after the fix below. We're first analyzing the fall-through branch
on 32 bit signed >= test eventually leading to rejection of the program in this
specific case:
0: R1=ctx(id=0,off=0,imm=0) R10=fp0
0: (b7) r2 = 808464432
1: R1=ctx(id=0,off=0,imm=0) R2_w=invP808464432 R10=fp0
1: (85) call bpf_get_socket_cookie#46
2: R0_w=invP(id=0) R10=fp0
2: (bf) r6 = r0
3: R0_w=invP(id=0) R6_w=invP(id=0) R10=fp0
3: (57) r6 &= 808464432
4: R0_w=invP(id=0) R6_w=invP(id=0,umax_value=808464432,var_off=(0x0; 0x30303030)) R10=fp0
4: (14) w6 -= 810299440
5: R0_w=invP(id=0) R6_w=invP(id=0,umax_value=4294967295,var_off=(0xcf800000; 0x3077fff0)) R10=fp0
5: (c4) w6 s>>= 1
6: R0_w=invP(id=0) R6_w=invP(id=0,umin_value=3888119808,umax_value=4294705144,var_off=(0xe7c00000; 0x183bfff8)) R10=fp0
(0x67c00000) (0xfffbfff8)
6: (76) if w6 s>= 0x30303030 goto pc+216
7: R0_w=invP(id=0) R6_w=invP(id=0,umin_value=3888119808,umax_value=4294705144,var_off=(0xe7c00000; 0x183bfff8)) R10=fp0
7: (30) r0 = *(u8 *)skb[808464432]
BPF_LD_[ABS|IND] uses reserved fields
processed 8 insns (limit 1000000) [...]
Fixes: 9cbe1f5a32dc ("bpf/verifier: improve register value range tracking with ARSH")
Reported-by: Anatoly Trosinenko <anatoly.trosinenko@gmail.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Acked-by: Yonghong Song <yhs@fb.com>
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Link: https://lore.kernel.org/bpf/20200115204733.16648-1-daniel@iogearbox.net
2020-01-15 23:47:33 +03:00
|
|
|
struct tnum tnum_arshift(struct tnum a, u8 min_shift, u8 insn_bitness);
|
2017-08-07 17:26:19 +03:00
|
|
|
/* Add two tnums, return @a + @b */
|
|
|
|
struct tnum tnum_add(struct tnum a, struct tnum b);
|
|
|
|
/* Subtract two tnums, return @a - @b */
|
|
|
|
struct tnum tnum_sub(struct tnum a, struct tnum b);
|
|
|
|
/* Bitwise-AND, return @a & @b */
|
|
|
|
struct tnum tnum_and(struct tnum a, struct tnum b);
|
|
|
|
/* Bitwise-OR, return @a | @b */
|
|
|
|
struct tnum tnum_or(struct tnum a, struct tnum b);
|
|
|
|
/* Bitwise-XOR, return @a ^ @b */
|
|
|
|
struct tnum tnum_xor(struct tnum a, struct tnum b);
|
|
|
|
/* Multiply two tnums, return @a * @b */
|
|
|
|
struct tnum tnum_mul(struct tnum a, struct tnum b);
|
|
|
|
|
|
|
|
/* Return a tnum representing numbers satisfying both @a and @b */
|
|
|
|
struct tnum tnum_intersect(struct tnum a, struct tnum b);
|
|
|
|
|
|
|
|
/* Return @a with all but the lowest @size bytes cleared */
|
|
|
|
struct tnum tnum_cast(struct tnum a, u8 size);
|
|
|
|
|
|
|
|
/* Returns true if @a is a known constant */
|
|
|
|
static inline bool tnum_is_const(struct tnum a)
|
|
|
|
{
|
|
|
|
return !a.mask;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Returns true if @a == tnum_const(@b) */
|
|
|
|
static inline bool tnum_equals_const(struct tnum a, u64 b)
|
|
|
|
{
|
|
|
|
return tnum_is_const(a) && a.value == b;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Returns true if @a is completely unknown */
|
|
|
|
static inline bool tnum_is_unknown(struct tnum a)
|
|
|
|
{
|
|
|
|
return !~a.mask;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Returns true if @a is known to be a multiple of @size.
|
|
|
|
* @size must be a power of two.
|
|
|
|
*/
|
|
|
|
bool tnum_is_aligned(struct tnum a, u64 size);
|
|
|
|
|
|
|
|
/* Returns true if @b represents a subset of @a. */
|
|
|
|
bool tnum_in(struct tnum a, struct tnum b);
|
|
|
|
|
|
|
|
/* Formatting functions. These have snprintf-like semantics: they will write
|
|
|
|
* up to @size bytes (including the terminating NUL byte), and return the number
|
|
|
|
* of bytes (excluding the terminating NUL) which would have been written had
|
|
|
|
* sufficient space been available. (Thus tnum_sbin always returns 64.)
|
|
|
|
*/
|
|
|
|
/* Format a tnum as a pair of hex numbers (value; mask) */
|
|
|
|
int tnum_strn(char *str, size_t size, struct tnum a);
|
|
|
|
/* Format a tnum as tristate binary expansion */
|
|
|
|
int tnum_sbin(char *str, size_t size, struct tnum a);
|
2019-08-19 19:10:35 +03:00
|
|
|
|
|
|
|
#endif /* _LINUX_TNUM_H */
|