fix UAF when lookup kallsym after ftrace disabled
v2 cover fix UAF when lookup kallsym after ftrace disabled
From: Ye Bin <[email protected]>
Diff v2 vs v1:
(1) Add description for PATCH[1/2];
(2) Move judgement from ftrace_free_mem() to allocate_ftrace_mod_map()
Ye Bin (2):
ftrace: fix UAF when lookup kallsym after ftrace disabled
ftrace: don't allocate ftrace module map if ftrace is disabled
kernel/trace/ftrace.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
Signature · 1 line
2.34.1
PATCH v2 1/2 ftrace: fix UAF when lookup kallsym after ftrace disabled
From: Ye Bin <[email protected]>
There's issue as follows:
BUG: unable to handle page fault for address: ffffffffc05d0218 PGD 1bd66f067 P4D 1bd66f067 PUD 1bd671067 PMD 101808067 PTE 0 Oops: Oops: 0000 [#1] SMP KASAN PTI Tainted: [O]=OOT_MODULE, [E]=UNSIGNED_MODULE Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS RIP: 0010:sized_strscpy+0x81/0x2f0 RSP: 0018:ffff88812d76fa08 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffffffffc0601010 RCX: dffffc0000000000 RDX: 0000000000000038 RSI: dffffc0000000000 RDI: ffff88812608da2d RBP: 8080808080808080 R08: ffff88812608da2d R09: ffff88812608da68 R10: ffff88812608d82d R11: ffff88812608d810 R12: 0000000000000038 R13: ffff88812608da2d R14: ffffffffc05d0218 R15: fefefefefefefeff FS: 00007fef552de740(0000) GS:ffff8884251c7000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffc05d0218 CR3: 00000001146f0000 CR4: 00000000000006f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ftrace_mod_get_kallsym+0x1ac/0x590 update_iter_mod+0x239/0x5b0 s_next+0x5b/0xa0 seq_read_iter+0x8c9/0x1070 seq_read+0x249/0x3b0 proc_reg_read+0x1b0/0x280 vfs_read+0x17f/0x920 ksys_read+0xf3/0x1c0 do_syscall_64+0x5f/0x2e0 entry_SYSCALL_64_after_hwframe+0x76/0x7e
Above issue may happens as follow:
(1) Add kprobe trace point;
(2) insmod test.ko;
(3) Trigger ftrace disabled;
(4) rmmod test.ko;
(5) cat /proc/kallsyms; --> Will trigger UAF as test.ko already removed; ftrace_mod_get_kallsym()
...strscpy(module_name, mod_map->mod->name, MODULE_NAME_LEN);
...
As ftrace_release_mod() judge 'ftrace_disabled' is true will return, and 'mod_map' will remaining in ftrace_mod_maps. 'mod_map' has no chance to release. Therefore, this also causes residual resources to accumulate. To solve above issue, unconditionally clean up'mod_map'. Of course, the root cause of this problem is the presence of ftrace_disabled. The fixes tags patch introduces the possibility of residual resources in the case of ftrace_disabled. The root cause of the problem is ftrace_disabled. This patch only adds protection when ftrace_disabled occurs.
--- kernel/trace/ftrace.c | 3 --- 1 file changed, 3 deletions(-)
kernel/trace/ftrace.c +0 -3
@@ -7438,9 +7438,6 @@ void ftrace_release_mod(struct module *mod)mutex_lock (&ftrace_lock); -if (ftrace_disabled) - goto out_unlock; -list_for_each_entry_safe (mod_map, n, &ftrace_mod_maps, list) {if (mod_map->mod == mod) {list_del_rcu (&mod_map->list);
Signature · 1 line
2.34.1
PATCH v2 2/2 ftrace: don't allocate ftrace module map if ftrace is disabled
In reply to Ye BinFrom: Ye Bin <[email protected]>
If the ftrace is disabled, it is meaningless to allocate module map. So add check in allocate_ftrace_mod_map().
--- kernel/trace/ftrace.c | 3 +++ 1 file changed, 3 insertions(+)
kernel/trace/ftrace.c +3 -0
@@ -7626,6 +7626,9 @@ allocate_ftrace_mod_map(struct module *mod, {struct ftrace_mod_map *mod_map; +if (ftrace_disabled) +return NULL ; + mod_map =kmalloc (sizeof (*mod_map),GFP_KERNEL );if (!mod_map)return NULL ;
Signature · 1 line
2.34.1