Kernel panic on Cintiq Pro 24 #276
Comments
|
From the dmesg, it looks like the touch is not loaded yet. Did you see issue when you touch the surface with a pen, instead of your fingers? Did the issue happen when the tablet was connected to the system before you started your system? Also, are you comfortable with building kernel driver, i.e. build and install wacom kernel driver from input-wacom? |
There is no problem, when i use a pen.
No.
Convenient, ready to test. |
|
Can you build the kernel driver by following the steps at: https://github.com/linuxwacom/input-wacom/wiki/Installing-input-wacom-from-source, if you haven't done so? |
Assembled the driver, the problem remained. |
|
We tested it on a kernel 4.19 system. We could not reproduce the issue. Can you try the following steps to see if the issue occurs:
Also, do you have another kernel version to try it on? |
|
I have tested it on a kernel 4.18 sytem and wacom.ko version v2.00-0.48.0.10.g59402f2. Posible problem with USB 3.0. While touching and moving (!) finger the screen I connect/disconnect cable many times in USB 2.0, but when i tried to do this manipulations with USB 3.0 it crashed Kernel Panic. The dmesg demonstraits it. The touchscreen working correctly in any other cases. You are not recommend touching the screen since the system isn't ready, but it's important case for our customer because there is KVM switch in our system and when somebody switch it, a connect / disconnect occurs. |
|
It is an electronic device. For all devices/tools, there are proper ways to use them. The devices react to what we tell them to do. If we give them confusing instruction, they get "confused" too. In theory, when data/device wasn't ready, the driver should not process any events. However, there could be corner cases or under race conditions, data from unexpected user activities trip in. Can you explain the use case a bit more, like why did your customers need to touch the screen while the KVM switch was in action? You probably need to make sure they understand the situation and avoid touching the device when switching is on process. If USB 2 cable worked, can they stay with USB 2 cable? Maybe their system can not catch up with the superspeed USB 3 cable. Or maybe it's just that particular USB 3 cable is causing issue. Did you try another USB 3 cable? Your Call Trace showed hid/usb common code... |
|
Can you please attach the v2.00-0.48.0.10.g59402f2 wacom.ko driver that you compiled which triggered the previous crash on kernel 4.18? You should be able to find it in at |
|
|
Thanks for the copy of the driver. Unfortunately(?) I'm still seeing the same general area which makes little sense for a crash. The RIP in the crash is set to Lines 2694 to 2703 in 59402f2 Squinting at the disassembly seems to indicate that the %rax register is storing the (null) This doesn't really make sense though. The loop just above this block derefrerences each In case its the latter, I've uploaded a test commit which should work around the issue. Please run |
|
Good day, |
|
Glad to hear the patch worked. As the commit states, this was more of a work-in-progress patch to verify the root cause. Now that we know the crash is caused by the driver dealing with stale data, we can write a more proper fix. I'll try to have a more proper fix in the coming days. |
torvalds
pushed a commit
to torvalds/linux
that referenced
this issue
Jan 21, 2022
If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]>
|
Fix has been accepted upstream and should be available in the next RC release of the Linux kernel. Stable releases of the kernel should also get the fix "soon". I'll update again once I have version numbers. |
jigpu
added a commit
to jigpu/input-wacom
that referenced
this issue
Jan 21, 2022
If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom#276 Fixes: 003f50ab673c (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> [[email protected]: Imported into input-wacom repository (20f3cf5f860f)] Signed-off-by: Jason Gerecke <[email protected]>
jigpu
added a commit
to jigpu/input-wacom
that referenced
this issue
Jan 21, 2022
…t count If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom#276 Fixes: 003f50ab673c (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> [[email protected]: Imported into input-wacom repository (20f3cf5f860f)] Signed-off-by: Jason Gerecke <[email protected]> [[email protected]: Backported from input-wacom repository (86c7513)] Signed-off-by: Jason Gerecke <[email protected]>
imaami
pushed a commit
to imaami/linux
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ammarfaizi2
pushed a commit
to ammarfaizi2/linux-block
that referenced
this issue
Jan 23, 2022
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
krazey
pushed a commit
to krazey/android_kernel_samsung_exynos9810
that referenced
this issue
Aug 11, 2022
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
krazey
pushed a commit
to krazey/android_kernel_samsung_exynos9810
that referenced
this issue
Aug 12, 2022
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
krazey
pushed a commit
to ExyBrick/android_kernel_samsung_universal9810
that referenced
this issue
Sep 3, 2022
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
vullk4n
pushed a commit
to vullk4n/kernel_motorola_sdm632
that referenced
this issue
Sep 15, 2022
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
vullk4n
pushed a commit
to vullk4n/kernel_motorola_sdm632
that referenced
this issue
Sep 15, 2022
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
iqba78
pushed a commit
to iqba78/android_kernel_xiaomi_sdm660_southwest
that referenced
this issue
Dec 17, 2022
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
iqba78
pushed a commit
to iqba78/android_kernel_xiaomi_sdm660_southwest
that referenced
this issue
Dec 17, 2022
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Elchanz3
pushed a commit
to Elchanz3/android_kernel_samsung_exynos9820
that referenced
this issue
Mar 8, 2023
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Wrdn28
pushed a commit
to Wrdn28/X01AD_Kernel
that referenced
this issue
Mar 11, 2023
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Elchanz3
pushed a commit
to Elchanz3/android_kernel_samsung_exynos9820
that referenced
this issue
Mar 22, 2023
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Elchanz3
pushed a commit
to kimboKTeam/android_kernel_samsung_exynos9820
that referenced
this issue
Mar 25, 2023
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
bggRGjQaUbCoE
pushed a commit
to bggRGjQaUbCoE/android_kernel_samsung_sm8250-mohammad92
that referenced
this issue
Apr 6, 2023
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Rem01Gaming
pushed a commit
to Rem01Gaming/liquid_kernel_realme_even
that referenced
this issue
May 22, 2023
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
intersectRaven
pushed a commit
to intersectRaven/rk356x-kernel
that referenced
this issue
Sep 16, 2023
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50ab673c (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
diphons
pushed a commit
to diphons/D8G_Kernel
that referenced
this issue
Sep 17, 2023
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ratatouille100
pushed a commit
to ratatouille100/kernel_samsung_universal9611
that referenced
this issue
Dec 19, 2023
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
roniwae
pushed a commit
to roniwae/MiuiKernel
that referenced
this issue
Jan 23, 2024
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Dheeraj3031A
pushed a commit
to Dheeraj3031A/kernel_oplus_RMX3461
that referenced
this issue
Jan 31, 2024
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
RT1648
pushed a commit
to RT1648/android_kernel_asus_sdm660
that referenced
this issue
Feb 17, 2024
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Huawei-Dev
pushed a commit
to Huawei-Dev/android_kernel_huawei_hi3660
that referenced
this issue
Apr 13, 2024
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Huawei-Dev
pushed a commit
to Huawei-Dev/android_kernel_huawei_hi3660
that referenced
this issue
May 20, 2024
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Huawei-Dev
pushed a commit
to Huawei-Dev/android_kernel_huawei_hi3660
that referenced
this issue
May 21, 2024
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
dek0der
pushed a commit
to dek0der/kernel_realme_RMX3031
that referenced
this issue
Jun 14, 2024
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ZorEl212
pushed a commit
to ZorEl212/Cuh-Kernel
that referenced
this issue
Jun 15, 2024
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
ZorEl212
pushed a commit
to ZorEl212/android_kernel_xiaomi_ginkgo
that referenced
this issue
Jul 23, 2024
commit 20f3cf5 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
FakeShell
pushed a commit
to FuriLabs/linux-furiphone-krypton
that referenced
this issue
Aug 20, 2024
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
dragonGR
pushed a commit
to dragonGR/kernel_samsung_sm7125
that referenced
this issue
Sep 8, 2024
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
deflamingq
pushed a commit
to deflamingq/kernel_asus_sdm660
that referenced
this issue
Nov 3, 2024
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Andrey0800770
pushed a commit
to Andrey0800770/samsung_sdm845-kernel
that referenced
this issue
Dec 24, 2024
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50a (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
AndroidHQ254
pushed a commit
to A325F/android_kernel_samsung_a32
that referenced
this issue
Jan 3, 2025
commit 20f3cf5f860f9f267a6a6e5642d3d0525edb1814 upstream. If we ever see a touch report with contact count data we initialize several variables used to read the contact count in the pre-report phase. These variables are never reset if we process a report which doesn't contain a contact count, however. This can cause the pre- report function to trigger a read of arbitrary memory (e.g. NULL if we're lucky) and potentially crash the driver. This commit restores resetting of the variables back to default "none" values that were used prior to the commit mentioned below. Link: linuxwacom/input-wacom#276 Fixes: 003f50ab673c (HID: wacom: Update last_slot_field during pre_report phase) CC: [email protected] Signed-off-by: Jason Gerecke <[email protected]> Reviewed-by: Ping Cheng <[email protected]> Signed-off-by: Jiri Kosina <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
When we connect a touchscreen (usb) and hand moving on the screen in this moment, we get kernel panic.
OS: Oracle linux 8.4
Kernel version: 5.4.17-2102.202.5.el8uek.x86_64
wacom.ko: last current version (48)
Wacom model: Wacom cintiq pro 24
vmcore-dmesg.txt:
What can we do to solve this problem?
Thanks.
The text was updated successfully, but these errors were encountered: