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).
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Amazon_linux_2023 | — | Upgrade kernel6.18Upgrade bpftool6.18-debuginfoUpgrade kernel6.18-develUpgrade kernel6.18-toolsUpgrade kernel-livepatch-6.18.48-107.148Upgrade kernel6.18-debuginfo-common-x86_64Upgrade kernel6.18-debuginfoUpgrade kernel6.18-headersUpgrade kernel6.18-modules-extraUpgrade perf6.18-debuginfoUpgrade microvm-kernel6.18Upgrade kernel6.18-tools-develUpgrade kernel6.18-tools-debuginfoUpgrade python3-perf6.18-debuginfoUpgrade python3-perf6.18Upgrade kernel6.18-modules-extra-commonUpgrade perf6.18Upgrade kernel6.18-debuginfo-common-aarch64Upgrade bpftool6.18 | Sep 30, 2026 | Aug 28, 2026 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub