lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240815160148.be83228a7804c6389393429a@linux-foundation.org>
Date: Thu, 15 Aug 2024 16:01:48 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Ivan Orlov <ivan.orlov0322@...il.com>
Cc: kees@...nel.org, davidgow@...gle.com, kunit-dev@...glegroups.com,
 linux-kernel@...r.kernel.org, erhard_f@...lbox.org
Subject: Re: [PATCH] kunit/overflow: Fix UB in overflow_allocation_test

On Thu, 15 Aug 2024 01:04:31 +0100 Ivan Orlov <ivan.orlov0322@...il.com> wrote:

> The 'device_name' array doesn't exist out of the
> 'overflow_allocation_test' function scope. However, it is being used as
> a driver name when calling 'kunit_driver_create' from
> 'kunit_device_register'. It produces the kernel panic with KASAN
> enabled.
> 
> Since this variable is used in one place only, remove it and pass the
> device name into kunit_device_register directly as an ascii string.

Fixes: ca90800a91ba ("test_overflow: Add memory allocation overflow tests")
Cc: <stable@...r.kernel.org>

yes?


I'll grab it now, but perhaps Kees will handle this.


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ