Refusal to Enable an Unbound Pipe in phonet/pep

Kernel Updated 02 Oct 2025

Summary

30/12/2021
N/A
No i
Unrated
Not published

GSD-2021-1002775: phonet/pep: refuse to enable an unbound pipe. Affects Kernel versions < 0bbdd62ce9d44f3a22059b3d20a0df977d9f6d59. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The phonet/pep package is a component of the Linux Kernel ecosystem. It provides functionality related to the Phone Networking Subsystem (Phonet) and the Protocol for Exchanging Parameters (PEP). Phonet is a protocol used for communication between devices in a phone network, while PEP is a protocol used for exchanging parameters between devices. This vulnerability affects the phonet/pep package in the Linux Kernel.

Vulnerability Detail

The vulnerability in phonet/pep involves the enabling of an unbound pipe. An unbound pipe is a pipe that has not been properly initialized or configured. By refusing to enable an unbound pipe, this vulnerability prevents potential security risks and ensures the proper functioning of the phonet/pep package. The impact and attack plausibility of this vulnerability have not been proven yet.

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

The refusal to enable an unbound pipe vulnerability in the phonet/pep package of the Linux Kernel has been identified and fixed in version v4.4.297. It is recommended to update the Linux Kernel to the latest version to ensure the security and stability of the system. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The phonet/pep package is a component of the Linux Kernel ecosystem that provides functionality related to the Phone Networking Subsystem (Phonet) and the Protocol for Exchanging Parameters (PEP).

An unbound pipe is a pipe that has not been properly initialized or configured. In the context of this vulnerability, refusing to enable an unbound pipe prevents potential security risks and ensures the proper functioning of the phonet/pep package.

The impact of this vulnerability is currently unknown as the actual attack plausibility has not been proven. However, by fixing this vulnerability, the phonet/pep package ensures the security and stability of the Linux Kernel.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v4.4.297 or later. This fix is implemented in commit 0bbdd62ce9d44f3a22059b3d20a0df977d9f6d59 of the Linux Kernel repository.

For more details about this vulnerability, you can refer to the source link provided in the database specific information of the vulnerability.

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