Vulnerability in Kernel: crypto: hisilicon/sec - fix the aead software fallback for engine
Summary
GSD-2022-1001278: crypto: hisilicon/sec - fix the aead software fallback for engine. Affects Kernel versions >= 6c46a3297beae4ae2d22b26da5e091f058381c7c, < 5c1149e2abe0b7489300736b8277b45b113de67f. 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 Kernel is a fundamental component of the Linux operating system that provides core functionalities and interfaces between hardware and software. It is responsible for managing system resources, facilitating communication between different components, and ensuring security. The crypto subsystem within the Kernel provides cryptographic services, including encryption and decryption algorithms. The hisilicon/sec driver is a component of the crypto subsystem that supports hardware acceleration for cryptographic operations on HiSilicon platforms. However, a vulnerability has been identified in the aead software fallback mechanism of the hisilicon/sec driver, which could potentially lead to security breaches and unauthorized access to sensitive information.
Vulnerability Detail
The vulnerability in the hisilicon/sec driver's aead software fallback mechanism allows an attacker to bypass hardware acceleration and exploit software-based cryptographic operations. This can result in reduced performance and increased vulnerability to side-channel attacks. The issue was introduced in Linux Kernel version v5.14 and was fixed in version v5.17.2. The vulnerability could potentially be exploited to decrypt encrypted data, tamper with cryptographic operations, or launch other attacks that rely on cryptographic integrity. It is important to promptly apply the fix to mitigate the risk of exploitation.
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 workaround, users can disable the hisilicon/sec driver or the aead software fallback mechanism. However, this may result in a loss of hardware acceleration for cryptographic operations and potentially impact system performance. Disabling the driver or fallback mechanism should only be considered if immediate update to the fixed Kernel version is not feasible. The specific steps to disable the driver or fallback mechanism may vary depending on the Linux distribution and system configuration. It is recommended to consult the official documentation or seek assistance from the Linux distribution's support channels for guidance on implementing the workaround.
Conclusion
The vulnerability in the hisilicon/sec driver's aead software fallback mechanism poses a risk to the security and performance of Linux systems. It is crucial to update the Linux Kernel to version v5.17.2 or later to address the vulnerability. Alternatively, users can implement the temporary workaround of disabling the driver or fallback mechanism, although this may impact system performance. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability allows an attacker to bypass hardware acceleration and exploit software-based cryptographic operations, potentially leading to unauthorized access to sensitive information and reduced system performance.
You can use tools like Vulert (https://vulert.com) to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in the software.
It is recommended to update the Linux Kernel to version v5.17.2 or later. Alternatively, you can disable the hisilicon/sec driver or the aead software fallback mechanism as a temporary workaround, although this may impact system performance.
The vulnerability can potentially be exploited remotely if the affected system is accessible over a network. It is important to apply the fix or workaround as soon as possible to mitigate the risk of remote exploitation.
There are no known instances of this vulnerability being exploited in the wild. However, it is important to proactively address the vulnerability to minimize the risk of exploitation.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
