Null-Pointer Dereference Vulnerability in audit_filter_rules

Kernel Updated 02 Oct 2025

Summary

28/10/2021
N/A
No i
Unrated
Not published

GSD-2021-1001842: audit: fix possible null-pointer dereference in audit_filter_rules. Affects Kernel versions >= bf361231c295d92a28ca283ea713f56e93e55796, < 16802fa4c33eb1a8efb23f1e93365190e4047d05. 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 is a critical component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionalities such as process management, memory management, and device drivers. The audit subsystem within the Kernel is responsible for monitoring and logging system events for security and compliance purposes. The audit_filter_rules function is a crucial part of this subsystem, used to apply filtering rules to determine which events should be audited. However, a vulnerability has been discovered in this function that could lead to a null-pointer dereference.

Vulnerability Detail

The null-pointer dereference vulnerability in audit_filter_rules arises from a flaw introduced in version v5.3 of the Linux Kernel. This flaw allows an attacker to trigger a null-pointer dereference, potentially leading to a system crash or the execution of arbitrary code with kernel privileges. By exploiting this vulnerability, an attacker could gain unauthorized access to sensitive information, modify system configurations, or disrupt the normal operation of the system. The vulnerability was fixed in version v5.10.76 of the Linux 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 →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the provided fix by updating the Linux Kernel to a patched version.

Conclusion

The null-pointer dereference vulnerability in audit_filter_rules poses a significant risk to the security and stability of Linux systems. It is crucial to apply the provided fix by updating the Linux Kernel to a patched version. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

A null-pointer dereference occurs when a program attempts to access or manipulate memory using a null pointer, which does not point to a valid memory location. This can lead to crashes, unexpected behavior, or security vulnerabilities.

By crafting a malicious input or triggering specific conditions, an attacker can exploit the null-pointer dereference vulnerability in audit_filter_rules to crash the system or execute arbitrary code with kernel privileges.

If successfully exploited, this vulnerability could allow an attacker to gain unauthorized access to sensitive information, modify system configurations, or disrupt the normal operation of the system.

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

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.10.76 or later. This can be done by obtaining the updated Kernel source code from the official Linux Kernel repository and compiling it for the target system.

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