{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-68480 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-68480 is a vulnerability in Linux, published on 6 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-68480 and fix it if it is affected.\n\nWhat it is: CVE-2026-68480 is a vulnerability in Linux, published on 6 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-68480 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-68480/ (Markdown: https://insights.sbomify.com/CVE-2026-68480/index.md)","id":"CVE-2026-68480","markdown":"https://insights.sbomify.com/CVE-2026-68480/index.md","name":"CVE-2026-68480","record":{"aliases":["BELL-CVE-2026-68480","DEBIAN-CVE-2026-68480","GHSA-76mh-mwm6-543c","UBUNTU-CVE-2026-68480"],"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":"none","summary":"An attacker can inject interrupts to bypass Safe-RET mitigations, potentially leaking sensitive data via speculative execution.","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\nx86/bugs: Make Safe-RET robust against interrupt injection\n\nAn attacker injecting interrupts while the Safe-RET mitigation executes\non machines affected by SRSO can neutralize the safe return sequence,\npotentially leading to data leakage through speculative execution.\n\nFixup register state as if the Safe-RET sequence executed successfully\nby \"emulating\" it, in a manner of speaking, and avoid executing a RET\ninstruction after returning from the interrupt.","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":"x86/bugs: Make Safe-RET robust against interrupt injection","id":"CVE-2026-68480","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"Apache CXF: Revocation bypass in DefaultEncryptingOAuthDataProvider","id":"CVE-2026-68481"},"packages":[],"prev":{"headline":"Bluetooth: btrtl: validate firmware patch bounds","id":"CVE-2026-68479"},"products":["Linux"],"published":"2026-08-06","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-18","vendors":["Linux"]},"summary":"An attacker can inject interrupts to bypass Safe-RET mitigations, potentially leaking sensitive data via speculative execution.","url":"https://insights.sbomify.com/CVE-2026-68480/"}