jfs: Prevent NULL dereference in diFree
Summary
GSD-2022-1001024: jfs: prevent NULL deref in diFree. Affects Kernel versions < 2e0e1de4f7a17e0886524c1d6701b8e2bf5a7363. 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 jfs package is a component of the Linux Kernel, which is responsible for managing the JFS file system. JFS (Journaled File System) is a high-performance file system designed for use on IBM AIX operating systems. It provides features such as journaling, which ensures the integrity of file system metadata and data. The diFree function in the jfs package is responsible for freeing disk inode structures. However, a vulnerability exists in this function that can lead to a NULL dereference.
Vulnerability Detail
The vulnerability in the diFree function of the jfs package allows an attacker to trigger a NULL dereference, which can result in a system crash or potential code execution. By exploiting this vulnerability, an attacker may be able to cause a denial-of-service (DoS) condition or execute arbitrary code with kernel privileges. The vulnerability has been fixed in Linux Kernel version v5.17.3 by commit 2e0e1de4f7a17e0886524c1d6701b8e2bf5a7363.
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 known workaround for this vulnerability. It is recommended to apply the fix mentioned in the 'how_to_fix' section.
Conclusion
The jfs package in the Linux Kernel is vulnerable to a NULL dereference in the diFree function. This vulnerability can lead to a system crash or potential code execution. It is recommended to update the Linux Kernel to version v5.17.3 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to a system crash or potential code execution, allowing an attacker to cause a denial-of-service (DoS) condition or execute arbitrary code with kernel privileges.
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 and the Vulert Playground will analyze it for any known vulnerabilities.
At the time of this report, there is no known public exploit for this vulnerability. However, it is always recommended to apply security patches as soon as they become available to mitigate the risk.
No, this vulnerability requires local access to the system in order to exploit it.
The only known mitigation for this vulnerability is to update the Linux Kernel to version v5.17.3 or later.
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.
