# CVE-2023-4622: Use-after-free in Linux kernel's af_unix component

> A use-after-free in the Linux kernel's af_unix component allows local attackers to escalate privileges due to a race condition.

- **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:** 6 Sep 2023
- **Updated:** 17 Sep 2026
- **Also known as:** A-299123598, ASB-A-299123598, AZL-28679, AZL-31642, DEBIAN-CVE-2023-4622, GHSA-hxpr-87wq-jwf8, SUSE-SU-2023:4795-1, SUSE-SU-2023:4799-1, SUSE-SU-2023:4831-1, SUSE-SU-2023:4847-1, UBUNTU-CVE-2023-4622

## What is CVE-2023-4622?

CVE-2023-4622 is a high-severity use after free vulnerability in Debian Debian Linux, published on 6 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A use-after-free vulnerability in the Linux kernel's af_unix component can be exploited to achieve local privilege escalation.

The unix_stream_sendpage() function tries to add data to the last skb in the peer's recv queue without locking the queue. Thus there is a race where unix_stream_sendpage() could access an skb locklessly that is being released by garbage collection, resulting in use-after-free.

We recommend upgrading past commit 790c2f9d15b594350ae9bca7b236f2b1859de02c (or backported equivalents).

Weakness: CWE-416 (Use After Free)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kgraft-patch-SLE12-SP5_Update_39` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 10-2.2 |
| `kgraft-patch-SLE12-SP5_Update_42` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 8-2.1 |
| `kgraft-patch-SLE12-SP5_Update_47` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 4-2.1 |
| `kernel-livepatch-SLE15-SP1_Update_36` | SUSE:Linux Enterprise Live Patching 15 SP1 | All versions | 11-150100.2.2 |
| `kernel-livepatch-SLE15-SP1_Update_38` | SUSE:Linux Enterprise Live Patching 15 SP1 | All versions | 8-150100.2.1 |

Products: Debian Debian Linux, Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2023-4622 being exploited?

There is no known exploitation of CVE-2023-4622 in the wild and no public exploit code.

Public exploit code:

- https://github.com/android-cve-exploits/0range1337--CVE-CVE-2023-4622 (github_poc): https://github.com/android-cve-exploits/0range1337--CVE-CVE-2023-4622

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-4622 is a high-severity use after free vulnerability in Debian Debian Linux, published on 6 Sep 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-4622 in the wild and no public exploit code.

Affected product: Debian Debian 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-4622/ (Markdown: https://insights.sbomify.com/CVE-2023-4622/index.md)
```

## Sources

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

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