Metrics
Affected Vendors & Products
Tue, 04 Aug 2026 09:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
cvssV3_1
|
Thu, 04 Dec 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-190 | |
| CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* |
Wed, 17 Sep 2025 11:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Linux
Linux linux Kernel |
|
| Vendors & Products |
Linux
Linux linux Kernel |
Tue, 16 Sep 2025 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
cvssV3_1
|
Mon, 15 Sep 2025 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In the Linux kernel, the following vulnerability has been resolved: crypto: cavium - prevent integer overflow loading firmware The "code_length" value comes from the firmware file. If your firmware is untrusted realistically there is probably very little you can do to protect yourself. Still we try to limit the damage as much as possible. Also Smatch marks any data read from the filesystem as untrusted and prints warnings if it not capped correctly. The "ntohl(ucode->code_length) * 2" multiplication can have an integer overflow. | |
| Title | crypto: cavium - prevent integer overflow loading firmware | |
| References |
|
|
Status: PUBLISHED
Assigner: Linux
Published:
Updated: 2026-08-04T09:08:31.771Z
Reserved: 2025-09-15T14:18:36.815Z
Link: CVE-2022-50330
No data.
Status : Analyzed
Published: 2025-09-15T15:15:45.187
Modified: 2026-06-17T05:23:14.930
Link: CVE-2022-50330
OpenCVE Enrichment
Updated: 2025-09-17T10:06:51Z