CVE-2022-50763: crypto: marvell/octeontx - prevent integer overflows
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.25% (FIRST EPSS).
- Fixed version: Linux Linux 12acfa1059ad69aa352ddb2bf23ba1b831aff15f, 7bfa7d67735381715c98091194e81e7685f9b7db, 8f5eee162e55175d9dac98b5e9b8da76449d2257.
Low priority for now. Upgrade to Linux Linux 12acfa1059ad69aa352ddb2bf23ba1b831aff15f, 7bfa7d67735381715c98091194e81e7685f9b7db, 8f5eee162e55175d9dac98b5e9b8da76449d2257 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: crypto: marvell/octeontx - prevent integer overflows 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 "code_length * 2" can overflow. The round_up(ucode_size, 16) + sizeof() expression can overflow too. Prevent these overflows.
- Published
- Dec 24, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.7affected
- d9110b0b01ff1cd02751cd5c2c94e938a8906083 and later · before 7bfa7d67735381715c98091194e81e7685f9b7dbaffected · git
- d9110b0b01ff1cd02751cd5c2c94e938a8906083 and later · before 12acfa1059ad69aa352ddb2bf23ba1b831aff15faffected · git
- d9110b0b01ff1cd02751cd5c2c94e938a8906083 and later · before 8f5eee162e55175d9dac98b5e9b8da76449d2257affected · git
- d9110b0b01ff1cd02751cd5c2c94e938a8906083 and later · before e7ff7a46baafd38d7ed45604397e650d61f5db8daffected · git
- d9110b0b01ff1cd02751cd5c2c94e938a8906083 and later · before caca37cf6c749ff0303f68418cfe7b757a4e0697affected · git
- before 5.7not affected · semver
- 5.10.150 and later · up to and including 5.10.*not affected · semver
- 5.15.75 and later · up to and including 5.15.*not affected · semver
- 5.19.17 and later · up to and including 5.19.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.0.3-1 | 6.0.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-50761Dec 24, 2025 · x86/xen: Fix memory leak in xen_init_lock_cpu()0Monitor
- ← EarlierCVE-2022-50762Dec 24, 2025 · fs/ntfs3: Avoid UBSAN error on true_sectors_per_clst()0Monitor
- Later →CVE-2022-50764Dec 24, 2025 · ipv6/sit: use DEV_STATS_INC() to avoid data-races0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 12acfa1059ad69aa352ddb2bf23ba1b831aff15f | Vendor (CNA) |
| Linux Linux | 7bfa7d67735381715c98091194e81e7685f9b7db | Vendor (CNA) |
| Linux Linux | 8f5eee162e55175d9dac98b5e9b8da76449d2257 | Vendor (CNA) |
| Linux Linux | caca37cf6c749ff0303f68418cfe7b757a4e0697 | Vendor (CNA) |
| Linux Linux | e7ff7a46baafd38d7ed45604397e650d61f5db8d | Vendor (CNA) |
| debian:linux | 6.0.3-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.