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-1002802: phonet/pep: refuse to enable an unbound pipe. Affects Kernel versions < 48c76fc53582e7f13c1e0b11c916e503256c4d0b. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The phonet/pep package is a component of the Linux Kernel, which is responsible for handling the Phonet protocol and its associated protocols. Phonet is a network protocol used for communication between devices in embedded systems. The phonet/pep package provides the necessary functionality to enable and manage Phonet pipes, which are used for data transfer between devices. However, a vulnerability has been discovered in the package that allows the enabling of an unbound pipe.

Vulnerability Detail

The vulnerability in the phonet/pep package allows the enabling of an unbound pipe. An unbound pipe refers to a pipe that has not been properly initialized or associated with any specific device or endpoint. By enabling an unbound pipe, an attacker could potentially exploit this vulnerability to perform unauthorized data transfer or disrupt the normal operation of the system. The impact and attack plausibility of this vulnerability have not yet been proven. The vulnerability has been fixed in Linux Kernel version v5.4.169 by commit 48c76fc53582e7f13c1e0b11c916e503256c4d0b.

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 vulnerability in the phonet/pep package that allowed the enabling of an unbound pipe has been fixed in Linux Kernel version v5.4.169. It is recommended to update the Kernel to the fixed version to mitigate the risk of exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The phonet/pep package is a component of the Linux Kernel that handles the Phonet protocol and its associated protocols. It provides functionality for enabling and managing Phonet pipes.

A Phonet pipe is a communication channel used for data transfer between devices in embedded systems.

An unbound pipe refers to a pipe that has not been properly initialized or associated with any specific device or endpoint.

Enabling an unbound pipe can potentially allow unauthorized data transfer or disrupt the normal operation of the system.

Yes, the vulnerability has been fixed in Linux Kernel version v5.4.169 by commit 48c76fc53582e7f13c1e0b11c916e503256c4d0b.

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