summaryrefslogtreecommitdiff
path: root/drivers/ntb/ntb_transport.c
diff options
context:
space:
mode:
authorKaixin Wang <kxwang23@m.fudan.edu.cn>2024-09-09 20:20:07 +0300
committerJon Mason <jdmason@kudzu.us>2024-09-20 17:50:38 +0300
commite51aded92d42784313ba16c12f4f88cc4f973bbb (patch)
treeafb951ba4c4fb48b8f8cfad36a4958420cc68ed6 /drivers/ntb/ntb_transport.c
parent87a7d7150589f68cd7938b208310c93d1e4c3773 (diff)
downloadlinux-e51aded92d42784313ba16c12f4f88cc4f973bbb.tar.xz
ntb: ntb_hw_switchtec: Fix use after free vulnerability in switchtec_ntb_remove due to race condition
In the switchtec_ntb_add function, it can call switchtec_ntb_init_sndev function, then &sndev->check_link_status_work is bound with check_link_status_work. switchtec_ntb_link_notification may be called to start the work. If we remove the module which will call switchtec_ntb_remove to make cleanup, it will free sndev through kfree(sndev), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | check_link_status_work switchtec_ntb_remove | kfree(sndev); | | if (sndev->link_force_down) | // use sndev Fix it by ensuring that the work is canceled before proceeding with the cleanup in switchtec_ntb_remove. Signed-off-by: Kaixin Wang <kxwang23@m.fudan.edu.cn> Reviewed-by: Logan Gunthorpe <logang@deltatee.com> Signed-off-by: Jon Mason <jdmason@kudzu.us>
Diffstat (limited to 'drivers/ntb/ntb_transport.c')
0 files changed, 0 insertions, 0 deletions