# CVE-2023-32629: Privilege escalation in Ubuntu Kernel

> Local attackers can escalate privileges in Ubuntu kernels due to missing permission checks in overlayfs metadata copying.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jul 2023
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-5xvw-32xh-2vr5

## What is CVE-2023-32629?

CVE-2023-32629 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 26 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-32629?

It affects 1 product.


Products: Canonical Ubuntu Linux.

## How do I fix CVE-2023-32629?

Apply the vendor's patch.

## Is CVE-2023-32629 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32629 exists.

Public exploit code:

- Ubuntu Privilege Escalation bash one-liner using CVE-2023-32629 & CVE-2023-2640 (github_poc): https://github.com/ThrynSec/CVE-2023-32629-CVE-2023-2640---POC-Escalation
- Check for CVE-2023-32629 "GameOver(lay)" vulnerability  (github_poc): https://github.com/kaotickj/Check-for-CVE-2023-32629-GameOver-lay
- One-Liner CVE-2023-32629/CVE-2023-2640 Ubuntu Privilege Escalation (github_poc): https://github.com/k4but0/Ubuntu-LPE
- CVE-2023-32629 & CVE-2023-2640  Ubuntu Privilege Escalation POC (github_poc): https://github.com/xS9NTX/CVE-2023-32629-CVE-2023-2640-Ubuntu-Privilege-Escalation-POC
- GameOver(lay) Privilege Escalation and Container Escape (metasploit)
- OverlayFS Local Privilege Escalation - Full write-up to full escalation (github_poc): https://github.com/h3raklez/CVE-2023-32629

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32629 and fix it if it is affected.

What it is: CVE-2023-32629 is a high-severity vulnerability in Canonical Ubuntu Linux, published on 26 Jul 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-32629 exists.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-32629/ (Markdown: https://insights.sbomify.com/CVE-2023-32629/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-32629
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-32629
- OSV: https://osv.dev/vulnerability/CVE-2023-32629

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-32629/
Summaries are generated and may contain mistakes; the official description above is the record.