CVE-2022-50330
BaseFortify
Publication date: 2025-09-15
Last updated on: 2025-12-04
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 4.11 (inc) to 4.14.296 (exc) |
| linux | linux_kernel | From 4.15 (inc) to 4.19.262 (exc) |
| linux | linux_kernel | From 4.20 (inc) to 5.4.220 (exc) |
| linux | linux_kernel | From 5.5 (inc) to 5.10.150 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.75 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 5.19.17 (exc) |
| linux | linux_kernel | From 6.0 (inc) to 6.0.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-190 | The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an integer overflow issue in the Linux kernel's crypto cavium driver when loading firmware. Specifically, the 'code_length' value, which comes from the firmware file, is multiplied by 2 using 'ntohl(ucode->code_length) * 2'. If this multiplication causes an integer overflow, it can lead to incorrect behavior or potential security risks. The vulnerability arises because the firmware is considered untrusted input, and the code did not properly limit or check this value to prevent overflow.
How can this vulnerability impact me? :
If exploited, this integer overflow could cause the Linux kernel to misinterpret the size of the firmware data, potentially leading to memory corruption or other unexpected behavior. Since the firmware is untrusted, this could be leveraged by an attacker to cause denial of service or possibly execute arbitrary code, depending on the context. However, the description notes that realistically there is very little you can do to protect yourself if the firmware is untrusted, but the fix aims to limit the damage as much as possible.
What immediate steps should I take to mitigate this vulnerability?
Since the vulnerability involves an integer overflow when loading untrusted firmware in the Linux kernel's cavium crypto module, immediate mitigation steps include ensuring that only trusted firmware is used and limiting exposure to untrusted firmware files. There is little that can be done if untrusted firmware must be used, but applying the latest kernel updates that include the fix is recommended.