{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89502 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89502 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-89502 and fix it if it is affected.\n\nWhat it is: CVE-2026-89502 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-89502 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-89502/ (Markdown: https://insights.sbomify.com/CVE-2026-89502/index.md)","id":"CVE-2026-89502","markdown":"https://insights.sbomify.com/CVE-2026-89502/index.md","name":"CVE-2026-89502","record":{"aliases":["BELL-CVE-2026-89502","DEBIAN-CVE-2026-89502","GHSA-43ww-w2jp-2rjx","UBUNTU-CVE-2026-89502"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"Incorrect memory deallocation in the Linux kernel ring buffer can lead to memory corruption and potential system crashes or code execution.","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\nring-buffer: Free cpu_buffer::free_page with subbuf_order\n\nWhen sub-buffers use an order greater than 0, cpu_buffer-\u003efree_page is\nallocated with subbuf_order. Use the correct order for\ncpu_buffer-\u003efree_page.","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":"ring-buffer: Free cpu_buffer::free_page with subbuf_order","id":"CVE-2026-89502","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ring-buffer: Fix subbuf resize race with ring_buffer_alloc_read_page()","id":"CVE-2026-89503"},"packages":[],"prev":{"headline":"ring-buffer: Hold cpu_buffer::lock when resizing a subbuf","id":"CVE-2026-89501"},"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":"Incorrect memory deallocation in the Linux kernel ring buffer can lead to memory corruption and potential system crashes or code execution.","url":"https://insights.sbomify.com/CVE-2026-89502/"}