net: ena: fix MMIO read buffer leak on probe failure
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.6.160, 6.12.112, 6.18.55, 7.2.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: net: ena: fix MMIO read buffer leak on probe failure ena_device_init() initializes the MMIO read mechanism with ena_com_mmio_reg_read_request_init(), which allocates a coherent DMA buffer for MMIO read responses. The normal removal path releases this buffer through ena_com_mmio_reg_read_request_destroy(). However, if ena_probe() fails after ena_device_init() succeeds, the error path destroys the admin resources and eventually frees ena_dev without destroying the MMIO read request, leaving the coherent DMA buffer allocated. Call ena_com_mmio_reg_read_request_destroy() in the probe error path before releasing the remaining device resources. This issue was found by manual code inspection.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 1738cd3ed342294360d6a74d4e58800004bff854 · fixed in a0f5fd7a285f44fa402242f26feddfe1d4a0fc6c; From 1738cd3ed342294360d6a74d4e58800004bff854 · fixed in 7bd3e9a2d0c288e54f51df260d9433163f5fbc1e; From 1738cd3ed342294360d6a74d4e58800004bff854 · fixed in 30ff01b4c7e419bb70f40f01dcd7f6af680808b3; From 1738cd3ed342294360d6a74d4e58800004bff854 · fixed in 47785f9f638b064ce6e32e8e3b6f1ffd83849fc2; From 1738cd3ed342294360d6a74d4e58800004bff854 · fixed in 9476b4468862927297c94c440863cd8ed1e7cc83
- Linux Linux
4.9
- KernelLinux
From 4.9.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.112; From 6.13.0 · fixed in 6.18.55; From 6.19.0 · fixed in 7.2.9