Bug#899998: nvidia-legacy-340xx-kernel-dkms: Dmesg output: "Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t'"

Uoti Urpala uoti.urpala at pp1.inet.fi
Thu Jun 28 20:59:02 BST 2018


On Thu, 24 May 2018 09:14:34 -0500 Phil Miller <unmobile+debbugs at gmail.
com> wrote:
> At present, this doesn't hurt functionality of a default configuration system,
> but it would prevent someone using the nvidia driver from enabling the kernel's
> usercopy protections. In future kernel releases where those protections are
> enabled by default, this bug will become more serious.

Kernel package version 4.16.16-1 has this:
* hardening: enable FORTIFY_SOURCE, disable HARDENED_USERCOPY_FALLBACK

I think this means that the driver is broken with the current kernel in
unstable. Booting with the kernel commandline parameter
"slab_common.usercopy_fallback=Y" may work around the problem?



More information about the pkg-nvidia-devel mailing list