Input: synaptics-rmi4 - fix F55 transmitter electrode count typo
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0739c65e799d4a93fe573ed23255a71fcfcc5438, 6058f0fea10f3caf63a435677358d1b8e9325114, 6484e00d6778fdf2209cd75940bc3902b276457f.
Low priority for now. Upgrade to Linux Linux 0739c65e799d4a93fe573ed23255a71fcfcc5438, 6058f0fea10f3caf63a435677358d1b8e9325114, 6484e00d6778fdf2209cd75940bc3902b276457f or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: Input: synaptics-rmi4 - fix F55 transmitter electrode count typo During F55 sensor detection, the transmitter (TX) electrode count was incorrectly assigned the value of the receiver (RX) electrode count due to copy-paste typos. This incorrect value was then propagated to the driver data and used by F54 to determine the diagnostics report size. On devices with more RX than TX electrodes, this inflated the perceived TX count, leading to incorrect report size calculations and potential out-of-bounds buffer accesses. Fix the typos by correctly assigning the TX electrode counts.
- Published
- Sep 3, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- —
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.10affected
- 6adba43fd222ea362c36296d1a6897c2e28fdc8e and later · before 6484e00d6778fdf2209cd75940bc3902b276457faffected · git
- 6adba43fd222ea362c36296d1a6897c2e28fdc8e and later · before db4e20265ebda729610ca5cf45ca9437462c3f36affected · git
- 6adba43fd222ea362c36296d1a6897c2e28fdc8e and later · before a6d9646e77da7cab2dff7043a8e9f75e23b836bcaffected · git
- 6adba43fd222ea362c36296d1a6897c2e28fdc8e and later · before 0739c65e799d4a93fe573ed23255a71fcfcc5438affected · git
- 6adba43fd222ea362c36296d1a6897c2e28fdc8e and later · before 9759502f5cd71805923457f183ae5b9533e20c7baffected · git
- 6adba43fd222ea362c36296d1a6897c2e28fdc8e and later · before 9b184c8337c6e12df129399007735a7fbcbbcb7baffected · git
- 6adba43fd222ea362c36296d1a6897c2e28fdc8e and later · before a81cafe3c3c2f8494063385a7b0ea7ff407bf19faffected · git
- 6adba43fd222ea362c36296d1a6897c2e28fdc8e and later · before 6058f0fea10f3caf63a435677358d1b8e9325114affected · git
- before 4.10not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.10-1 | 7.1.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80738Sep 3, 2026 · bpf: Check sk_state before sk_protocol in bpf_tcp_*_syncookie29Monitor
- ← EarlierCVE-2026-80747Sep 3, 2026 · drm/amdkfd: Add bounds check for CRAT subtype length32Monitor
- Later →CVE-2026-80755Sep 3, 2026 · selinux: reject a permission value exceeding the class permission count0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0739c65e799d4a93fe573ed23255a71fcfcc5438 | Vendor (CNA) |
| Linux Linux | 6058f0fea10f3caf63a435677358d1b8e9325114 | Vendor (CNA) |
| Linux Linux | 6484e00d6778fdf2209cd75940bc3902b276457f | Vendor (CNA) |
| Linux Linux | 9759502f5cd71805923457f183ae5b9533e20c7b | Vendor (CNA) |
| Linux Linux | 9b184c8337c6e12df129399007735a7fbcbbcb7b | Vendor (CNA) |
| Linux Linux | a6d9646e77da7cab2dff7043a8e9f75e23b836bc | Vendor (CNA) |
| Linux Linux | a81cafe3c3c2f8494063385a7b0ea7ff407bf19f | Vendor (CNA) |
| Linux Linux | db4e20265ebda729610ca5cf45ca9437462c3f36 | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/6058f0fea10f3caf63a435677358d1b8e9325114
- git.kernel.org/stable/c/6484e00d6778fdf2209cd75940bc3902b276457f
- git.kernel.org/stable/c/9759502f5cd71805923457f183ae5b9533e20c7b
- git.kernel.org/stable/c/9b184c8337c6e12df129399007735a7fbcbbcb7b
- git.kernel.org/stable/c/a6d9646e77da7cab2dff7043a8e9f75e23b836bc
- git.kernel.org/stable/c/a81cafe3c3c2f8494063385a7b0ea7ff407bf19f
- git.kernel.org/stable/c/db4e20265ebda729610ca5cf45ca9437462c3f36
Vendor advisories and official records. Exploit/PoC links are deliberately left out.