Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50814: crypto: hisilicon/zip - fix mismatch in get/set sgl_sge_nr

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.24% (FIRST EPSS).
  • Fixed version: Linux Linux 272093471305261c4e07a2fc97c2d1e53cd56819, 5eaebd19fbb0e26e73a34f55d3b1dc310df0eb15, d74f9340097a881869c4c22ca376654cc2516ecc.

Low priority for now. Upgrade to Linux Linux 272093471305261c4e07a2fc97c2d1e53cd56819, 5eaebd19fbb0e26e73a34f55d3b1dc310df0eb15, d74f9340097a881869c4c22ca376654cc2516ecc 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: hisilicon/zip - fix mismatch in get/set sgl_sge_nr KASAN reported this Bug: [17619.659757] BUG: KASAN: global-out-of-bounds in param_get_int+0x34/0x60 [17619.673193] Read of size 4 at addr fffff01332d7ed00 by task read_all/1507958 ... [17619.698934] The buggy address belongs to the variable: [17619.708371] sgl_sge_nr+0x0/0xffffffffffffa300 [hisi_zip] There is a mismatch in hisi_zip when get/set the variable sgl_sge_nr. The type of sgl_sge_nr is u16, and get/set sgl_sge_nr by param_get/set_int. Replacing param_get/set_int to param_get/set_ushort can fix this bug.

—No exploit Fix available
Published
Dec 30, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 15th percentile
CWE
—

Report tools

JSON

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.

Follow CVE-2022-50814

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

Affected 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.5affected
    • f081fda293ffba54216a7dab66faba7275475006 and later · before d88b88514ef28515ccfa1f1787c2aedef75a79ddaffected · git
    • f081fda293ffba54216a7dab66faba7275475006 and later · before 272093471305261c4e07a2fc97c2d1e53cd56819affected · git
    • f081fda293ffba54216a7dab66faba7275475006 and later · before f8a983d6e01b198320d310cb1326364d7d973b2aaffected · git
    • f081fda293ffba54216a7dab66faba7275475006 and later · before 5eaebd19fbb0e26e73a34f55d3b1dc310df0eb15affected · git
    • f081fda293ffba54216a7dab66faba7275475006 and later · before d74f9340097a881869c4c22ca376654cc2516eccaffected · git
    • before 5.5not 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.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.0.3-16.0.3-1

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2022-50812Dec 30, 2025 · security: Restrict CONFIG_ZERO_CALL_USED_REGS to gcc or clang > 15.0.6
    0Monitor
  • ← EarlierCVE-2022-50813Dec 30, 2025 · drivers: mcb: fix resource leak in mcb_probe()
    0Monitor
  • Later →CVE-2022-50815Dec 30, 2025 · ext2: Add sanity checks for group and filesystem size
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux272093471305261c4e07a2fc97c2d1e53cd56819Vendor (CNA)
Linux Linux5eaebd19fbb0e26e73a34f55d3b1dc310df0eb15Vendor (CNA)
Linux Linuxd74f9340097a881869c4c22ca376654cc2516eccVendor (CNA)
Linux Linuxd88b88514ef28515ccfa1f1787c2aedef75a79ddVendor (CNA)
Linux Linuxf8a983d6e01b198320d310cb1326364d7d973b2aVendor (CNA)
debian:linux6.0.3-1 · Debian:12Package 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.

Finders, 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

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records