Vulnerability in Kernel Package: dax: make sure inodes are flushed before destroy cache

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1002093: dax: make sure inodes are flushed before destroy cache. Affects Kernel versions >= 7b6be8444e0f0dd675b54d059793423d3c9b4c03, < ec376f5c11c88c0215d173599db8449cd4196759. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Kernel package is a critical component of the Linux operating system, responsible for managing the system's core functionality. It provides an interface between the hardware and software layers, allowing applications to communicate with the underlying system resources. The dax subsystem within the Kernel package enables direct access to persistent memory devices, improving performance for certain workloads. However, a vulnerability has been identified in the dax subsystem that could potentially lead to security issues.

Vulnerability Detail

The vulnerability in the dax subsystem of the Kernel package arises when inodes are not properly flushed before destroying the cache. This flaw could be exploited by an attacker to manipulate or access sensitive data, potentially leading to unauthorized information disclosure or privilege escalation. The vulnerability was introduced in version v4.12 of the Linux Kernel and has been fixed in version v5.10.110.

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

If updating the Linux Kernel package is not immediately feasible, a possible workaround is to manually flush the inodes before destroying the cache. This can be achieved by modifying the relevant code section responsible for cache destruction to include a call to the inode flushing function. Here is an example of how the code modification can be done:

// Code snippet demonstrating the workaround
void destroy_cache() {
  // Flush inodes before destroying cache
  flush_inodes();

  // Code to destroy cache
  ...
}

Conclusion

In conclusion, a vulnerability has been identified in the dax subsystem of the Kernel package, which could allow unauthorized access or manipulation of sensitive data. It is crucial to update the Linux Kernel package to version v5.10.110 or later to mitigate this vulnerability. If immediate updating is not possible, applying the provided workaround can help mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability could potentially allow an attacker to manipulate or access sensitive data, leading to unauthorized information disclosure or privilege escalation.

You can use Vulert's 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 to identify any open-source vulnerabilities, including this one.

Yes, this vulnerability has been fixed in version v5.10.110 of the Linux Kernel package.

At the time of this report, there are no known exploits for this vulnerability. However, it is important to apply the necessary updates and security patches to mitigate any potential risks.

If updating the Linux Kernel package is not immediately feasible, you can apply the provided workaround by manually flushing the inodes before destroying the cache. However, it is strongly recommended to update to the latest version as soon as possible to ensure comprehensive security.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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 →

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