{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-72011 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-72011 is a vulnerability in Linux, published on 15 Aug 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-72011 and fix it if it is affected.\n\nWhat it is: CVE-2026-72011 is a vulnerability in Linux, published on 15 Aug 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-72011 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-72011/ (Markdown: https://insights.sbomify.com/CVE-2026-72011/index.md)","id":"CVE-2026-72011","markdown":"https://insights.sbomify.com/CVE-2026-72011/index.md","name":"CVE-2026-72011","record":{"aliases":["BELL-CVE-2026-72011","DEBIAN-CVE-2026-72011","GHSA-gm6x-fg6p-956v","UBUNTU-CVE-2026-72011"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A missing speculative execution barrier in the Linux kernel s390 diag code allows local attackers to potentially read sensitive memory via side-channel attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"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/diag: Add missing array_index_nospec() call to memtop_get_page_count()\n\n'level' is user space controlled and used to read from an array. Add the\nmissing array_index_nospec() call to prevent speculative execution.","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/diag: Add missing array_index_nospec() call to memtop_get_page_count()","id":"CVE-2026-72011","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"tracing/osnoise: Call synchronize_rcu() when unregistering","id":"CVE-2026-72012"},"packages":[],"prev":{"headline":"cgroup/cpuset: rebind mm mempolicy to effective_mems, not mems_allowed","id":"CVE-2026-72010"},"products":["Linux"],"published":"2026-08-15","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-08-17","vendors":["Linux"]},"summary":"A missing speculative execution barrier in the Linux kernel s390 diag code allows local attackers to potentially read sensitive memory via side-channel attacks.","url":"https://insights.sbomify.com/CVE-2026-72011/"}