# CVE-2024-5564: Libndp: buffer overflow in route information length field > A local attacker can trigger a buffer overflow in NetworkManager via malformed IPv6 router advertisements, potentially causing denial of service or code execution. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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:** 31 May 2024 - **Updated:** 20 Nov 2025 - **Also known as:** ALSA-2024:4620, ALSA-2024:4636, AZL-42609, AZL-42625, CLSA-2024-1724259497, CLSA-2025-1745270484, CLSA-2025-1755617684, CLSA-2026-1791301513, DEBIAN-CVE-2024-5564, DLA-3837-1, DSA-5713-1, GHSA-rx7p-m6c3-777g, MGASA-2024-0225, OESA-2024-1723, RHBA-2025:6631, RHSA-2024:4618, RHSA-2024:4619, RHSA-2024:4620, RHSA-2024:4622, RHSA-2024:4636, RHSA-2024:4640, RHSA-2024:4641, RHSA-2024:4642, RHSA-2024:4643, RLSA-2024:4620, RLSA-2024:4636, SUSE-SU-2024:2283-1, SUSE-SU-2024:2541-1, SUSE-SU-2025:20088-1, UBUNTU-CVE-2024-5564, USN-6830-1, USN-7248-1, openSUSE-SU-2024:14112-1 ## What is CVE-2024-5564? CVE-2024-5564 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 31 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability was found in libndp. This flaw allows a local malicious user to cause a buffer overflow in NetworkManager, triggered by sending a malformed IPv6 router advertisement packet. This issue occurred as libndp was not correctly validating the route length information. Weakness: CWE-120 (Buffer Copy without Checking Size of Input) ## Which versions are affected by CVE-2024-5564? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libndp` | AlmaLinux:8 | All versions | 1.7-7.el8_10.alma.1 | | `libndp` | AlmaLinux:9 | All versions | 1.8-6.el9_4.alma.1 | | `libndp` | Red Hat:enterprise_linux:10.0 | All versions | 0:1.9-2.el10 | | `libndp-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:1.9-2.el10 | | `libndp-debugsource` | Red Hat:enterprise_linux:10.0 | All versions | 0:1.9-2.el10 | | `libndp` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.7-7.el8_10 | | `libndp-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.7-7.el8_10 | | `libndp-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.7-7.el8_10 | | `libndp` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.8-6.el9_4 | | `libndp-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.8-6.el9_4 | | `libndp-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:1.8-6.el9_4 | | `libndp` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:1.7-4.el8_2 | | `libndp-debuginfo` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:1.7-4.el8_2 | | `libndp-debugsource` | Red Hat:rhel_aus:8.2::baseos | All versions | 0:1.7-4.el8_2 | | `libndp` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:1.7-6.el8_4 | | `libndp-debuginfo` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:1.7-6.el8_4 | | `libndp-debugsource` | Red Hat:rhel_aus:8.4::baseos | All versions | 0:1.7-6.el8_4 | | `libndp` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:1.7-7.el8_6 | | `libndp-debuginfo` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:1.7-7.el8_6 | | `libndp-debugsource` | Red Hat:rhel_aus:8.6::baseos | All versions | 0:1.7-7.el8_6 | | `libndp` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:1.7-6.el8_4 | | `libndp-debuginfo` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:1.7-6.el8_4 | | `libndp-debugsource` | Red Hat:rhel_e4s:8.4::baseos | All versions | 0:1.7-6.el8_4 | | `libndp` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:1.7-7.el8_6 | | `libndp-debuginfo` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:1.7-7.el8_6 | | `libndp-debugsource` | Red Hat:rhel_e4s:8.6::baseos | All versions | 0:1.7-7.el8_6 | | `libndp` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:1.8-5.el9_0 | | `libndp-debuginfo` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:1.8-5.el9_0 | | `libndp-debugsource` | Red Hat:rhel_e4s:9.0::baseos | All versions | 0:1.8-5.el9_0 | | `libndp` | Red Hat:rhel_els:7 | All versions | 0:1.2-10.el7_9 | | `libndp-debuginfo` | Red Hat:rhel_els:7 | All versions | 0:1.2-10.el7_9 | | `libndp-devel` | Red Hat:rhel_els:7 | All versions | 0:1.2-10.el7_9 | | `libndp` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:1.7-7.el8_8 | | `libndp-debuginfo` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:1.7-7.el8_8 | | `libndp-debugsource` | Red Hat:rhel_eus:8.8::baseos | All versions | 0:1.7-7.el8_8 | | `libndp` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1.8-5.el9_2 | | `libndp-debuginfo` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1.8-5.el9_2 | | `libndp-debugsource` | Red Hat:rhel_eus:9.2::baseos | All versions | 0:1.8-5.el9_2 | | `libndp` | Red Hat:rhel_tus:8.4::baseos | All versions | 0:1.7-6.el8_4 | | `libndp-debuginfo` | Red Hat:rhel_tus:8.4::baseos | All versions | 0:1.7-6.el8_4 | ## How do I fix CVE-2024-5564? Apply the vendor's patch. ## Is CVE-2024-5564 being exploited? There is no known exploitation of CVE-2024-5564 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-5564 and fix it if it is affected. What it is: CVE-2024-5564 is a high-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 31 May 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-2024-5564 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. 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-5564/ (Markdown: https://insights.sbomify.com/CVE-2024-5564/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-5564 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-5564 - OSV: https://osv.dev/vulnerability/CVE-2024-5564 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-5564/ Summaries are generated and may contain mistakes; the official description above is the record.