cxl/pmem: Fix cxl_pmem_region and cxl_memdev leak

{
  "id": "924f544634470f9c3ff46ee44ee3526ed64f983881f3f0413809b4e16321bee5",
  "url": "https://osv.dev/vulnerability/CVE-2022-49896",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "cxl/pmem: Fix cxl_pmem_region and cxl_memdev leak",
    "summary": "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.",
    "evidence": "osv:CVE-2022-49896",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.0.8",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "medium",
    "structured": {
      "id": "CVE-2022-49896",
      "aliases": [
        "CVE-2022-49896"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "04ad63f086d1a9649b8b082748cbc7a570ade461"
                },
                {
                  "fixed": "f43b6bfdbab78606735ba81185cf0602b81e40b6"
                },
                {
                  "fixed": "4d07ae22e79ebc2d7528bbc69daa53b86981cb3a"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49896.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.0.0"
                },
                {
                  "fixed": "6.0.8"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49896.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:51.504811826Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/4d07ae22e79ebc2d7528bbc69daa53b86981cb3a",
        "https://git.kernel.org/stable/c/f43b6bfdbab78606735ba81185cf0602b81e40b6",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49896.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2022-49896",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49896.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2022-49896",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 520099,
  "published_at": "2025-05-01T14:10:38.336+00:00"
}