CVE-2022-49813

MEDIUMNVD 5.55.5—Trending — 4 sources updated this week

5.5

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

net: ena: Fix error handling in ena_init()

The ena_init() won't destroy workqueue created by create_singlethread_workqueue() when pci_register_driver() failed. Call destroy_workqueue() when pci_register_driver() failed to prevent the resource leak.

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

Published

May 1, 2025

Last Modified

November 7, 2025

References (4)

416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/0e2369223b174d198ec42a3ec0a7f06c8727b968
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/3f7b2ef8fe924e299bc339811ea3f1b9935c040f
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/6b23a4b252044e4fd23438930d452244818d7000
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/d349e9be5a2c2d7588a2c4e4bfa0bb3dc1226769

Weakness Classification(1)

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

CWE-908Use of Uninitialized Resource

Data Freshness Timeline

(refreshed 10× in last 7d / 10× 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-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-30 06:30 UTCEG score recompute
2026-05-30 06:29 UTCGHSA enrichment
2026-05-29 21:20 UTCOSV refresh
2026-05-29 13:43 UTCepss_batch

Frequently asked(5)

What is CVE-2022-49813?

CVE-2022-49813 is a medium vulnerability published on May 1, 2025. In the Linux kernel, the following vulnerability has been resolved: net: ena: Fix error handling in ena_init() The ena_init() won't destroy workqueue created by createsinglethreadworkqueue() when pciregisterdriver() failed. Call destroyworkqueue() when pciregister_driver() failed to prevent the…

When was CVE-2022-49813 disclosed?

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

Is CVE-2022-49813 actively exploited?

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

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

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

How do I remediate CVE-2022-49813?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49813, 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-49813

Explore →

Is Your Infrastructure Affected by CVE-2022-49813?

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

Start Free Scan →Browse All CVEs

CVE-2022-49813

📅 Published

🔄 Last Modified

🔗 References (4)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2022-49813?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (4)

Frequently asked(5)

Related CVEs(same CWE)