{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-97617 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-97617 is a vulnerability in Linux, published on 25 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-97617 and fix it if it is affected.\n\nWhat it is: CVE-2026-97617 is a vulnerability in Linux, published on 25 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-97617 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-97617/ (Markdown: https://insights.sbomify.com/CVE-2026-97617/index.md)","id":"CVE-2026-97617","markdown":"https://insights.sbomify.com/CVE-2026-97617/index.md","name":"CVE-2026-97617","record":{"aliases":["BELL-CVE-2026-97617","DEBIAN-CVE-2026-97617","GHSA-vwfx-985h-jqvx","UBUNTU-CVE-2026-97617"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A race condition in the Linux kernel ring buffer allows local attackers to corrupt memory mappings, potentially leading to privilege escalation or code execution.","user_interaction":"not_required","vuln_class":"race_condition"},"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: Check resize_disabled before publishing the new subbuf order\n\nring_buffer_subbuf_order_set() stores the new order and only then walks\nthe CPUs, returning -EBUSY if any of them has resizing disabled. A user\nmapped buffer has resizing disabled, and __rb_map_vma() reads\nbuffer-\u003esubbuf_order without buffer-\u003emutex, so an mmap of an already\nmapped CPU racing the failing order change sizes the mapping with the\nnew order and inserts pages past the sub-buffer into the VMA.\n\nCheck the CPUs before storing the new order.","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: Check resize_disabled before publishing the new subbuf order","id":"CVE-2026-97617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"io_uring/net: don't overconsume buffers when using MSG_TRUNC","id":"CVE-2026-97618"},"packages":[],"prev":{"headline":"net/sched: act_api: release all action references on NEWACTION failure","id":"CVE-2026-97616"},"products":["Linux"],"published":"2026-09-25","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 race condition in the Linux kernel ring buffer allows local attackers to corrupt memory mappings, potentially leading to privilege escalation or code execution.","url":"https://insights.sbomify.com/CVE-2026-97617/"}