{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98201 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98201 is a vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-98201 and fix it if it is affected.\n\nWhat it is: CVE-2026-98201 is a vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-98201 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-98201/ (Markdown: https://insights.sbomify.com/CVE-2026-98201/index.md)","id":"CVE-2026-98201","markdown":"https://insights.sbomify.com/CVE-2026-98201/index.md","name":"CVE-2026-98201","record":{"aliases":["AZL-106182","BELL-CVE-2026-98201","DEBIAN-CVE-2026-98201","GHSA-hc65-vq9g-6pfq","UBUNTU-CVE-2026-98201"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can read uninitialized kernel stack memory via the input subsystem's force feedback compatibility path, potentially leaking sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nInput: zero ff_effect before compat copy in input_ff_effect_from_user\n\nIn the compat path input_ff_effect_from_user() aliases the caller's\nnative struct ff_effect with the smaller struct ff_effect_compat and\ncopies only the compat sized prefix:\n\n\tcompat_effect = (struct ff_effect_compat *)effect;\n\n\tif (copy_from_user(compat_effect, buffer,\n\t\t\t   sizeof(struct ff_effect_compat)))\n\nThe tail of the native structure is never written. Callers pass an\nuninitialized on-stack object, for example evdev_do_ioctl() for\nEVIOCSFF, so those bytes keep their previous stack contents.\ninput_ff_upload() then stores the full native structure in\nff-\u003eeffects[id], from where a uinput based force feedback daemon can\nread it back via UI_BEGIN_FF_UPLOAD, disclosing kernel stack memory to\nuserspace.\n\nZero the effect before the compat copy.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Input: zero ff_effect before compat copy in input_ff_effect_from_user","id":"CVE-2026-98201","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":8,"next":{"headline":"Input: synaptics-rmi4 - fix GPF in suspend and resume when unbound","id":"CVE-2026-98202"},"packages":[],"prev":{"headline":"hwmon: (hp-wmi-sensors) Fix use-after-free in fungible_show()","id":"CVE-2026-98200"},"products":["Linux"],"published":"2026-10-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A local attacker can read uninitialized kernel stack memory via the input subsystem's force feedback compatibility path, potentially leaking sensitive data.","url":"https://insights.sbomify.com/CVE-2026-98201/"}