Use-after-free vulnerability in iio: trigger: sysfs
Summary
GSD-2022-1004254: iio: trigger: sysfs: fix use-after-free on remove. Affects Kernel versions >= f38bc926d022ebd67baad6ac7fc22c95fbc6238c, < 4ef1e521be610b720daeb7cf899fedc7db0274c4. 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 iio: trigger: sysfs package is a component of the Linux Kernel ecosystem. It provides functionality related to the Industrial I/O (IIO) subsystem, which enables Linux to interface with various sensors and measurement devices. The sysfs interface allows userspace applications to interact with IIO triggers. However, a use-after-free vulnerability has been discovered in this package.
Vulnerability Detail
The use-after-free vulnerability in iio: trigger: sysfs occurs when a trigger is removed from the sysfs interface. Due to improper handling of references, a use-after-free condition can be triggered, potentially leading to a system crash or arbitrary code execution. This vulnerability was introduced in version v3.7 of the Linux Kernel and has been fixed in version v5.18.8.
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 use-after-free vulnerability in iio: trigger: sysfs can have serious consequences, including system crashes and potential code execution. It is crucial to update the Linux Kernel to version v5.18.8 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially lead to a system crash or allow an attacker to execute arbitrary code.
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 Vulert Playground will analyze it for vulnerabilities.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate the risk.
This vulnerability requires local access to the system in order to exploit it. Remote exploitation is not possible.
The only effective mitigation for this vulnerability is to update the Linux Kernel to a version that includes the fix.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
