diff options
| author | Andrew Gabbasov <andrew_gabbasov@mentor.com> | 2017-09-30 08:55:55 -0700 |
|---|---|---|
| committer | Felipe Balbi <felipe.balbi@linux.intel.com> | 2017-10-11 13:14:30 +0300 |
| commit | aec17e1e249567e82b26dafbb86de7d07fde8729 (patch) | |
| tree | 9925bd20ffe7f0962bcfaf201b4e0872cfa7e523 /mm/oom_kill.c | |
| parent | cb84f56861eb333af0a5bab475d741b13067c05c (diff) | |
| download | linux-stable-aec17e1e249567e82b26dafbb86de7d07fde8729.tar.gz linux-stable-aec17e1e249567e82b26dafbb86de7d07fde8729.tar.bz2 linux-stable-aec17e1e249567e82b26dafbb86de7d07fde8729.zip | |
usb: gadget: composite: Fix use-after-free in usb_composite_overwrite_options
KASAN enabled configuration reports an error
BUG: KASAN: use-after-free in usb_composite_overwrite_options+...
[libcomposite] at addr ...
Read of size 1 by task ...
when some driver is un-bound and then bound again.
For example, this happens with FunctionFS driver when "ffs-test"
test application is run several times in a row.
If the driver has empty manufacturer ID string in initial static data,
it is then replaced with generated string. After driver unbinding
the generated string is freed, but the driver data still keep that
pointer. And if the driver is then bound again, that pointer
is re-used for string emptiness check.
The fix is to clean up the driver string data upon its unbinding
to drop the pointer to freed memory.
Fixes: cc2683c318a5 ("usb: gadget: Provide a default implementation of default manufacturer string")
Cc: stable@vger.kernel.org
Signed-off-by: Andrew Gabbasov <andrew_gabbasov@mentor.com>
Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
Diffstat (limited to 'mm/oom_kill.c')
0 files changed, 0 insertions, 0 deletions