CVE-2026-46232
Received Received - Intake
HID PlayStation Driver Touch Report Array Overflow

Publication date: 2026-05-28

Last updated on: 2026-05-28

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: HID: playstation: Clamp num_touch_reports A device would never lie about the number of touch reports would it? If it does the loop in dualshock4_parse_report will read off the end of the touch_reports array, up to about 2 KiB for the maximum number of 256 loop iteraions. The data that is read is emitted via evdev if the DS4_TOUCH_POINT_INACTIVE bit happens to be set. Protect against this by clamping the num_touch_reports value provided by the device to the maximum size of the touch_reports array.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-28
Last Modified
2026-05-28
Generated
2026-05-28
AI Q&A
2026-05-28
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux_kernel linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in the Linux kernel's handling of PlayStation controller touch reports. Specifically, the function dualshock4_parse_report processes touch input data from the device. If a device falsely reports the number of touch reports, the function may read beyond the allocated touch_reports array, potentially up to about 2 KiB of memory. This happens because the loop iterates up to the reported number of touch reports without proper validation. The vulnerability is mitigated by clamping the num_touch_reports value to the maximum size of the touch_reports array, preventing out-of-bounds reads.


How can this vulnerability impact me? :

If exploited, this vulnerability could cause the Linux kernel to read memory beyond the intended buffer when processing touch input from a PlayStation controller. This out-of-bounds read could potentially expose sensitive kernel memory data or cause system instability. The data read might be emitted via the evdev interface, which could lead to unintended information disclosure or other unpredictable behavior.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart