Use-after-free vulnerability in phylib package

Kernel Updated 02 Oct 2025

Summary

27/02/2022
N/A
No i
Unrated
Not published

GSD-2022-1000627: phylib: fix potential use-after-free. Affects Kernel versions >= bafbdd527d569c8200521f2f7579f65a044271be, < cb2fab10fc5e7a3aa1bb0a68a3abdcf3e37852af. 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 phylib package is a component of the Linux Kernel, which provides a framework for managing physical layer devices. It is responsible for handling the low-level interactions with network PHYs (Physical Layer Transceivers) and managing their state. PHYs are used in various networking devices, such as Ethernet adapters and switches, to establish and maintain network connections. The phylib package is an essential part of the Linux Kernel and is widely used in networking systems.

Vulnerability Detail

The identified vulnerability in the phylib package is a use-after-free issue. This type of vulnerability occurs when a program continues to use a pointer to an object after the object has been freed from memory. In the context of phylib, this vulnerability could be exploited by an attacker to manipulate the state of a PHY device after it has been freed, potentially leading to a variety of security issues. The use-after-free vulnerability was introduced in version 4.16 of the Linux Kernel and has been fixed in version 5.16.5.

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

As a workaround, users can apply the patch manually to the affected version of the Linux Kernel. The patch can be obtained from the commit cb2fab10fc5e7a3aa1bb0a68a3abdcf3e37852af in the Linux Kernel repository. However, it is strongly advised to update to the latest stable version of the Linux Kernel to ensure comprehensive security fixes.

Conclusion

The use-after-free vulnerability in the phylib package of the Linux Kernel can be addressed by updating to version 5.16.5 or later. It is crucial to keep the Linux Kernel up to date to ensure the latest security patches and protect against potential exploits. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

phylib is a package in the Linux Kernel that provides a framework for managing physical layer devices, such as network PHYs.

A use-after-free vulnerability occurs when a program continues to use a pointer to an object after the object has been freed from memory.

The use-after-free vulnerability in phylib could be exploited by an attacker to manipulate the state of a PHY device, potentially leading to security issues such as unauthorized access or denial of service.

The vulnerability was introduced in version 4.16 of the Linux Kernel and has been fixed in version 5.16.5.

To fix this vulnerability, it is recommended to update the Linux Kernel to version 5.16.5 or later.

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