jfs: Prevent NULL deref in diFree
Summary
GSD-2022-1002470: jfs: prevent NULL deref in diFree. Affects Kernel versions < d2e45f0bc25da09efcac658d6e405115fcfa83c2. 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 file system driver for the Linux Kernel. It provides support for the Journaled File System (JFS), which is a high-performance file system designed for use on modern, high-end servers. The diFree function in jfs is responsible for freeing a directory index (di) structure. However, a vulnerability exists in this function that can lead to a NULL dereference.
Vulnerability Detail
The vulnerability in jfs's diFree function allows an attacker to trigger a NULL pointer dereference, which can result in a system crash or potentially allow the attacker to execute arbitrary code with kernel privileges. The vulnerability was discovered in the Linux Kernel version v4.9.311 and has been fixed in commit d2e45f0bc25da09efcac658d6e405115fcfa83c2.
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 above.
Conclusion
The jfs package in the Linux Kernel is vulnerable to a NULL dereference issue in the diFree function. This vulnerability can lead to a system crash or potential code execution with kernel privileges. Users are advised to update their Linux Kernel to version v4.9.311 or later to mitigate 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 allow an attacker to execute arbitrary code with kernel privileges.
This vulnerability was discovered through code analysis and testing.
There is no known exploit for this vulnerability at the moment.
No, only versions up to v4.9.311 are affected. The vulnerability has been fixed in later versions.
Yes, it is recommended to restart the system after updating the Linux Kernel to ensure the fix is applied correctly.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.