Critical Null Pointer Dereference in Linux Kernel Binder Package

linux Updated 02 Oct 2025

Summary

18/06/2025
N/A
Yes i
Unrated
Not published

CVE-2022-49947: In the Linux kernel, the following vulnerability has been resolved: binder: fix alloc->vma_vm_mm null-ptr dereference Syzbot reported a couple issues introduced by commit 44e602b4e52f ("binder_alloc: add missing mmap_loc... Affects linux versions < 6.0.2-1. Fixed in 6.0.2-1. 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 Linux kernel is the core component of many operating systems, responsible for managing hardware resources and providing essential services to software applications. The binder subsystem facilitates communication between different processes in Android environments. This subsystem is crucial for enabling inter-process communication (IPC) and is widely used in various applications. However, a recent vulnerability has been identified that affects the binder's memory management, potentially leading to system crashes and instability.

Vulnerability Detail

The vulnerability, identified as CVE-2022-49947, arises from a null pointer dereference in the binder subsystem of the Linux kernel. This issue was introduced by a commit that failed to properly initialize the 'alloc->vma_vm_mm' pointer before attempting to acquire the mmap_lock. If a binder process receives a transaction without having previously set up its memory allocation space, it can lead to a crash. The vulnerability can be exploited when the system attempts to dump debug information or handle transactions, resulting in a null pointer dereference and subsequent system instability.

How To Fix

Minimum fixed version

6.0.2-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to apply the patch by updating the kernel to the fixed version.

Conclusion

CVE-2022-49947 is a critical vulnerability in the Linux kernel's binder subsystem that can lead to severe system instability. Users are strongly advised to update their kernel to the patched version 6.0.2-1 or later to protect against potential exploitation. Regular monitoring and updates are essential for maintaining system security.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2022-49947 is a vulnerability in the Linux kernel's binder subsystem that can lead to a null pointer dereference, causing system crashes.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Simply upload your manifest file like package-lock.json to check for vulnerabilities.

Exploitation of this vulnerability can lead to system crashes and instability, affecting the overall performance and reliability of the operating system.

Yes, a patch is available in version 6.0.2-1 of the Linux kernel. Users should update to this version or later to mitigate the vulnerability.

The best way to secure your system is to regularly update your software packages, especially the Linux kernel, to the latest versions that include security patches.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

Minimum fixed version

6.0.2-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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