cve.bz

CVE-2023-32629 (GameOver(lay)) canonical ubuntu linux: Incorrect Authorization

7.8 highExploitEPSS 8.3%Fix available

Known as GameOver(lay)

High (7.8) in canonical ubuntu linux. EPSS 8.3% estimated probability of exploitation activity in the next 30 days.

On this page
Local privilege escalation vulnerability in Ubuntu Kernels overlayfs ovl_copy_up_meta_inode_data skip permission checks when calling ovl_do_setxattr on Ubuntu kernels

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
8.3% (unchanged from 8.3% a week ago; 9.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 95th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2024-10-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-32629 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-32629?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-32629?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-32629 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
canonical:ubuntu_linux23.04

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2023-32629
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2023-32629
Ubuntu20.04:LTSlinux5.4.0-155.172UBUNTU-CVE-2023-32629 USN-6251-1
Ubuntu20.04:LTSlinux-aws5.4.0-1106.114UBUNTU-CVE-2023-32629 USN-6251-1
Ubuntu20.04:LTSlinux-azure5.4.0-1112.118UBUNTU-CVE-2023-32629 USN-6251-1
Ubuntu20.04:LTSlinux-bluefield5.4.0-1068.74UBUNTU-CVE-2023-32629
Ubuntu20.04:LTSlinux-gcp5.4.0-1109.118UBUNTU-CVE-2023-32629 USN-6251-1
Ubuntu20.04:LTSlinux-gke5.4.0-1104.111UBUNTU-CVE-2023-32629 USN-6251-1
Ubuntu20.04:LTSlinux-gkeop5.4.0-1073.77UBUNTU-CVE-2023-32629 USN-6251-1
Ubuntu20.04:LTSlinux-ibm5.4.0-1053.58UBUNTU-CVE-2023-32629 USN-6251-1
Ubuntu20.04:LTSlinux-iot5.4.0-1018.19UBUNTU-CVE-2023-32629 USN-6261-1
Ubuntu20.04:LTSlinux-kvm5.4.0-1095.101UBUNTU-CVE-2023-32629 USN-6251-1
81 more for Ubuntu in the JSON and on Ubuntu's page.

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Important.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 6kernelNot affected
Red Hat Enterprise Linux 7kernelNot affected
Red Hat Enterprise Linux 7kernel-rtNot affected
Red Hat Enterprise Linux 8kernelNot affected
Red Hat Enterprise Linux 8kernel-rtNot affected
Red Hat Enterprise Linux 9kernelNot affected
Red Hat Enterprise Linux 9kernel-rtNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2023-32629.

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

References

Check your stackJSON