{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-98475 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-98475 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98475 and fix it if it is affected.\n\nWhat it is: CVE-2026-98475 is a memory corruption vulnerability in Linux, published on 18 Oct 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-98475 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-98475/ (Markdown: https://insights.sbomify.com/CVE-2026-98475/index.md)","id":"CVE-2026-98475","markdown":"https://insights.sbomify.com/CVE-2026-98475/index.md","name":"CVE-2026-98475","record":{"aliases":["BELL-CVE-2026-98475","DEBIAN-CVE-2026-98475","GHSA-p4wm-c7q2-mpq9","UBUNTU-CVE-2026-98475"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"none","summary":"A kernel flaw allows firmware to use incorrect addresses for channel measurement data, potentially leading to memory corruption or data exposure on s390 systems.","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/cmf: Fix virtual vs physical address confusion\n\nThe measurement block address is an absolute address. Define the\nassociated schib_config and schib fields as dma64_t to enable automatic\ndetection of incorrect assignments. Also add the missing virt_to_dma64()\ntranslation.\n\nWithout this fix, a wrong address will be used by firmware when storing\nextended format channel measurement data on kernels built with\nCONFIG_RANDOMIZE_IDENTITY_BASE=y.","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/cmf: Fix virtual vs physical address confusion","id":"CVE-2026-98475","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":"s390/cio: Fix NULL pointer dereference in ccw_device_get_util_str()","id":"CVE-2026-98476"},"packages":[],"prev":{"headline":"s390/pci: Fix missing device lock in zpci_report_status()","id":"CVE-2026-98474"},"products":["Linux"],"published":"2026-10-18","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 kernel flaw allows firmware to use incorrect addresses for channel measurement data, potentially leading to memory corruption or data exposure on s390 systems.","url":"https://insights.sbomify.com/CVE-2026-98475/"}