Affects the Linux kernel HID subsystem; widely used across servers/edge devices; could impact IT ops.
CVE-2026-46232
Linux kernel HID PS4: clamp touch reports to prevent OOB read.
Is CVE-2026-46232 being exploited?
Not confirmed. CVE-2026-46232 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-46232?
CVE-2026-46232 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-46232?
Yes. A fix has been recorded for CVE-2026-46232. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46232 affect?
CVE-2026-46232 affects Linux kernel (HID: DS4). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46232?
Apply kernel update and reboot.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Kernel out-of-bounds read via DS4 touch data; may disclose kernel data or cause a crash.
Patch when possible
- affected>= 752038248808a7ff176bbdb668f19ae7d2a9816b and < 0bc4cf1a6ba00fb8c074531b179bc7b97502fbc4
- affected>= 752038248808a7ff176bbdb668f19ae7d2a9816b and < 9c031b24aed6733b6dcc5d98527875b8654a04e9
- affected>= 752038248808a7ff176bbdb668f19ae7d2a9816b and < 7812694752a5f295eaa05a093b90a2c332666051
- affected>= 752038248808a7ff176bbdb668f19ae7d2a9816b and < 208f6d5b1dfd6399bc6af9e11f27f1f496243ed0
- affected>= 752038248808a7ff176bbdb668f19ae7d2a9816b and < cac61b58a3b6340c52afa06bb15eac033158db2f
- affected6.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.