Bug 2363521 (CVE-2022-49896) - CVE-2022-49896 kernel: cxl/pmem: Fix cxl_pmem_region and cxl_memdev leak
Summary: CVE-2022-49896 kernel: cxl/pmem: Fix cxl_pmem_region and cxl_memdev leak
Keywords:
Status: NEW
Alias: CVE-2022-49896
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-05-01 15:08 UTC by OSIDB Bzimport
Modified: 2025-06-06 00:44 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-05-01 15:08:01 UTC
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.

Comment 1 Avinash Hanwate 2025-05-02 04:56:04 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025050100-CVE-2022-49896-2593@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.