jfs: NULL dereference in diFree

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1002399: jfs: prevent NULL deref in diFree. Affects Kernel versions < 33bd243566a9b1ca94261dcc2e16c7b9e3a71c15. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The jfs package is a component of the Linux Kernel, which is responsible for managing the JFS file system. JFS is a high-performance file system designed for use with large storage devices. It provides features such as journaling and support for large files and directories. However, a vulnerability has been discovered in the diFree function of the jfs package, which could 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 other unexpected behavior. This vulnerability could be exploited by an attacker with local access to the system. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability has been fixed in the Linux Kernel version v4.14.276 by commit 33bd243566a9b1ca94261dcc2e16c7b9e3a71c15.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v4.14.276 or later. This can be done by downloading the latest version of the Linux Kernel source code from the official repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it according to the provided instructions.

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 jfs package in the Linux Kernel is vulnerable to a NULL dereference in the diFree function. This vulnerability can potentially lead to system crashes or other unexpected behavior. It is recommended to update the Linux Kernel to version v4.14.276 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The jfs package is a component of the Linux Kernel that manages the JFS file system, providing high-performance features for large storage devices.

A NULL dereference occurs when a program attempts to access or manipulate memory using a NULL pointer, leading to a crash or unexpected behavior.

An attacker with local access to the system could exploit this vulnerability by triggering a NULL dereference in the diFree function of the jfs package, potentially causing a system crash or other unexpected behavior.

The impact and attack plausibility of this vulnerability have not been proven yet. Further analysis is required to determine the potential consequences.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v4.14.276 or later. Instructions for updating the Linux Kernel can be found in the official documentation.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v4.14.276 or later. This can be done by downloading the latest version of the Linux Kernel source code from the official repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it according to the provided instructions.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.