|
Message-ID: <20140430150844.GA10621@mwanda> Date: Wed, 30 Apr 2014 18:08:44 +0300 From: Dan Carpenter <dan.carpenter@...cle.com> To: Dan Carpenter <dan.carpenter@...cle.com> Cc: linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org, devel@...ica.org, kernel-hardening@...ts.openwall.com, Kees Cook <keescook@...omium.org>, Dave Jones <davej@...hat.com>, Andrew Morton <akpm@...ux-foundation.org> Subject: [patch] lib: check for strcpy() overflows to fixed length buffers There are sometimes where we know that we are doing an strcpy() into a fixed length buffer. In those cases, we could verify that the strcpy() doesn't overflow. This patch introduces DEBUG_STRICT_SLOW_STRCPY_CHECKS if you want to check for that. The downside is that it makes strcpy slower. I introduced __compiletime_size() to make this work. It returns the size of the destination buffer or zero if the size isn't known. The __compiletime_object_size() is similar but if you pass it a struct member then it returns the size of everything from there to the end of the struct. Another difference is __compiletime_object_size() returns -1 for unknown sizes. If you pass a char pointer to __compiletime_size() then it returns zero. The strcpy() check ignores buffers with just one byte because people often use those for variable length strings at the end of a struct. I have tested this patch lightly and created some bugs for it to detect but I have not detected any real life overflows. Signed-off-by: Dan Carpenter <dan.carpenter@...cle.com> diff --git a/include/acpi/platform/acenv.h b/include/acpi/platform/acenv.h index e863dd5..5e0fc2b 100644 --- a/include/acpi/platform/acenv.h +++ b/include/acpi/platform/acenv.h @@ -320,7 +320,7 @@ #define ACPI_STRSTR(s1,s2) strstr((s1), (s2)) #define ACPI_STRCHR(s1,c) strchr((s1), (c)) #define ACPI_STRLEN(s) (acpi_size) strlen((s)) -#define ACPI_STRCPY(d,s) (void) strcpy((d), (s)) +#define ACPI_STRCPY(d,s) strcpy((d), (s)) #define ACPI_STRNCPY(d,s,n) (void) strncpy((d), (s), (acpi_size)(n)) #define ACPI_STRNCMP(d,s,n) strncmp((d), (s), (acpi_size)(n)) #define ACPI_STRCMP(d,s) strcmp((d), (s)) diff --git a/include/linux/compiler-gcc4.h b/include/linux/compiler-gcc4.h index 2507fd2..1fb7fd0 100644 --- a/include/linux/compiler-gcc4.h +++ b/include/linux/compiler-gcc4.h @@ -16,6 +16,9 @@ #if GCC_VERSION >= 40100 && GCC_VERSION < 40600 # define __compiletime_object_size(obj) __builtin_object_size(obj, 0) #endif +#if GCC_VERSION > 40600 +# define __compiletime_size(obj) __builtin_object_size(obj, 3) +#endif #if GCC_VERSION >= 40300 /* Mark functions as cold. gcc will assume any path leading to a call diff --git a/include/linux/compiler.h b/include/linux/compiler.h index ee7239e..b615964 100644 --- a/include/linux/compiler.h +++ b/include/linux/compiler.h @@ -318,6 +318,9 @@ void ftrace_likely_update(struct ftrace_branch_data *f, int val, int expect); #ifndef __compiletime_object_size # define __compiletime_object_size(obj) -1 #endif +#ifndef __compiletime_size +# define __compiletime_size(obj) 0 +#endif #ifndef __compiletime_warning # define __compiletime_warning(message) #endif diff --git a/include/linux/string.h b/include/linux/string.h index ac889c5..fc126a1 100644 --- a/include/linux/string.h +++ b/include/linux/string.h @@ -154,4 +154,13 @@ static inline const char *kbasename(const char *path) return tail ? tail + 1 : path; } +#if CONFIG_DEBUG_STRICT_SLOW_STRCPY_CHECKS +#define strcpy(dest, src) do { \ + int len = __compiletime_size(dest); \ + if (len > 1 && strlen(src) >= len) \ + WARN_ONCE(1, "strcpy() overflow copying \"%s\"\n", src); \ + strcpy(dest, src); \ +} while (0) +#endif + #endif /* _LINUX_STRING_H_ */ diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug index 819ac51..94db086 100644 --- a/lib/Kconfig.debug +++ b/lib/Kconfig.debug @@ -1431,6 +1431,15 @@ config DEBUG_STRICT_USER_COPY_CHECKS If unsure, say N. +config DEBUG_STRICT_SLOW_STRCPY_CHECKS + bool "Strict checks for strcpy() overflows" + depends on DEBUG_KERNEL + help + Enabling this option adds some extra sanity checks when strcpy() is + called(). This will slow down the kernel a bit. + + If unsure, say N. + source kernel/trace/Kconfig menu "Runtime Testing"
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.