A flaw was found in the ptp4l program of the linuxptp package.
Noroxi assessment
Priority: Monitor (action score 29/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 79.2% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: linuxptp (AlmaLinux:8) 3.1.1-1.el8; linuxptp (Debian:12) 3.1-2.1; linuxptp (Red Hat:enterprise_linux:8::appstream) 0:3.1.1-1.el8.
Low priority for now. Upgrade to linuxptp (AlmaLinux:8) 3.1.1-1.el8; linuxptp (Debian:12) 3.1-2.1; linuxptp (Red Hat:enterprise_linux:8::appstream) 0:3.1.1-1.el8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A flaw was found in the ptp4l program of the linuxptp package. When ptp4l is operating on a little-endian architecture as a PTP transparent clock, a remote attacker could send a crafted one-step sync message to cause an information leak or crash. The highest threat from this vulnerability is to data confidentiality and system availability. This flaw affects linuxptp versions before 3.1.1 and before 2.0.1.
- Published
- Jul 9, 2021
- Updated
- Jun 17, 2026
- EPSS
- 1.9% · 79th percentile
- CWE
- CWE-119
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linuxptp project | linuxptp | cpe:2.3:a:linuxptp_project:linuxptp |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- fedoraproject fedora33
- fedoraproject fedora34
- linuxptp project linuxptpbefore 2.0.1
- linuxptp project linuxptp3.0 and later · before 3.1.1
- redhat enterprise linux8.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
n/a linuxptp
- linuxptp 3.1.1, linuxptp 2.0.1affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | linuxptp | before 3.1.1-1.el8 | 3.1.1-1.el8 |
| Debian:12 | linuxptp | before 3.1-2.1 | 3.1-2.1 |
| Red Hat:enterprise_linux:8::appstream | linuxptp | before 0:3.1.1-1.el8 | 0:3.1.1-1.el8 |
| Red Hat:enterprise_linux:8::appstream | linuxptp-debuginfo | before 0:3.1.1-1.el8 | 0:3.1.1-1.el8 |
| Red Hat:enterprise_linux:8::appstream | linuxptp-debugsource | before 0:3.1.1-1.el8 | 0:3.1.1-1.el8 |
| Rocky Linux:8 | linuxptp | before 0:3.1.1-1.el8 | 0:3.1.1-1.el8 |
Same product
linuxptp project: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-3570A flaw was found in the ptp4l program of the linuxptp package.36Monitor
- CVE-2024-42861An 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 30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:linuxptp | 3.1.1-1.el8 · AlmaLinux:8 | Package registry (OSV) |
| debian:linuxptp | 3.1-2.1 · Debian:12 | Package registry (OSV) |
| red hat:linuxptp | 0:3.1.1-1.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:linuxptp-debuginfo | 0:3.1.1-1.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| red hat:linuxptp-debugsource | 0:3.1.1-1.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| rocky linux:linuxptp | 0:3.1.1-1.el8 · Rocky Linux:8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.