{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89437 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89437 is a memory corruption 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-89437 and fix it if it is affected.\n\nWhat it is: CVE-2026-89437 is a memory corruption 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-89437 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-89437/ (Markdown: https://insights.sbomify.com/CVE-2026-89437/index.md)","id":"CVE-2026-89437","markdown":"https://insights.sbomify.com/CVE-2026-89437/index.md","name":"CVE-2026-89437","record":{"aliases":["AZL-100247","BELL-CVE-2026-89437","DEBIAN-CVE-2026-89437","GHSA-8554-6hg6-mf5q","UBUNTU-CVE-2026-89437"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A memory leak in the Linux kernel int1092 driver allows local attackers to cause denial of service through resource exhaustion.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nplatform/x86: int1092: Fix potential memory leak in sar_probe()\n\nThe memory allocated for device_mode_info in parse_package() called by\nsar_get_data() is not freed in some of the error paths in sar_probe().\nFix that by converting to use device managed allocations.","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":"platform/x86: int1092: Fix potential memory leak in sar_probe()","id":"CVE-2026-89437","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"platform/x86: ISST: Validate logical CPU id and clos id","id":"CVE-2026-89438"},"packages":[],"prev":{"headline":"platform/x86: panasonic-laptop: Fix sentinel write past pcc-\u003esinf[]","id":"CVE-2026-89436"},"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-21","vendors":["Linux"]},"summary":"A memory leak in the Linux kernel int1092 driver allows local attackers to cause denial of service through resource exhaustion.","url":"https://insights.sbomify.com/CVE-2026-89437/"}