# CVE-2026-46232: HID: playstation: Clamp num_touch_reports

> A malicious PlayStation controller can trigger an out-of-bounds read in the Linux kernel HID driver, potentially leaking memory or causing a crash.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2026
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2026-46232, DEBIAN-CVE-2026-46232, GHSA-6gfw-vfv3-ggqr, ROOT-OS-UBUNTU-2404-CVE-2026-46232, UBUNTU-CVE-2026-46232

## What is CVE-2026-46232?

CVE-2026-46232 is a high-severity memory corruption vulnerability in Linux kernel, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-46232?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2026-46232?

Apply the vendor's patch.

## Is CVE-2026-46232 being exploited?

There is no known exploitation of CVE-2026-46232 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-46232 and fix it if it is affected.

What it is: CVE-2026-46232 is a high-severity memory corruption vulnerability in Linux kernel, published on 28 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-46232 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-46232/ (Markdown: https://insights.sbomify.com/CVE-2026-46232/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46232
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46232
- OSV: https://osv.dev/vulnerability/CVE-2026-46232

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-46232/
Summaries are generated and may contain mistakes; the official description above is the record.