* [PATCH net-next v2] tipc: guard against string buffer overrun
@ 2024-08-01 18:35 Simon Horman
2024-08-02 9:42 ` Simon Horman
2024-08-03 0:30 ` patchwork-bot+netdevbpf
0 siblings, 2 replies; 3+ messages in thread
From: Simon Horman @ 2024-08-01 18:35 UTC (permalink / raw)
To: David S. Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni
Cc: Jon Maloy, Ying Xue, Per Liden, netdev, tipc-discussion
Smatch reports that copying media_name and if_name to name_parts may
overwrite the destination.
.../bearer.c:166 bearer_name_validate() error: strcpy() 'media_name' too large for 'name_parts->media_name' (32 vs 16)
.../bearer.c:167 bearer_name_validate() error: strcpy() 'if_name' too large for 'name_parts->if_name' (1010102 vs 16)
This does seem to be the case so guard against this possibility by using
strscpy() and failing if truncation occurs.
Introduced by commit b97bf3fd8f6a ("[TIPC] Initial merge")
Compile tested only.
Reviewed-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Simon Horman <horms@kernel.org>
---
I am not marking this as a fix for net as I am not aware of this
actually breaking anything in practice. Thus, at this point I consider
it more of a clean-up than a bug fix.
---
Changes in v2:
- Correct formatting and typo in subject (Thanks Jakub)
+ The formatting problem was caused by tooling (b4)
so I reworded the subject as a work-around
- Added Acked-by tag from Jakub
- Link to v1: https://lore.kernel.org/r/20240731-tipic-overrun-v1-1-32ce5098c3e9@kernel.org
---
net/tipc/bearer.c | 8 ++++++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/net/tipc/bearer.c b/net/tipc/bearer.c
index 5a526ebafeb4..3c9e25f6a1d2 100644
--- a/net/tipc/bearer.c
+++ b/net/tipc/bearer.c
@@ -163,8 +163,12 @@ static int bearer_name_validate(const char *name,
/* return bearer name components, if necessary */
if (name_parts) {
- strcpy(name_parts->media_name, media_name);
- strcpy(name_parts->if_name, if_name);
+ if (strscpy(name_parts->media_name, media_name,
+ TIPC_MAX_MEDIA_NAME) < 0)
+ return 0;
+ if (strscpy(name_parts->if_name, if_name,
+ TIPC_MAX_IF_NAME) < 0)
+ return 0;
}
return 1;
}
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [PATCH net-next v2] tipc: guard against string buffer overrun
2024-08-01 18:35 [PATCH net-next v2] tipc: guard against string buffer overrun Simon Horman
@ 2024-08-02 9:42 ` Simon Horman
2024-08-03 0:30 ` patchwork-bot+netdevbpf
1 sibling, 0 replies; 3+ messages in thread
From: Simon Horman @ 2024-08-02 9:42 UTC (permalink / raw)
To: David S. Miller, Eric Dumazet, Jakub Kicinski, Paolo Abeni
Cc: Jon Maloy, Ying Xue, Per Liden, netdev, tipc-discussion
On Thu, Aug 01, 2024 at 07:35:37PM +0100, Simon Horman wrote:
> Smatch reports that copying media_name and if_name to name_parts may
> overwrite the destination.
>
> .../bearer.c:166 bearer_name_validate() error: strcpy() 'media_name' too large for 'name_parts->media_name' (32 vs 16)
> .../bearer.c:167 bearer_name_validate() error: strcpy() 'if_name' too large for 'name_parts->if_name' (1010102 vs 16)
>
> This does seem to be the case so guard against this possibility by using
> strscpy() and failing if truncation occurs.
>
> Introduced by commit b97bf3fd8f6a ("[TIPC] Initial merge")
>
> Compile tested only.
>
> Reviewed-by: Jakub Kicinski <kuba@kernel.org>
> Signed-off-by: Simon Horman <horms@kernel.org>
> ---
> I am not marking this as a fix for net as I am not aware of this
> actually breaking anything in practice. Thus, at this point I consider
> it more of a clean-up than a bug fix.
> ---
> Changes in v2:
> - Correct formatting and typo in subject (Thanks Jakub)
> + The formatting problem was caused by tooling (b4)
> so I reworded the subject as a work-around
Just to clarify. The formatting issue I was referring, is a double space
in the subject [1], which seems to of occurred due to the subject being
linewrapped and then unlinewrapped. However, in the light of a new day,
it is not at all clear to me that b4 is the cause of the problem.
So sorry for pointing my finger at it.
[1] https://lore.kernel.org/netdev/20240731182356.01a4c2b8@kernel.org/
> - Added Acked-by tag from Jakub
> - Link to v1: https://lore.kernel.org/r/20240731-tipic-overrun-v1-1-32ce5098c3e9@kernel.org
...
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH net-next v2] tipc: guard against string buffer overrun
2024-08-01 18:35 [PATCH net-next v2] tipc: guard against string buffer overrun Simon Horman
2024-08-02 9:42 ` Simon Horman
@ 2024-08-03 0:30 ` patchwork-bot+netdevbpf
1 sibling, 0 replies; 3+ messages in thread
From: patchwork-bot+netdevbpf @ 2024-08-03 0:30 UTC (permalink / raw)
To: Simon Horman
Cc: davem, edumazet, kuba, pabeni, jmaloy, ying.xue, per.liden,
netdev, tipc-discussion
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 01 Aug 2024 19:35:37 +0100 you wrote:
> Smatch reports that copying media_name and if_name to name_parts may
> overwrite the destination.
>
> .../bearer.c:166 bearer_name_validate() error: strcpy() 'media_name' too large for 'name_parts->media_name' (32 vs 16)
> .../bearer.c:167 bearer_name_validate() error: strcpy() 'if_name' too large for 'name_parts->if_name' (1010102 vs 16)
>
> This does seem to be the case so guard against this possibility by using
> strscpy() and failing if truncation occurs.
>
> [...]
Here is the summary with links:
- [net-next,v2] tipc: guard against string buffer overrun
https://git.kernel.org/netdev/net-next/c/6555a2a9212b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2024-08-03 0:30 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2024-08-01 18:35 [PATCH net-next v2] tipc: guard against string buffer overrun Simon Horman
2024-08-02 9:42 ` Simon Horman
2024-08-03 0:30 ` patchwork-bot+netdevbpf
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).