Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98201

Input: zero ff_effect before compat copy in input_ff_effect_from_user

Description

In the Linux kernel, the following vulnerability has been resolved: Input: zero ff_effect before compat copy in input_ff_effect_from_user In the compat path input_ff_effect_from_user() aliases the caller's native struct ff_effect with the smaller struct ff_effect_compat and copies only the compat sized prefix: compat_effect = (struct ff_effect_compat *)effect; if (copy_from_user(compat_effect, buffer, sizeof(struct ff_effect_compat))) The tail of the native structure is never written. Callers pass an uninitialized on-stack object, for example evdev_do_ioctl() for EVIOCSFF, so those bytes keep their previous stack contents. input_ff_upload() then stores the full native structure in ff->effects[id], from where a uinput based force feedback daemon can read it back via UI_BEGIN_FF_UPLOAD, disclosing kernel stack memory to userspace. Zero the effect before the compat copy.

Timeline

  1. ID reserved

    By Linux

  2. · 11 days later

    Published

  3. · 13 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (11 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 2d56f3a32c0e62f99c043d2579840f9731fe5855 – < ed0905fda39682d3da7937184397d3276abbffa8
    • affected 2d56f3a32c0e62f99c043d2579840f9731fe5855 – < ec174c2ab1abb76b20fa167c6db848c3d97aa838
    • affected 2d56f3a32c0e62f99c043d2579840f9731fe5855 – < 6c26681c5668c973bd0e951407d670ac60d9cd66
    • affected 2d56f3a32c0e62f99c043d2579840f9731fe5855 – < c5e573bb095d502be7cbbaa99c26a20984111c6d
    • affected 2d56f3a32c0e62f99c043d2579840f9731fe5855 – < b878720e8bcaa4cf7163a5081f904dd6baf11b2c
    • affected 2d56f3a32c0e62f99c043d2579840f9731fe5855 – < 0d05b43b55d4784a42ce8fb318175f8ad7d9af5a
    • affected 2d56f3a32c0e62f99c043d2579840f9731fe5855 – < ed0406e490f48ed180df140fe2a81be26bccb1a9
    • affected 2d56f3a32c0e62f99c043d2579840f9731fe5855 – < f84819ef8d66931ee3998fee3c4f03230f4cb6cc
  • Linux · Linux

    • affected 2.6.29
    • unaffected < 2.6.29
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.54 – ≤ 6.18.*
    • unaffected 7.2.8 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98201 badge
[![CVE-2026-98201](https://cveledger.app/badge/CVE-2026-98201.svg)](https://cveledger.app/cve/CVE-2026-98201)

Record last updated .