Use-After-Free Vulnerability in PackageKit - Memory Access Risk

packagekit Updated 02 Oct 2025

Summary

03/01/2024
N/A
No i
Low
3.3

CVE-2024-0217: A use-after-free flaw was found in PackageKitd. Affects packagekit across 2 version ranges.

< 9915e1b611e6d662f67e6c1dcd4e7fda5c31cba8 < 64278c9127e3333342b56ead99556161f7e86f79

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

PackageKit is a system designed to make installing and managing software on Linux easier. It provides a unified interface for package management across different distributions, allowing users to install, update, and remove software packages seamlessly. However, PackageKit is susceptible to a use-after-free vulnerability, which can lead to unintended memory access and potential data loss.

Vulnerability Detail

A use-after-free flaw was discovered in PackageKitd, where the cleanup mechanics for a transaction could be disrupted under certain conditions. This flaw allows memory access to regions that have already been freed, potentially leading to data corruption or crashes. Once a memory region is freed, it can be reallocated for other uses, resulting in the loss of any previously stored data in that region. The vulnerability affects multiple versions of PackageKit across different Debian ecosystems.

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

As a temporary measure, users can avoid operations that may trigger the use-after-free condition until the package is updated. This includes refraining from initiating multiple transactions simultaneously within PackageKit.

Conclusion

The use-after-free vulnerability in PackageKit poses a significant risk to system stability and data integrity. Users are strongly advised to update their PackageKit installations to the latest versions to mitigate this risk. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for packagekit →

Share this vulnerability

FAQ

A use-after-free vulnerability occurs when a program continues to use a memory reference after it has been freed, potentially leading to memory corruption or crashes.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. By uploading your manifest file like package-lock.json, you can check for vulnerabilities in real-time.

The vulnerability can lead to data loss, memory corruption, or crashes, which can compromise system stability and security.

Yes, updating to the latest version of PackageKit where the vulnerability has been patched is essential for safety.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

Related vulnerabilities

Recent vulnerabilities recorded for packagekit.

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