Refcount Leak in irqchip/gic-v3 Package
Summary
GSD-2022-1004497: irqchip/gic-v3: Fix refcount leak in gic_populate_ppi_partitions. Affects Kernel versions >= e3825ba1af3a27d7522c9f5f929f5a13b8b138ae, < cc5984cf270b69d03f9f4b27063e535036c659e9. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The irqchip/gic-v3 package is a component of the Linux Kernel, which is responsible for managing interrupt requests on systems that use the GICv3 interrupt controller. The GICv3 is commonly found in ARM-based systems and provides advanced interrupt handling capabilities. The package includes various modules and functions to handle interrupt partitioning and distribution. However, a vulnerability has been discovered in the gic_populate_ppi_partitions function, which can lead to a refcount leak.
Vulnerability Detail
The vulnerability in the gic_populate_ppi_partitions function of the irqchip/gic-v3 package allows for a refcount leak. This occurs when the function fails to properly release references to certain data structures, leading to a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory resources, resulting in a denial-of-service condition. The vulnerability was introduced in version v4.7 of the Linux Kernel and has been fixed in version v5.15.49.
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 necessary to apply the fix by updating the Linux Kernel.
Conclusion
The refcount leak vulnerability in the irqchip/gic-v3 package can lead to a denial-of-service condition by exhausting system memory resources. It is crucial to update the Linux Kernel to version v5.15.49 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a denial-of-service condition by exhausting system memory resources.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the playground will analyze it for vulnerabilities.
No, this vulnerability requires local access to the system.
There are no known instances of this vulnerability being exploited in the wild.
Yes, a patch is available in version v5.15.49 of the Linux Kernel.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
