Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64273: Input: iforce - bound the device-reported force-feedback effect index

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.16% (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 0e9943d2e4c63496b6ca84bc66fd3c71d40558e2, 6c0f2901c9d325d4a0574c4237fd507810d225ff, 70019779325f2bb5f5a4098e91e79c655f50fcef.

Low priority for now. Upgrade to Linux Linux 0e9943d2e4c63496b6ca84bc66fd3c71d40558e2, 6c0f2901c9d325d4a0574c4237fd507810d225ff, 70019779325f2bb5f5a4098e91e79c655f50fcef 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: iforce - bound the device-reported force-feedback effect index iforce_process_packet() handles a status report (packet id 0x02) by taking a force-feedback effect index straight from the device wire and using it to address the per-effect state array: i = data[1] & 0x7f; if (data[1] & 0x80) { if (!test_and_set_bit(FF_CORE_IS_PLAYED, iforce->core_effects[i].flags)) ... } else if (test_and_clear_bit(FF_CORE_IS_PLAYED, iforce->core_effects[i].flags)) { ... } The index is masked only with 0x7f, so it ranges 0..127, but core_effects[] holds only IFORCE_EFFECTS_MAX (32) entries. For an index of 32..127 the test_and_set_bit()/test_and_clear_bit() is an out-of-bounds single-bit read-modify-write past the array. core_effects[] is the second-to-last member of struct iforce, so the write lands in the trailing members and beyond the embedding kzalloc()'d iforce_serio / iforce_usb object. data[1] is unvalidated device payload on both transports (the USB interrupt endpoint and serio), and the status path is not gated on force feedback being present, so a malicious or counterfeit device can set or clear a bit at an attacker-chosen offset past the object. Reject an out-of-range index instead of indexing with it. Bound against the array dimension IFORCE_EFFECTS_MAX rather than dev->ff->max_effects so the check guarantees memory safety regardless of how many effects the device registered. A legitimate "effect started/stopped" status always carries an index below IFORCE_EFFECTS_MAX, so well-formed devices are unaffected; the neighbouring mark_core_as_ready() loop is already bounded and is left untouched.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Jul 25, 2026
Updated
Oct 24, 2026
EPSS
0.1% · 6th percentile

Report tools

JSON

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%

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.

Follow CVE-2026-64273

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel2.6.12.1 and later · before 5.10.261
  • linux linux kernel5.11 and later · before 5.15.212
  • linux linux kernel5.16 and later · before 6.1.178
  • linux linux kernel6.2 and later · before 6.6.145
  • linux linux kernel6.7 and later · before 6.12.96
  • linux linux kernel6.13 and later · before 6.18.39
  • linux linux kernel6.19 and later · before 7.1.4
  • linux linux kernel2.6.12

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

    • 2.6.12affected
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before b1b79e89bc33e4c682d3df7ae2aadc62b5a0c310affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before d10b0507fa0f5b46764b178e3271f9012f2df677affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 6c0f2901c9d325d4a0574c4237fd507810d225ffaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before c21295616a8a52b9a5f18cd4ca8c73030eda3d4faffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before e5fa31f0550b55d80045669ae9080dd5b88abffaaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 70019779325f2bb5f5a4098e91e79c655f50fcefaffected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before a40250f97c312e000e3616c9074022311a0efbc3affected · git
    • 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and later · before 0e9943d2e4c63496b6ca84bc66fd3c71d40558e2affected · git
    • before 2.6.12not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.180-16.1.180-1
Debian:12linux-6.12before 6.12.100-1~deb12u16.12.100-1~deb12u1
Debian:13linuxbefore 6.12.96-16.12.96-1
Debian:14linuxbefore 7.1.4-17.1.4-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2026-64271Jul 25, 2026 · Input: touchwin - reset the packet index on every complete packet
    31Monitor
  • ← EarlierCVE-2026-64272Jul 25, 2026 · Input: mms114 - fix touch indexing for MMS134S and MMS136
    31Monitor
  • Later →CVE-2026-64274Jul 25, 2026 · Input: goodix - clamp the device-reported contact count
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux0e9943d2e4c63496b6ca84bc66fd3c71d40558e2Vendor (CNA)
Linux Linux6c0f2901c9d325d4a0574c4237fd507810d225ffVendor (CNA)
Linux Linux70019779325f2bb5f5a4098e91e79c655f50fcefVendor (CNA)
Linux Linuxa40250f97c312e000e3616c9074022311a0efbc3Vendor (CNA)
Linux Linuxb1b79e89bc33e4c682d3df7ae2aadc62b5a0c310Vendor (CNA)
Linux Linuxc21295616a8a52b9a5f18cd4ca8c73030eda3d4fVendor (CNA)
Linux Linuxd10b0507fa0f5b46764b178e3271f9012f2df677Vendor (CNA)
Linux Linuxe5fa31f0550b55d80045669ae9080dd5b88abffaVendor (CNA)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package 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.

EPSS, last 120 days

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.

Finders, 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.

  • CVE-2026-640186 days apartnet: mana: validate rx_req_idx to prevent out-of-bounds array access
    37Monitor
  • CVE-2026-4311080 days apartwifi: brcmfmac: validate bsscfg indices in IF events
    35Monitor
  • CVE-2026-4317280 days apartwifi: iwlwifi: fix 22000 series SMEM parsing
    35Monitor
  • CVE-2026-23246129 days apartwifi: mac80211: bounds-check link_id in ieee80211_ml_reconfiguration
    35Monitor
  • CVE-2026-642710 days apartInput: touchwin - reset the packet index on every complete packet
    31Monitor
  • CVE-2026-643240 days apartudf: validate free block extents against the partition length
    31Monitor

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

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records