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.
Security readout for executives and security teams
Plain-English summary
A malicious or faulty PlayStation-compatible controller can make Linux read beyond an internal touch-report array. Some unintended kernel-memory data may then reach the input-event interface, creating possible information disclosure; the supplied CVSS also indicates potential availability impact. Systems that never accept affected controllers have lower practical exposure.
Executive priority
Treat as a high-priority kernel update where untrusted peripherals can reach Linux systems. Controlled environments with no relevant controllers can use normal patch cadence after confirming exposure. Focus first on publicly accessible, shared, or sensitive systems because the documented behavior can disclose kernel memory.
Technical view
The Linux HID PlayStation driver's dualshock4_parse_report function trusted a device-controlled num_touch_reports value. Values exceeding the touch_reports array bounds caused an out-of-bounds read of up to roughly 2 KiB across 256 iterations. Read data could be emitted through evdev when interpreted as having DS4_TOUCH_POINT_INACTIVE set. The resolution clamps the count to the array's capacity.
Likely exposure
Exposure requires an affected Linux kernel and interaction with a device handled as a DualShock 4 controller. Risk is greatest where users can attach untrusted, counterfeit, modified, or compromised controllers. The supplied affected-version data is ambiguous, so downstream vendor advisories and backport status must determine exposure.
Exploitation context
The supplied CVSS is 8.1 with adjacent attack vector, low complexity, no privileges, and no user interaction. CISA KEV status is false, and the bundle provides no evidence of active exploitation or a public exploit. Practical abuse depends on presenting malicious touch-report metadata through a relevant device.
Researcher notes
The documented primitive is a device-controlled out-of-bounds read, not a write. Disclosure through evdev is conditional on read bytes being interpreted with the inactive-point bit set. The supplied narrative does not explain the CVSS availability rating, identify a CWE, or establish exploit reliability. Affected-version entries appear incomplete or flattened and require vendor confirmation.
Mitigation direction
Update to a vendor-supported kernel containing the num_touch_reports clamp or an equivalent backport.
Check distribution or appliance vendor guidance because kernel version numbers alone may not reveal backported fixes.
Until patched, prevent affected systems from accepting untrusted or unnecessary PlayStation-compatible controllers.
Prioritize shared, public-facing, laboratory, or kiosk systems where peripheral access is less controlled.
Validation and detection
Inventory systems running Linux kernels and determine whether the HID PlayStation driver is present or used.
Record exact kernel package, build, and downstream vendor rather than relying only on upstream version numbers.
Confirm vendor changelogs or source include the relevant clamp or one of the cited stable commits.
Test approved controllers after updating to confirm expected input and touch functionality remains available.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-46232 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
6Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.