# CVE-2023-52340: Denial of service in n/a

> An attacker can cause a denial of service by exhausting IPv6 route cache entries via raw sockets, affecting Linux kernel systems.

- **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:** 5 Jul 2024
- **Updated:** 4 Nov 2025
- **Also known as:** AZL-43279, BELL-CVE-2023-52340, DEBIAN-CVE-2023-52340, GHSA-7q4j-f74f-6h5j, SUSE-SU-2024:1207-1, SUSE-SU-2024:1273-1, SUSE-SU-2024:1278-1, SUSE-SU-2024:1280-1, UBUNTU-CVE-2023-52340

## What is CVE-2023-52340?

CVE-2023-52340 is a high-severity denial of service vulnerability in Linux kernel, published on 5 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The IPv6 implementation in the Linux kernel before 6.3 has a net/ipv6/route.c max_size threshold that can be consumed easily, e.g., leading to a denial of service (network is unreachable errors) when IPv6 packets are sent in a loop via a raw socket.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kgraft-patch-SLE12-SP5_Update_53` | SUSE:Linux Enterprise Live Patching 12 SP5 | All versions | 3-2.1 |
| `kernel-livepatch-SLE15-SP2_Update_45` | SUSE:Linux Enterprise Live Patching 15 SP2 | All versions | 4-150200.2.1 |
| `kernel-livepatch-SLE15-SP3_Update_41` | SUSE:Linux Enterprise Live Patching 15 SP3 | All versions | 4-150300.2.1 |
| `kernel-livepatch-SLE15-SP4_Update_23` | SUSE:Linux Enterprise Live Patching 15 SP4 | All versions | 2-150400.9.8.1 |
| `kernel-livepatch-SLE15-SP5-RT_Update_10` | SUSE:Linux Enterprise Live Patching 15 SP5 | All versions | 2-150500.11.8.1 |
| `kernel-livepatch-SLE15-SP5_Update_10` | SUSE:Linux Enterprise Live Patching 15 SP5 | All versions | 2-150500.11.8.1 |

Products: Linux kernel.

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

Upgrade to a fixed version.

## Is CVE-2023-52340 being exploited?

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

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-52340 is a high-severity denial of service vulnerability in Linux kernel, published on 5 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-52340 in the wild and no public exploit code.

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

## Sources

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

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