[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251106195635.2438-1-vnranganath.20@gmail.com>
Date: Fri, 7 Nov 2025 01:26:32 +0530
From: Ranganath V N <vnranganath.20@...il.com>
To: davem@...emloft.net,
edumazet@...gle.com,
horms@...nel.org,
jhs@...atatu.com,
jiri@...nulli.us,
kuba@...nel.org,
pabeni@...hat.com,
xiyou.wangcong@...il.com
Cc: vnranganath.20@...il.com,
david.hunter.linux@...il.com,
khalid@...nel.org,
linux-kernel@...r.kernel.org,
netdev@...r.kernel.org,
skhan@...uxfoundation.org,
syzbot+0c85cae3350b7d486aee@...kaller.appspotmail.com
Subject: [PATCH v3 0/2] net: sched: initialize struct tc_ife to fix kernel-infoleak
This series addresses the uninitialization of the struct which has
2 btes of padding. And copying this uninitialized data to userspace
can leak info from kernel memory.
This sereies ensure all members and padding are cleared prior to
begin copied.
This change silences the KMSAN report and prevents potential information
leaks from the kernel memory.
Signed-off-by: Ranganath V N <vnranganath.20@...il.com>
---
Changes in v3:
- updated the commit messages and subject.
- corrected the code misisng ";" in v2
- Link to v2: https://lore.kernel.org/r/20251101-infoleak-v2-0-01a501d41c09@gmail.com
Changes in v2:
- removed memset(&t, 0, sizeof(t)) from previous patch.
- added the new patch series to address the issue.
- Link to v1: https://lore.kernel.org/r/20251031-infoleak-v1-1-9f7250ee33aa@gmail.com
Ranganath V N (2):
net: sched: act_connmark: initialize struct tc_ife to fix kernel leak
net: sched: act_ife: initialize struct tc_ife to fix KMSAN
kernel-infoleak
net/sched/act_connmark.c | 12 +++++++-----
net/sched/act_ife.c | 12 +++++++-----
2 files changed, 14 insertions(+), 10 deletions(-)
--
2.43.0
Powered by blists - more mailing lists