# CVE-2024-42861: Denial of service in n/a

> A remote attacker can cause a denial of service in the linuxptp time synchronization function by sending a crafted Pdelay_Req message.

- **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:** 23 Sep 2024
- **Updated:** 18 Mar 2025
- **Also known as:** AZL-49731, AZL-49740, DEBIAN-CVE-2024-42861, GHSA-xgfh-jv6x-46xv, UBUNTU-CVE-2024-42861

## What is CVE-2024-42861?

CVE-2024-42861 is a high-severity denial of service vulnerability in n/a, published on 23 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in IEEE 802.1AS linuxptp v.4.2 and before allowing a remote attacker to cause a denial of service via a crafted Pdelay_Req message to the time synchronization function

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

It affects 1 product.


Products: Linuxptp Project Linuxptp.

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

Upgrade to a fixed version.

## Is CVE-2024-42861 being exploited?

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

Public exploit code:

- the (github_poc): https://github.com/qiupy123/CVE-2024-42861

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42861 and fix it if it is affected.

What it is: CVE-2024-42861 is a high-severity denial of service vulnerability in n/a, published on 23 Sep 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-42861 in the wild and no public exploit code.

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-2024-42861/ (Markdown: https://insights.sbomify.com/CVE-2024-42861/index.md)
```

## Sources

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

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