* [PATCH 2/2] procfs.c: Increasing array size
@ 2023-11-16 7:05 Andrey Shumilin
2024-01-08 16:56 ` Alexey Khoroshilov
0 siblings, 1 reply; 2+ messages in thread
From: Andrey Shumilin @ 2023-11-16 7:05 UTC (permalink / raw)
To: Sudip Mukherjee
Cc: Andrey Shumilin, linux-kernel, khoroshilov, ykarpov, vmerzlyakov,
vefanov
The maximum size in bytes of the port->base and port->base_hi
variables is 20 bytes per variable, since they are copied in
decimal notation. Two more characters are \t and \n.
A maximum of 42 bytes can be written to a buffer variable.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
Signed-off-by: Andrey Shumilin <shum.sdl@nppct.ru>
---
drivers/parport/procfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/parport/procfs.c b/drivers/parport/procfs.c
index bd388560ed59..9b894f7cb581 100644
--- a/drivers/parport/procfs.c
+++ b/drivers/parport/procfs.c
@@ -117,7 +117,7 @@ static int do_hardware_base_addr(struct ctl_table *table, int write,
void *result, size_t *lenp, loff_t *ppos)
{
struct parport *port = (struct parport *)table->extra1;
- char buffer[20];
+ char buffer[44];
int len = 0;
if (*ppos) {
--
2.30.2
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: [PATCH 2/2] procfs.c: Increasing array size
2023-11-16 7:05 [PATCH 2/2] procfs.c: Increasing array size Andrey Shumilin
@ 2024-01-08 16:56 ` Alexey Khoroshilov
0 siblings, 0 replies; 2+ messages in thread
From: Alexey Khoroshilov @ 2024-01-08 16:56 UTC (permalink / raw)
To: Andrey Shumilin, Sudip Mukherjee; +Cc: linux-kernel, lvc-project
On 16.11.2023 10:05, Andrey Shumilin wrote:
> The maximum size in bytes of the port->base and port->base_hi
> variables is 20 bytes per variable, since they are copied in
> decimal notation. Two more characters are \t and \n.
> A maximum of 42 bytes can be written to a buffer variable.
I would update subject and description like that:
paport: Fix potential buffer overflow in do_hardware_base_addr()
The maximum size after expansion for the "%lu\t%lu\n"
is 20+1+20+1+1 = 43 bytes, while buffer is of size 20 bytes.
So buffer overflow may happen.
Otherwise, looks good to me.
Reviewed-by: Alexey Khoroshilov <khoroshilov@ispras.ru>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Signed-off-by: Andrey Shumilin <shum.sdl@nppct.ru>
> ---
> drivers/parport/procfs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/parport/procfs.c b/drivers/parport/procfs.c
> index bd388560ed59..9b894f7cb581 100644
> --- a/drivers/parport/procfs.c
> +++ b/drivers/parport/procfs.c
> @@ -117,7 +117,7 @@ static int do_hardware_base_addr(struct ctl_table *table, int write,
> void *result, size_t *lenp, loff_t *ppos)
> {
> struct parport *port = (struct parport *)table->extra1;
> - char buffer[20];
> + char buffer[44];
> int len = 0;
>
> if (*ppos) {
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2024-01-08 17:34 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-11-16 7:05 [PATCH 2/2] procfs.c: Increasing array size Andrey Shumilin
2024-01-08 16:56 ` Alexey Khoroshilov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®