[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250105070537.58334-1-tanyaagarwal25699@gmail.com>
Date: Sun, 5 Jan 2025 12:35:38 +0530
From: Tanya Agarwal <tanyaagarwal25699@...il.com>
To: paul@...l-moore.com,
jmorris@...ei.org,
serge@...lyn.com
Cc: kees@...nel.org,
yuehaibing@...wei.com,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org,
matthewgarrett@...gle.com,
skhan@...uxfoundation.org,
anupnewsmail@...il.com,
tanyaagarwal25699@...il.com
Subject: [PATCH V3] lockdown: Initialize array before use
From: Tanya Agarwal <tanyaagarwal25699@...il.com>
The static code analysis tool "Coverity Scan" pointed the following
details out for further development considerations:
CID 1486102: Uninitialized scalar variable (UNINIT)
uninit_use_in_call: Using uninitialized value *temp when calling
strlen.
Conclusion:
Initialize array before use in lockdown_read() to satisfy the static
analyzer.
Fixes: 000d388ed3bb ("security: Add a static lockdown policy LSM")
Signed-off-by: Tanya Agarwal <tanyaagarwal25699@...il.com>
---
V2: add Fixes tag and reword commit description
V3: use "" initialization instead of {}
Coverity Link:
https://scan7.scan.coverity.com/#/project-view/52849/11354?selectedIssue=1486102
security/lockdown/lockdown.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/security/lockdown/lockdown.c b/security/lockdown/lockdown.c
index f2bdbd55aa2b..cf83afa1d879 100644
--- a/security/lockdown/lockdown.c
+++ b/security/lockdown/lockdown.c
@@ -96,7 +96,7 @@ static int __init lockdown_lsm_init(void)
static ssize_t lockdown_read(struct file *filp, char __user *buf, size_t count,
loff_t *ppos)
{
- char temp[80];
+ char temp[80] = "";
int i, offset = 0;
for (i = 0; i < ARRAY_SIZE(lockdown_levels); i++) {
--
2.39.5
Powered by blists - more mailing lists