{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89765 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89765 is a vulnerability in Linux, published on 11 Sep 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-89765 and fix it if it is affected.\n\nWhat it is: CVE-2026-89765 is a vulnerability in Linux, published on 11 Sep 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-89765 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-89765/ (Markdown: https://insights.sbomify.com/CVE-2026-89765/index.md)","id":"CVE-2026-89765","markdown":"https://insights.sbomify.com/CVE-2026-89765/index.md","name":"CVE-2026-89765","record":{"aliases":["AZL-100623","BELL-CVE-2026-89765","DEBIAN-CVE-2026-89765","GHSA-x38g-mr96-v378","UBUNTU-CVE-2026-89765"],"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":"none","summary":"Local attackers can read uninitialized kernel memory via getitimer on sparc64 due to missing zero-initialization of padding bytes.","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\ntimers/itimer: Zero-init old itimerval before copy to userspace\n\nOn native sparc64, struct __kernel_old_timeval contains a four-byte hole\nafter tv_usec because tv_sec is 64-bit while __kernel_suseconds_t is 32-bit.\nput_itimerval() fills only the named fields in a stack-allocated\n__kernel_old_itimerval and copies the entire object to userspace, so\ngetitimer() can expose the two padding holes.\n\nZero-initialize the aggregate before assigning the fields so implicit\npadding is deterministic before it crosses the user/kernel boundary.","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":"timers/itimer: Zero-init old itimerval before copy to userspace","id":"CVE-2026-89765","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":"pidfd: hold exec_update_lock around namespace ioctl","id":"CVE-2026-89766"},"packages":[],"prev":{"headline":"rust: devres: fix race between concurrent revokers","id":"CVE-2026-89764"},"products":["Linux"],"published":"2026-09-11","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":"Local attackers can read uninitialized kernel memory via getitimer on sparc64 due to missing zero-initialization of padding bytes.","url":"https://insights.sbomify.com/CVE-2026-89765/"}