# CVE-2022-48340: Use after free in n/a

> A use-after-free vulnerability in GlusterFS allows attackers to potentially execute arbitrary code or cause a denial of service.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Feb 2023
- **Updated:** 14 Mar 2025
- **Also known as:** CLSA-2026-1781080101, CLSA-2026-1781177494, CLSA-2026-1782151075, CLSA-2026-1782151296, DEBIAN-CVE-2022-48340, GHSA-wqf4-gccr-fcx6, OESA-2024-1265, OESA-2024-1266, OESA-2024-1267, OESA-2024-1268, OESA-2024-1269, UBUNTU-CVE-2022-48340, USN-6507-1

## What is CVE-2022-48340?

CVE-2022-48340 is a high-severity use after free vulnerability in n/a, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Gluster GlusterFS 11.0, there is an xlators/cluster/dht/src/dht-common.c dht_setxattr_mds_cbk use-after-free.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2022-48340?

It affects 1 product.


Products: Gluster Glusterfs.

## How do I fix CVE-2022-48340?

Apply the vendor's patch.

## Is CVE-2022-48340 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-1112](https://insights.sbomify.com/CVE-2018-1112/): Auth bypass in glusterfs (high 8.0)
- [CVE-2023-26253](https://insights.sbomify.com/CVE-2023-26253/): Memory corruption in n/a (high 7.5)
- [CVE-2018-10924](https://insights.sbomify.com/CVE-2018-10924/): Denial of service in glusterfs (medium 5.3)
- [CVE-2014-3619](https://insights.sbomify.com/CVE-2014-3619/): Denial of service in n/a (medium 5.0)
- [CVE-2012-4417](https://insights.sbomify.com/CVE-2012-4417/): Path traversal in n/a (low 3.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48340 and fix it if it is affected.

What it is: CVE-2022-48340 is a high-severity use after free vulnerability in n/a, published on 21 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-48340 exists.

Affected product: n/a. 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-2022-48340/ (Markdown: https://insights.sbomify.com/CVE-2022-48340/index.md)
```

## Sources

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

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