Vulnerability in Kernel: net: phy: micrel: Allow probing without .driver_data
Summary
GSD-2022-1003880: net: phy: micrel: Allow probing without .driver_data. Affects Kernel versions < 91e720b32cba25fa58eaa4c88fe957009cffe9f3. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Kernel is a critical component of the Linux operating system that manages communication between hardware and software. It provides essential functions and services to ensure the proper functioning of the system. The net: phy: micrel module in the Kernel is responsible for handling network physical layer devices manufactured by Micrel. These devices include Ethernet PHYs (Physical Layer Transceivers) used for network connectivity. The vulnerability in this module allows probing without .driver_data, potentially leading to security issues.
Vulnerability Detail
The vulnerability in the net: phy: micrel module allows probing without .driver_data, which can have security implications. The .driver_data field is used to store driver-specific data associated with the PHY device. By allowing probing without this field, it may be possible for an attacker to exploit the uninitialized state of the device and perform unauthorized actions or gain elevated privileges. 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 vulnerability in the net: phy: micrel module of the Kernel allows probing without .driver_data, potentially leading to security issues. It is recommended to update the Linux Kernel to the fixed version to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it has the potential to allow unauthorized actions or privilege escalation.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. It analyzes the manifest file like package-lock.json to identify vulnerabilities in the software.
There is no known exploit for this vulnerability at the moment.
The recommended mitigation is to update the Linux Kernel to the fixed version mentioned in the 'how_to_fix' section.
You can find more information about this vulnerability in the Open Source Vulnerability Database. The specific vulnerability ID is GSD-2022-1003880.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
