Vulnerability in Kernel: zonefs_iomap_begin() for reads

Kernel Updated 02 Oct 2025

Summary

31/07/2022

Disclosed on

N/A

Severity

No i

Fix available

Unrated

Severity

Not published

CVSS Score

GSD-2022-1004285: zonefs: fix zonefs_iomap_begin() for reads. Affects Kernel versions >= 8dcc1a9d90c10fa4143e5c17821082e5e60e46a1, < 3a7f05f104347b407e865c10be2675cd833a4e48. 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 Browse

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.

Background

The Kernel is a critical component of the Linux operating system that provides core functionality and interfaces with hardware devices. It manages system resources, facilitates communication between software and hardware, and ensures the stability and security of the system. One of the components within the Kernel is zonefs, which is responsible for managing zones on zoned block devices. Zones are logical divisions of storage devices that allow for efficient data management. However, a vulnerability has been identified in the zonefs_iomap_begin() function when used for reads.

Vulnerability Detail

The zonefs_iomap_begin() function in the Kernel's zonefs component has a security flaw that can be exploited during read operations. The vulnerability was introduced in version v5.6 of the Linux Kernel and was fixed in version v5.18.7. The exact impact and attack plausibility of this vulnerability have not been proven yet. However, if exploited, it could potentially lead to unauthorized access, information disclosure, or other security breaches. The vulnerability has been assigned the ID GSD-2022-1004285.

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 v5.18.7 or later. This update includes the necessary patch to address the security flaw in the zonefs_iomap_begin() function. Users can obtain the updated Kernel from the official Linux Kernel repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

No workaround has been provided for this vulnerability. It is essential to update to the fixed version of the Linux Kernel to ensure the security of the system.

Conclusion

The vulnerability in the Kernel's zonefs component, identified as GSD-2022-1004285, affects the zonefs_iomap_begin() function used for reads. It is crucial to update the Linux Kernel to version v5.18.7 or later to mitigate the risk of unauthorized access, information disclosure, or other security breaches. No workaround has been provided, and it is recommended to apply the patch provided in the updated Kernel. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

FAQ

What is the impact of this vulnerability?

The exact impact of this vulnerability is yet to be determined. However, if exploited, it could potentially lead to unauthorized access, information disclosure, or other security breaches.

How can I check if my system is affected by this vulnerability?

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. It analyzes the manifest file, such as package-lock.json, and provides real-time alerts for open-source vulnerabilities in the software.

You can find more information about this vulnerability in the GSD-2022-1004285 entry of the GSD Database maintained by the Cloud Security Alliance. The source can be accessed on GitHub: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1004xxx/GSD-2022-1004285.json