CVE-2026-80724: ptp: vmclock: prevent read-only mappings from becoming writable
Noroxi assessment
Priority: Monitor (action score 35/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0ce59c4148ecd1520c5592a63bb3c8991ee2d326, 2496e141827102d6af512950057d402a2cfb2bfc, 2e596e7814ba38cdc129991058b6c254ed37cb11.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0ce59c4148ecd1520c5592a63bb3c8991ee2d326, 2496e141827102d6af512950057d402a2cfb2bfc, 2e596e7814ba38cdc129991058b6c254ed37cb11 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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).
- Published
- Aug 28, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.13affected
- 20503272422693d793b84f88bf23fe4e955d3a33 and later · before 5b4f2bec7bea6c04084d720d731bedee7caf878daffected · git
- 20503272422693d793b84f88bf23fe4e955d3a33 and later · before 3f5677d2f817355147337f0453174c7bb0f3b66aaffected · git
- 20503272422693d793b84f88bf23fe4e955d3a33 and later · before 2496e141827102d6af512950057d402a2cfb2bfcaffected · git
- 20503272422693d793b84f88bf23fe4e955d3a33 and later · before 2e596e7814ba38cdc129991058b6c254ed37cb11affected · git
- 20503272422693d793b84f88bf23fe4e955d3a33 and later · before 0ce59c4148ecd1520c5592a63bb3c8991ee2d326affected · git
- 20503272422693d793b84f88bf23fe4e955d3a33 and later · before a5edadbae57e2298a56cf7a4e774a027905a331faffected · git
- before 6.13not affected · semver
- 6.18.47 and later · up to and including 6.18.*not affected · semver
- 6.18.50 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:14 | linux | before 7.1.12-1 | 7.1.12-1 |
| openSUSE:Tumbleweed | kernel-source | before 7.2.3-1.1 | 7.2.3-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80722Aug 28, 2026 · wifi: mac80211: validate individual TWT params before driver setup35Monitor
- ← EarlierCVE-2026-80723Aug 28, 2026 · of: reserved_mem: prevent OOB when too many dynamic regions are defined33Monitor
- Later →CVE-2026-80725Aug 29, 2026 · net: gro: properly validate BIG TCP aggregation criteria39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0ce59c4148ecd1520c5592a63bb3c8991ee2d326 | Vendor (CNA) |
| Linux Linux | 2496e141827102d6af512950057d402a2cfb2bfc | Vendor (CNA) |
| Linux Linux | 2e596e7814ba38cdc129991058b6c254ed37cb11 | Vendor (CNA) |
| Linux Linux | 3f5677d2f817355147337f0453174c7bb0f3b66a | Vendor (CNA) |
| Linux Linux | 5b4f2bec7bea6c04084d720d731bedee7caf878d | Vendor (CNA) |
| Linux Linux | a5edadbae57e2298a56cf7a4e774a027905a331f | Vendor (CNA) |
| debian:linux | 7.1.12-1 · Debian:14 | Package registry (OSV) |
| opensuse:kernel-source | 7.2.3-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:1 | 2026-08-30 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+2 d
- TodayNov 8, 2026+72 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0945 · Aug 31, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/2496e141827102d6af512950057d402a2cfb2bfc
- git.kernel.org/stable/c/2e596e7814ba38cdc129991058b6c254ed37cb11
- git.kernel.org/stable/c/3f5677d2f817355147337f0453174c7bb0f3b66a
- git.kernel.org/stable/c/5b4f2bec7bea6c04084d720d731bedee7caf878d
- git.kernel.org/stable/c/a5edadbae57e2298a56cf7a4e774a027905a331f
Vendor advisories and official records. Exploit/PoC links are deliberately left out.