diff options
| author | Florian Westphal <fw@strlen.de> | 2018-02-07 15:46:25 +0300 |
|---|---|---|
| committer | Pablo Neira Ayuso <pablo@netfilter.org> | 2018-02-14 22:47:41 +0300 |
| commit | 57ebd808a97d7c5b1e1afb937c2db22beba3c1f8 (patch) | |
| tree | 8a048d1fd60cb33a795d292ab8eada5840826325 /tools/perf/scripts/python/export-to-sqlite.py | |
| parent | 01ea306f2ac2baff98d472da719193e738759d93 (diff) | |
| download | linux-57ebd808a97d7c5b1e1afb937c2db22beba3c1f8.tar.xz | |
netfilter: add back stackpointer size checks
The rationale for removing the check is only correct for rulesets
generated by ip(6)tables.
In iptables, a jump can only occur to a user-defined chain, i.e.
because we size the stack based on number of user-defined chains we
cannot exceed stack size.
However, the underlying binary format has no such restriction,
and the validation step only ensures that the jump target is a
valid rule start point.
IOW, its possible to build a rule blob that has no user-defined
chains but does contain a jump.
If this happens, no jump stack gets allocated and crash occurs
because no jumpstack was allocated.
Fixes: 7814b6ec6d0d6 ("netfilter: xtables: don't save/restore jumpstack offset")
Reported-by: syzbot+e783f671527912cd9403@syzkaller.appspotmail.com
Signed-off-by: Florian Westphal <fw@strlen.de>
Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-sqlite.py')
0 files changed, 0 insertions, 0 deletions