{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98024 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98024 is a memory corruption 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-98024 and fix it if it is affected.\n\nWhat it is: CVE-2026-98024 is a memory corruption 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-98024 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-98024/ (Markdown: https://insights.sbomify.com/CVE-2026-98024/index.md)","id":"CVE-2026-98024","markdown":"https://insights.sbomify.com/CVE-2026-98024/index.md","name":"CVE-2026-98024","record":{"aliases":["AZL-104307","BELL-CVE-2026-98024","DEBIAN-CVE-2026-98024","GHSA-8x93-8jfm-fwvw","UBUNTU-CVE-2026-98024"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel driver","requires_auth":"none","summary":"A memory corruption vulnerability in the s390 ISM driver allows local attackers to cause slab allocator corruption or potential code execution via improper memory freeing.","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\ns390/ism: folio_put() after error\n\ndmb-\u003ecpu_addr was allocated via folio_alloc(). Use folio_put() instead of\nkfree() in the error exit of ism_alloc_dmb() to avoid slab allocator\ncorruption.\n\nWhile at it, reset dmb-\u003ecpu_addr after folio_put to avoid unintentional UAF\nby future callers.","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":"s390/ism: folio_put() after error","id":"CVE-2026-98024","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":"net: usb: cx82310_eth: drop URB after 0xffff reboot sentinel to prevent partial_data heap overflow","id":"CVE-2026-98025"},"packages":[],"prev":{"headline":"vxlan: reject dynamic fdb entries that reference a nexthop id","id":"CVE-2026-98023"},"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 memory corruption vulnerability in the s390 ISM driver allows local attackers to cause slab allocator corruption or potential code execution via improper memory freeing.","url":"https://insights.sbomify.com/CVE-2026-98024/"}