HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 80724 ptp vmclock prevent read only mappings from
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
High · CVSS 8.8CVE-2026-80724

ptp: vmclock: prevent read-only mappings from becoming writableCVE-2026-80724

Answer in brief

CVE-2026-80724 records a High severity (CVSS 8.8) vulnerability in ptp: vmclock: prevent read-only mappings from becoming writable. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 28, 2026Updated Sep 7, 2026Source checked Oct 13, 2026First seen by HOL Aug 28, 2026Material review Sep 7, 2026
Upstream Advisory

Record context

Vulnerability class
Vulnerability
EPSS
Not reported
CWE IDs
Not reported
Source
CVE List V5
Source checked
Oct 13, 2026
References
6 linked sources
Open source record

Key facts

Risk
High · CVSS 8.8
Exploitation
Not marked as known exploited
Affected software
4 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 8.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Linux/Linuxgeneric>=20503272422693d793b84f88bf23fe4e955d3a33 <5b4f2bec7bea6c04084d720d731bedee7caf878d || >=20503272422693d793b84f88bf23fe4e955d3a33 <2496e141827102d6af512950057d402a2cfb2bfc || >=20503272422693d793b84f88bf23fe4e955d3a33 <2e596e7814ba38cdc129991058b6c254ed37cb115b4f2bec7bea6c04084d720d731bedee7caf878d, 2496e141827102d6af512950057d402a2cfb2bfc, 2e596e7814ba38cdc129991058b6c254ed37cb11
Linux/Linuxgeneric>=20503272422693d793b84f88bf23fe4e955d3a33 <5b4f2bec7bea6c04084d720d731bedee7caf878d || >=20503272422693d793b84f88bf23fe4e955d3a33 <2496e141827102d6af512950057d402a2cfb2bfc || >=20503272422693d793b84f88bf23fe4e955d3a33 <2e596e7814ba38cdc129991058b6c254ed37cb11 || >=20503272422693d793b84f88bf23fe4e955d3a33 <a5edadbae57e2298a56cf7a4e774a027905a331f5b4f2bec7bea6c04084d720d731bedee7caf878d, 2496e141827102d6af512950057d402a2cfb2bfc, 2e596e7814ba38cdc129991058b6c254ed37cb11, a5edadbae57e2298a56cf7a4e774a027905a331f
Linux/Linuxgeneric6.13Not reported
Linux/Linuxgeneric>=20503272422693d793b84f88bf23fe4e955d3a33 <5b4f2bec7bea6c04084d720d731bedee7caf878d || >=20503272422693d793b84f88bf23fe4e955d3a33 <3f5677d2f817355147337f0453174c7bb0f3b66a || >=20503272422693d793b84f88bf23fe4e955d3a33 <2496e141827102d6af512950057d402a2cfb2bfc || >=20503272422693d793b84f88bf23fe4e955d3a33 <2e596e7814ba38cdc129991058b6c254ed37cb11 || >=20503272422693d793b84f88bf23fe4e955d3a33 <0ce59c4148ecd1520c5592a63bb3c8991ee2d326 || >=20503272422693d793b84f88bf23fe4e955d3a33 <a5edadbae57e2298a56cf7a4e774a027905a331f5b4f2bec7bea6c04084d720d731bedee7caf878d, 3f5677d2f817355147337f0453174c7bb0f3b66a, 2496e141827102d6af512950057d402a2cfb2bfc, 2e596e7814ba38cdc129991058b6c254ed37cb11, 0ce59c4148ecd1520c5592a63bb3c8991ee2d326, a5edadbae57e2298a56cf7a4e774a027905a331f

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux, Linux/Linux.
  2. 2Review the reported fix. Update Linux/Linux to 5b4f2bec7bea6c04084d720d731bedee7caf878d; Linux/Linux to 5b4f2bec7bea6c04084d720d731bedee7caf878d; Linux/Linux to 5b4f2bec7bea6c04084d720d731bedee7caf878d if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Aug 28, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Sep 7, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Aug 28, 2026

Sources and claim methodology

  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
  • Source referencegit.kernel.org
Upstream source description

In the Linux kernel, the following vulnerability has been resolved: ptp: vmclock: prevent read-only mappings from becoming writable vmclock_miscdev_mmap() rejects writable mappings of the shared vmclock ABI page with -EROFS, but leaves VM_MAYWRITE set. Userspace can map the page read-only and then upgrade it to writable with mprotect(), after which the guest can corrupt the host-written timekeeping data (sequence counter, UTC time, TSC offset) that the vmclock ABI defines as read-only. Clear VM_MAYWRITE on the read-only path so the mapping cannot be upgraded, as i915 does for its read-only objects and as fixed in drm/vc4 (CVE-2026-68445) and drm/panthor (CVE-2024-53071).

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Security Vulnerability identified in IBM TRIRIGA - Zip SlipSame generic ecosystem
  • Edimax BR-6208AC QoS Page formQoS cross site scriptingSame generic ecosystem
  • code-projects Online Ticket Reservation System medallion.sql file information disclosureSame generic ecosystem
  • code-projects Matrimonial System matrimony.sql file accessSame generic ecosystem
  • EricLBuehler mistral.rs media_source.rs is_global_ip server-side request forgerySame generic ecosystem
  • EricLBuehler Mistral.rs handlers.rs calibration_apply path traversalSame generic ecosystem