[DE] Kernel 4.16.8-towo.2 und nvidia Problem?

[Geier0815]

Kernel failure message 1:
------------[ cut here ]------------
Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_t' (offset 11864, size 3)!
WARNING: CPU: 1 PID: 1803 at /build/linux-siduction-4.16/mm/usercopy.c:81 usercopy_warn+0x7e/0xa0
Modules linked in: cpufreq_powersave cpufreq_conservative cpufreq_userspace bridge stp llc binfmt_misc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iTCO_wdt input_leds irqbypass hp_wmi iTCO_vendor_support mei_wdt sparse_keymap wmi_bmof crct10dif_pclmul snd_hda_codec_realtek snd_hda_codec_hdmi crc32_pclmul snd_hda_codec_generic ghash_clmulni_intel snd_hda_intel pcbc aesni_intel snd_hda_codec pktcdvd snd_hda_core aes_x86_64 snd_hwdep snd_pcm_oss snd_mixer_oss crypto_simd snd_pcm glue_helper cryptd snd_timer mei_me snd soundcore intel_cstate mei intel_rapl_perf shpchp ie31200_edac lpc_ich mac_hid wmi nvidia(PO) nfsd drm firewire_sbp2 auth_rpcgss firewire_core nfs_acl lockd crc_itu_t parport_pc grace sunrpc ppdev lp parport ip_tables x_tables autofs4 uas usb_storage
 hid_generic usbmouse usbkbd usbhid hid ahci i2c_i801 libahci e1000 e1000e ptp pps_core
CPU: 1 PID: 1803 Comm: Xorg Tainted: P           O     4.16.8-towo.2-siduction-amd64 #1 siduction 4.16-16
Hardware name: Hewlett-Packard HP Z220 CMT Workstation/1790, BIOS K51 v01.72 04/01/2014
RIP: 0010:usercopy_warn+0x7e/0xa0
RSP: 0018:ffffad56c31b7bb8 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffff998745f7de58 RCX: 0000000000000006
RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff99875dc964b0
RBP: 0000000000000003 R08: 000000000000035b R09: 0000000000000004
R10: ffffffffa010c2d5 R11: 0000000000000001 R12: 0000000000000001
R13: ffff998745f7de5b R14: ffff998745f7de58 R15: ffff998745f7dea0
FS:  00007f1cca1eba40(0000) GS:ffff99875dc80000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1cc11b1000 CR3: 0000000377ac0001 CR4: 00000000001606e0
Call Trace:
 __check_object_size+0x9c/0x1a0
 os_memcpy_to_user+0x21/0x40 [nvidia]
 _nv001372rm+0xa5/0x260 [nvidia]
 ? _nv004784rm+0x4eba/0x5500 [nvidia]
 ? _nv004331rm+0xec/0xf0 [nvidia]
 ? _nv004326rm+0xca/0x650 [nvidia]
 ? _nv015126rm+0x576/0x5c0 [nvidia]
 ? _nv000694rm+0x2e/0x60 [nvidia]
 ? _nv000789rm+0x5f5/0x8b0 [nvidia]
 ? rm_ioctl+0x73/0x100 [nvidia]
 ? nvidia_ioctl+0x221/0x460 [nvidia]
 ? nvidia_frontend_ioctl+0x2d/0x60 [nvidia]
 ? nvidia_frontend_unlocked_ioctl+0x19/0x20 [nvidia]
 ? do_vfs_ioctl+0xa4/0x630
 ? vfs_write+0x12f/0x1a0
 ? SyS_ioctl+0x3b/0x70
 ? do_syscall_64+0x73/0x140
 ? entry_SYSCALL_64_after_hwframe+0x3d/0xa2
Code: 48 c7 c0 83 db 0c a0 48 0f 44 c2 41 50 51 41 51 48 89 f9 49 89 f1 4d 89 d8 4c 89 d2 48 89 c6 48 c7 c7 d0 db 0c a0 e8 d2 4d e3 ff <0f> 0b 48 83 c4 18 c3 48 c7 c6 01 c3 0b a0 49 89 f1 49 89 f3 eb
---[ end trace d2fb7bc8abe22861 ]---

Muß ich mir da Gedanken machen oder kann ich da gar etwas gegen tun?

[towo]

Punkt 1:  Das ist nicht erst seit .8 so
Punkt 2:  Das Einzige, was Du machen kannst, ist Nvidia auf die Füße treten.

[Geier0815]

Danke dir!