{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80724 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80724 is a high-severity vulnerability in Linux, published on 28 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-80724 and fix it if it is affected.\n\nWhat it is: CVE-2026-80724 is a high-severity vulnerability in Linux, published on 28 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-80724 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-80724/ (Markdown: https://insights.sbomify.com/CVE-2026-80724/index.md)","id":"CVE-2026-80724","markdown":"https://insights.sbomify.com/CVE-2026-80724/index.md","name":"CVE-2026-80724","record":{"aliases":["BELL-CVE-2026-80724","DEBIAN-CVE-2026-80724","GHSA-66mv-wq2c-77c3","UBUNTU-CVE-2026-80724","openSUSE-SU-2026:11703-1"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A guest user can escalate privileges by modifying read-only vmclock data via mprotect, requiring kernel patching.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nptp: vmclock: prevent read-only mappings from becoming writable\n\nvmclock_miscdev_mmap() rejects writable mappings of the shared vmclock\nABI page with -EROFS, but leaves VM_MAYWRITE set.  Userspace can map the\npage read-only and then upgrade it to writable with mprotect(), after\nwhich the guest can corrupt the host-written timekeeping data (sequence\ncounter, UTC time, TSC offset) that the vmclock ABI defines as read-only.\n\nClear VM_MAYWRITE on the read-only path so the mapping cannot be\nupgraded, as i915 does for its read-only objects and as fixed in drm/vc4\n(CVE-2026-68445) and drm/panthor (CVE-2024-53071).","ecosystems":["openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":"2026-08-30","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-30T15:38:11Z","kind":"github_poc","ref":"https://github.com/suruurism/cve-writeups-and-pocs","stars":1,"title":"CVE-2026-80724 PoC + full write-up — Linux kernel ptp/vmclock read-only mapping becomes writable (VM_MAYWRITE). Discovered, reported \u0026 fixed by Abdifatah Suruur (suruurism)"}],"tier":"poc_unverified"},"has_fix":true,"headline":"ptp: vmclock: prevent read-only mappings from becoming writable","id":"CVE-2026-80724","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":1,"n_references":6,"next":{"headline":"net: gro: properly validate BIG TCP aggregation criteria","id":"CVE-2026-80725"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["7.2.3-1.1"],"introduced":["0"],"last_affected":[],"package":"kernel-source","purl":"pkg:rpm/opensuse/kernel-source\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:11703-1"}],"prev":{"headline":"of: reserved_mem: prevent OOB when too many dynamic regions are defined","id":"CVE-2026-80723"},"products":["Linux"],"published":"2026-08-28","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":"A guest user can escalate privileges by modifying read-only vmclock data via mprotect, requiring kernel patching.","url":"https://insights.sbomify.com/CVE-2026-80724/"}