[PATCH 3/5] test_kmod: Avoid potential double free in trigger_config_run_type()
Luis R. Rodriguez
mcgrof at kernel.org
Wed Jun 10 15:49:21 UTC 2020
From: Tiezhu Yang <yangtiezhu at loongson.cn>
Reset the member "test_fs" of the test configuration after a call
of the function "kfree_const" to a null pointer so that a double
memory release will not be performed.
Fixes: d9c6a72d6fa2 ("kmod: add test driver to stress test the module loader")
Acked-by: Luis Chamberlain <mcgrof at kernel.org>
Signed-off-by: Tiezhu Yang <yangtiezhu at loongson.cn>
Signed-off-by: Luis Chamberlain <mcgrof at kernel.org>
---
lib/test_kmod.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/test_kmod.c b/lib/test_kmod.c
index e651c37d56db..eab52770070d 100644
--- a/lib/test_kmod.c
+++ b/lib/test_kmod.c
@@ -745,7 +745,7 @@ static int trigger_config_run_type(struct kmod_test_device *test_dev,
break;
case TEST_KMOD_FS_TYPE:
kfree_const(config->test_fs);
- config->test_driver = NULL;
+ config->test_fs = NULL;
copied = config_copy_test_fs(config, test_str,
strlen(test_str));
break;
--
2.26.2
More information about the Linux-security-module-archive
mailing list