Vulnerability · CVE-2022-49819
In the Linux kernel, the following vulnerability has been resolved: octeon_ep: fix potential memory leak in octep_device_setup() When occur unsupported_dev and mbox init errors, it
Published May 1, 2025 · corrected/updated May 11, 2026 · Linux Linux · evidence confidence high
In the Linux kernel, the following vulnerability has been resolved: octeon_ep: fix potential memory leak in octep_device_setup() When occur unsupported_dev and mbox init errors, it did not free oct->conf and iounmap() oct->mmio[i].hw_addr. That would trigger memory leak problem. Add kfree() for oct->conf and iounmap() for oct->mmio[i].hw_addr under unsupported_dev and mbox init errors to fix the problem.
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2022-49819 is a none public vulnerability record for Linux Linux. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether Linux Linux is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: Linux Linux 862cd659a6fbac664f1fcdd7149046040a7a7e9c <e4041be97b15302ebfffda8bbd45f3b2d096048f (862cd659a6fbac664f1fcdd7149046040a7a7e9c <e4041be97b15302ebfffda8bbd45f3b2d096048f). Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: CVSS 0.0, EPSS 17.0%. It is not currently listed in the CISA Known Exploited catalog. Sources contributing to this record: cve_org, euvd. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Not listed as known exploited in CISA KEV. Not in CISA KEV or VulnCheck KEV.
Patch and remediation
No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
May 1, 2025 · EUVD
Detected
In the Linux kernel, the following vulnerability has been resolved: octeon_ep: fix potential memory leak in octep_device_setup() When occur unsupported_dev and mbox init errors, it did not free oct->conf and iounmap() oct->mmio[i].hw_addr. That would trigger memory leak problem. Add kfree() for oct->conf and iounmap() for oct->mmio[i].hw_addr under unsupported_dev and mbox init errors to fix the p
May 11, 2026 · EUVD
Updated
In the Linux kernel, the following vulnerability has been resolved: octeon_ep: fix potential memory leak in octep_device_setup() When occur unsupported_dev and mbox init errors, it did not free oct->conf and iounmap() oct->mmio[i].hw_addr. That would trigger memory leak problem. Add kfree() for oct->conf and iounmap() for oct->mmio[i].hw_addr under unsupported_dev and mbox init errors to fix the p
Affected
- vendor Linux Linux 862cd659a6fbac664f1fcdd7149046040a7a7e9c <e4041be97b15302ebfffda8bbd45f3b2d096048f862cd659a6fbac664f1fcdd7149046040a7a7e9c <e4041be97b15302ebfffda8bbd45f3b2d096048f
Sources
- CVE.orgVulnerability recordCVE-2022-49819
Official CVE identifier
cve.org - EUVDVulnerability recordEUVD-2025-12947
In the Linux kernel, the following vulnerability has been resolved: octeon_ep: fix potential memory leak in octep_device_setup() When occur unsupported_dev and mbox init errors, it did not free oct->conf and iounmap() oct->mmio[i].hw_addr. That would trigger memory leak problem.
euvd.enisa.europa.eu