Linux Kernel: security vulnerability (CVE-2026-46232)
Published Last modified Sources: SUSE, HKCERT, Ubuntu, BSI, CVE.org, Msrc Update Guide, EUVD, OSV
What is affected, what to do
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.
Update Linux Kernel to version 6.6.140, Linux Kernel to version 6.12.90, Linux Kernel to version 6.18.32.
- Affected
- Linux Kernel
lt 6.2..6.6.140 - Linux Kernel
lt 6.7..6.12.90 - Linux Kernel
lt 6.13..6.18.32 - Linux Kernel
lt 6.19..7.0.9
- Linux Kernel
- Fixed in
- Linux Kernel
6.6.140 - Linux Kernel
6.12.90 - Linux Kernel
6.18.32 - Linux Kernel
7.0.9 - Linux Kernel
7.1
- Linux Kernel
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
8.1
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: Vendor (CNA), CVSS v3
8.1
CVSS v3
Severity High on the scale from 0 to 10.
Source: SUSE, HKCERT, Ubuntu, BSI, CVE.org, Msrc Update Guide, EUVD, OSV
0.3 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 17.5
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 60.68 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 8.1 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 8.1
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.3 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 17.5
- Elevated — this CVE ranks above at least 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: suse_csaf, HKCERT (CC BY 3.0 HK) · HKCERT rating: medium, Ubuntu Security Notices, BSI WID Portal, BSI CSAF, NVD (NIST), CVE.org (MITRE), Microsoft Security Update Guide, ENISA EUVD, OSV (Open Source Vulnerabilities), cvelistv5
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Linux | Linux |
|
|
| Android |
|
| |
| Android 14 |
|
| |
| Android 15 |
|
| |
| Android 16 |
|
| |
| Android 17 |
|
| |
| Android Automotive OS |
|
| |
| Android XR |
|
| |
| android | :linux_kernel: |
|
|
Vendors and products
Affected operating systems
| Linux | ubuntu | linux-oracle-7.0 | noble |
| Linux | linux | linux_kernel | 7.1 |
| Linux | linux | linux_kernel | — |
References & sources
- git.kernel.orgstable/c/0bc4cf1a6ba00fb8c074531b179bc7b97502fbc4euvd, Patch
- git.kernel.orgstable/c/9c031b24aed6733b6dcc5d98527875b8654a04e9euvd, Patch
- git.kernel.orgstable/c/7812694752a5f295eaa05a093b90a2c332666051euvd, Patch
- git.kernel.orgstable/c/208f6d5b1dfd6399bc6af9e11f27f1f496243ed0euvd, Patch
- git.kernel.orgstable/c/cac61b58a3b6340c52afa06bb15eac033158db2feuvd, Patch
- source.android.comsecurity/bulletin/2026-11-01advisory
- android.googlesource.comkernel/common/+/a5dca2389c9e2e3c43bedb72f556bf0eafe0cffdfix
- android.googlesource.comkernel/common/+/aab498d0885fd97d010a0cd1013a3479269f41d0fix
- android.googlesource.comkernel/common/+/60eed3576bb0cf3ceb11625240beb63b48f6e3c2fix
- android.googlesource.comkernel/common/+/cf8ba5678385b2b8832ed2e87c035925eb12bc4afix
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Initial analysis by NVDNVD
Newly listed as affected:- Linux Kernel (6.2 – before 6.6.140; 6.13 – before 6.18.32; 6.7 – before 6.12.90; 6.19 – before 7.0.9; 3 individual versions)
New references:- https://git.kernel.org/stable/c/0bc4cf1a6ba00fb8c074531b179bc7b97502fbc4
- https://git.kernel.org/stable/c/208f6d5b1dfd6399bc6af9e11f27f1f496243ed0
- https://git.kernel.org/stable/c/7812694752a5f295eaa05a093b90a2c332666051
- https://git.kernel.org/stable/c/9c031b24aed6733b6dcc5d98527875b8654a04e9
and 1 more reference
Show 7 original changes
Individual changes of this event as published by NVD Type Action Before After Weakness type (CWE) added —NVD-CWE-noinfoProduct configuration added —OR *cpe:2.3:o:linux:linux_kernel:7.1:rc1:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc2:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:7.1:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.140 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.32 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.90 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.9Reference type added —kernel.org: https://git.kernel.org/stable/c/0bc4cf1a6ba00fb8c074531b179bc7b97502fbc4 Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/208f6d5b1dfd6399bc6af9e11f27f1f496243ed0 Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/7812694752a5f295eaa05a093b90a2c332666051 Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/9c031b24aed6733b6dcc5d98527875b8654a04e9 Types: PatchReference type added —kernel.org: https://git.kernel.org/stable/c/cac61b58a3b6340c52afa06bb15eac033158db2f Types: PatchSource identifier: nvd@nist.gov
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-46232"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-46232.svg?lang=en" alt="CVE-2026-46232 – NEOSEC Intel" height="20"></a>