CVE-2022-49570

MEDIUMNVD 5.55.5—Trending — 4 sources updated this week

5.5

In the Linux kernel, the following vulnerability has been resolved:

gpio: gpio-xilinx: Fix integer overflow

Current implementation is not able to configure more than 32 pins due to incorrect data type. So type casting with unsigned long to avoid it.

CVSS v3: 5.5
EG Score: 5.5(medium)
EPSS: 34.4%
KEV: Not listed

Published

February 26, 2025

Last Modified

October 1, 2025

References (3)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/32c094a09d5829ad9b02cdf667569aefa8de0ea6
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/6f16a5390640807dde420ee5ccbc4c95577aea6a
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/e129e5486b981d324057e6986059f852658b0d00

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-190Integer Overflow or Wraparound

Data Freshness Timeline

(refreshed 16× in last 7d / 17× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-05 22:46 UTCepss_batch
2026-06-05 22:46 UTCepss_batch
2026-06-05 06:09 UTCepss_batch
2026-06-05 06:09 UTCepss_batch
2026-06-04 13:11 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-30 10:48 UTCEG score recompute
2026-05-30 10:48 UTCGHSA enrichment
2026-05-30 10:05 UTCOSV refresh
2026-05-29 13:43 UTCepss_batch

Frequently asked(5)

What is CVE-2022-49570?

CVE-2022-49570 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: gpio: gpio-xilinx: Fix integer overflow Current implementation is not able to configure more than 32 pins due to incorrect data type. So type casting with unsigned long to avoid it.

When was CVE-2022-49570 disclosed?

CVE-2022-49570 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on October 1, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2022-49570 actively exploited?

CVE-2022-49570 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 34.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2022-49570?

CVE-2022-49570 has a CVSS v3 base score of 5.5 (NVD).

How do I remediate CVE-2022-49570?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49570, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-49570

Explore →

Is Your Infrastructure Affected by CVE-2022-49570?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2022-49570

📅 Published

🔄 Last Modified

🔗 References (3)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2022-49570?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (3)

Frequently asked(5)

Related CVEs(same CWE)