First published: Thu May 01 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: cxl/pmem: Fix cxl_pmem_region and cxl_memdev leak When a cxl_nvdimm object goes through a ->remove() event (device physically removed, nvdimm-bridge disabled, or nvdimm device disabled), then any associated regions must also be disabled. As highlighted by the cxl-create-region.sh test [1], a single device may host multiple regions, but the driver was only tracking one region at a time. This leads to a situation where only the last enabled region per nvdimm device is cleaned up properly. Other regions are leaked, and this also causes cxl_memdev reference leaks. Fix the tracking by allowing cxl_nvdimm objects to track multiple region associations.
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | ||
Linux Kernel | >=6.0<6.0.8 | |
Linux Kernel | =6.1-rc1 | |
Linux Kernel | =6.1-rc2 | |
Linux Kernel | =6.1-rc3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2022-49896 is categorized as a moderate vulnerability in the Linux kernel.
To fix CVE-2022-49896, update the Linux kernel to a version that has addressed this vulnerability.
CVE-2022-49896 can lead to resource leaks in cxl_nvdimm objects, potentially affecting system performance.
CVE-2022-49896 affects various versions of the Linux kernel prior to the patch release that addresses this issue.
As of now, there are no public reports indicating that CVE-2022-49896 is being actively exploited in the wild.