# CVE-2024-56600: net: inet6: do not leave a dangling sk pointer in inet6_create()

> A use-after-free vulnerability in the Linux kernel's inet6_create function allows attackers to potentially execute code or escalate privileges.

- **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:** 27 Dec 2024
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-55491, AZL-55576, BELL-CVE-2024-56600, DEBIAN-CVE-2024-56600, GHSA-qc69-73cr-g9fg, SUSE-SU-2025:1214-1, SUSE-SU-2025:1238-1, SUSE-SU-2025:1276-1, UBUNTU-CVE-2024-56600

## What is CVE-2024-56600?

CVE-2024-56600 is a high-severity use after free vulnerability in Linux kernel, published on 27 Dec 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

net: inet6: do not leave a dangling sk pointer in inet6_create()

sock_init_data() attaches the allocated sk pointer to the provided sock
object. If inet6_create() fails later, the sk object is released, but the
sock object retains the dangling sk pointer, which may cause use-after-free
later.

Clear the sock sk pointer on error.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2024-56600?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel-livepatch-SLE15-SP4_Update_29` | SUSE:Linux Enterprise Live Patching 15 SP4 | All versions | 8-150400.2.1 |
| `kernel-livepatch-SLE15-SP4_Update_31` | SUSE:Linux Enterprise Live Patching 15 SP4 | All versions | 6-150400.2.1 |
| `kernel-livepatch-SLE15-SP5_Update_17` | SUSE:Linux Enterprise Live Patching 15 SP5 | All versions | 8-150500.2.1 |
| `kernel-livepatch-SLE15-SP5_Update_19` | SUSE:Linux Enterprise Live Patching 15 SP5 | All versions | 6-150500.2.1 |
| `kernel-livepatch-SLE15-SP6-RT_Update_1` | SUSE:Linux Enterprise Live Patching 15 SP6 | All versions | 12-150600.2.1 |
| `kernel-livepatch-SLE15-SP6_Update_6` | SUSE:Linux Enterprise Live Patching 15 SP6 | All versions | 4-150600.2.1 |

Products: Linux kernel.

## How do I fix CVE-2024-56600?

Apply the vendor's patch.

## Is CVE-2024-56600 being exploited?

There is no known exploitation of CVE-2024-56600 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-2024-56600 and fix it if it is affected.

What it is: CVE-2024-56600 is a high-severity use after free vulnerability in Linux kernel, published on 27 Dec 2024. 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-2024-56600 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-2024-56600/ (Markdown: https://insights.sbomify.com/CVE-2024-56600/index.md)
```

## Sources

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

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