{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-40035 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-40035 is a vulnerability in Linux, published on 28 Oct 2025. 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-2025-40035 and fix it if it is affected.\n\nWhat it is: CVE-2025-40035 is a vulnerability in Linux, published on 28 Oct 2025. 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-2025-40035 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-2025-40035/ (Markdown: https://insights.sbomify.com/CVE-2025-40035/index.md)","id":"CVE-2025-40035","markdown":"https://insights.sbomify.com/CVE-2025-40035/index.md","name":"CVE-2025-40035","record":{"aliases":["AZL-68852","BELL-CVE-2025-40035","DEBIAN-CVE-2025-40035","GHSA-8c35-rp3g-c86r","ROOT-OS-DEBIAN-11-CVE-2025-40035","ROOT-OS-UBUNTU-2204-CVE-2025-40035","ROOT-OS-UBUNTU-2404-CVE-2025-40035","UBUNTU-CVE-2025-40035"],"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 uinput interface due to missing zero-initialization in the ff_effect_compat structure.","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: uinput - zero-initialize uinput_ff_upload_compat to avoid info leak\n\nStruct ff_effect_compat is embedded twice inside\nuinput_ff_upload_compat, contains internal padding. In particular, there\nis a hole after struct ff_replay to satisfy alignment requirements for\nthe following union member. Without clearing the structure,\ncopy_to_user() may leak stack data to userspace.\n\nInitialize ff_up_compat to zero before filling valid fields.","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: uinput - zero-initialize uinput_ff_upload_compat to avoid info leak","id":"CVE-2025-40035","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":8,"next":{"headline":"misc: fastrpc: fix possible map leak in fastrpc_put_args","id":"CVE-2025-40036"},"packages":[],"prev":{"headline":"PCI/AER: Avoid NULL pointer dereference in aer_ratelimit()","id":"CVE-2025-40034"},"products":["Linux"],"published":"2025-10-28","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-05-11","vendors":["Linux"]},"summary":"A local attacker can read uninitialized kernel stack memory via the uinput interface due to missing zero-initialization in the ff_effect_compat structure.","url":"https://insights.sbomify.com/CVE-2025-40035/"}