jfs: Prevent NULL dereference in diFree
Summary
GSD-2022-1001695: jfs: prevent NULL deref in diFree. Affects Kernel versions < d925b7e78b62805fcc5440d1521181c82b6f03cb. 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
Background
The jfs package is a component of the Linux Kernel, which is responsible for providing support for the Journaled File System (JFS). JFS is a high-performance file system designed for use on modern, high-end servers. It offers advanced features such as journaling, which ensures file system consistency in the event of a system crash or power failure. 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, potentially leading to a system crash or privilege escalation. By exploiting this vulnerability, an attacker could cause a denial of service (DoS) condition or execute arbitrary code with elevated privileges. The vulnerability is fixed in Linux Kernel version v5.15.34 by commit d925b7e78b62805fcc5440d1521181c82b6f03cb.
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 as soon as possible.
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 privilege escalation. It is recommended to update the Linux Kernel to version v5.15.34 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a system crash or privilege escalation, potentially allowing an attacker to execute arbitrary code with elevated 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 Vulert will analyze it for any known vulnerabilities.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
No, this vulnerability requires local access to the system in order to exploit it.
The only effective mitigation for this vulnerability is to apply the provided fix by updating the Linux Kernel to version v5.15.34 or later.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
