Memory Leak Vulnerability in ptp

Kernel Updated 02 Oct 2025

Summary

28/10/2021
N/A
No i
Unrated
Not published

GSD-2021-1001888: ptp: Fix possible memory leak in ptp_clock_register(). Affects Kernel versions >= a33121e5487b424339636b25c35d3a180eaa5f5e, < 95c0a0c5ec8839f8f21672be786e87a100319ca8. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The ptp package is a part of the Linux Kernel ecosystem and is responsible for handling Precision Time Protocol (PTP) clocks. PTP is a protocol used for synchronizing clocks in a network. The ptp_clock_register() function is used to register a PTP clock with the system. However, a memory leak vulnerability has been discovered in this function.

Vulnerability Detail

The vulnerability in ptp_clock_register() can lead to a memory leak. When a PTP clock is registered, memory is allocated for the clock structure. If the registration fails, this memory is not properly freed, resulting in a memory leak. An attacker could potentially trigger this vulnerability by repeatedly registering PTP clocks, causing the system to run out of memory. The impact of this vulnerability could include system instability, resource exhaustion, and denial of service.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability.

Conclusion

In conclusion, the ptp package in the Linux Kernel is vulnerable to a memory leak issue in the ptp_clock_register() function. This vulnerability can lead to system instability, resource exhaustion, and denial of service. It is recommended to update to Linux Kernel version v5.14.15 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

ptp_clock_register() is a function in the ptp package that is used to register a Precision Time Protocol (PTP) clock with the system.

A memory leak occurs when memory that is allocated dynamically is not properly freed, resulting in a loss of available memory.

The potential consequences of this vulnerability include system instability, resource exhaustion, and denial of service.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground and it will alert you if the vulnerability is present.

Yes, the vulnerability is fixed in Linux Kernel version v5.14.15. Updating to this version or later will resolve the memory leak issue in ptp_clock_register().

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback