CVE-2024-50022 (GCVE-0-2024-50022)

Vulnerability from cvelistv5 – Published: 2024-10-21 19:39 – Updated: 2025-11-03 22:24
VLAI?
Title
device-dax: correct pgoff align in dax_set_mapping()
Summary
In the Linux kernel, the following vulnerability has been resolved: device-dax: correct pgoff align in dax_set_mapping() pgoff should be aligned using ALIGN_DOWN() instead of ALIGN(). Otherwise, vmf->address not aligned to fault_size will be aligned to the next alignment, that can result in memory failure getting the wrong address. It's a subtle situation that only can be observed in page_mapped_in_vma() after the page is page fault handled by dev_dax_huge_fault. Generally, there is little chance to perform page_mapped_in_vma in dev-dax's page unless in specific error injection to the dax device to trigger an MCE - memory-failure. In that case, page_mapped_in_vma() will be triggered to determine which task is accessing the failure address and kill that task in the end. We used self-developed dax device (which is 2M aligned mapping) , to perform error injection to random address. It turned out that error injected to non-2M-aligned address was causing endless MCE until panic. Because page_mapped_in_vma() kept resulting wrong address and the task accessing the failure address was never killed properly: [ 3783.719419] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.049006] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.049190] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.448042] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.448186] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3784.792026] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3784.792179] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.162502] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.162633] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.461116] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.461247] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3785.764730] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3785.764859] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.042128] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.042259] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.464293] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.464423] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3786.818090] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3786.818217] Memory failure: 0x200c9742: recovery action for dax page: Recovered [ 3787.085297] mce: Uncorrected hardware memory error in user-access at 200c9742380 [ 3787.085424] Memory failure: 0x200c9742: recovery action for dax page: Recovered It took us several weeks to pinpoint this problem,  but we eventually used bpftrace to trace the page fault and mce address and successfully identified the issue. Joao added: ; Likely we never reproduce in production because we always pin : device-dax regions in the region align they provide (Qemu does : similarly with prealloc in hugetlb/file backed memory). I think this : bug requires that we touch *unpinned* device-dax regions unaligned to : the device-dax selected alignment (page size i.e. 4K/2M/1G)
Severity ?
No CVSS data available.
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: b9b5777f09be84d0de472ded2253d2f5101427f2 , < 9c4198dfdca818c5ce19c764d90eabd156bbc6da (git)
Affected: b9b5777f09be84d0de472ded2253d2f5101427f2 , < b822007e8db341d6f175c645ed79866db501ad86 (git)
Affected: b9b5777f09be84d0de472ded2253d2f5101427f2 , < e877427d218159ac29c9326100920d24330c9ee6 (git)
Affected: b9b5777f09be84d0de472ded2253d2f5101427f2 , < 7fcbd9785d4c17ea533c42f20a9083a83f301fa6 (git)
Create a notification for this product.
    Linux Linux Affected: 5.17
Unaffected: 0 , < 5.17 (semver)
Unaffected: 6.1.113 , ≤ 6.1.* (semver)
Unaffected: 6.6.57 , ≤ 6.6.* (semver)
Unaffected: 6.11.4 , ≤ 6.11.* (semver)
Unaffected: 6.12 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-50022",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-10-22T13:27:15.558211Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-10-22T13:28:47.118Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2025-11-03T22:24:33.602Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/dax/device.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "9c4198dfdca818c5ce19c764d90eabd156bbc6da",
              "status": "affected",
              "version": "b9b5777f09be84d0de472ded2253d2f5101427f2",
              "versionType": "git"
            },
            {
              "lessThan": "b822007e8db341d6f175c645ed79866db501ad86",
              "status": "affected",
              "version": "b9b5777f09be84d0de472ded2253d2f5101427f2",
              "versionType": "git"
            },
            {
              "lessThan": "e877427d218159ac29c9326100920d24330c9ee6",
              "status": "affected",
              "version": "b9b5777f09be84d0de472ded2253d2f5101427f2",
              "versionType": "git"
            },
            {
              "lessThan": "7fcbd9785d4c17ea533c42f20a9083a83f301fa6",
              "status": "affected",
              "version": "b9b5777f09be84d0de472ded2253d2f5101427f2",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/dax/device.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.17"
            },
            {
              "lessThan": "5.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.113",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.57",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.4",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.12",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.113",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.57",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.11.4",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndevice-dax: correct pgoff align in dax_set_mapping()\n\npgoff should be aligned using ALIGN_DOWN() instead of ALIGN().  Otherwise,\nvmf-\u003eaddress not aligned to fault_size will be aligned to the next\nalignment, that can result in memory failure getting the wrong address.\n\nIt\u0027s a subtle situation that only can be observed in\npage_mapped_in_vma() after the page is page fault handled by\ndev_dax_huge_fault.  Generally, there is little chance to perform\npage_mapped_in_vma in dev-dax\u0027s page unless in specific error injection\nto the dax device to trigger an MCE - memory-failure.  In that case,\npage_mapped_in_vma() will be triggered to determine which task is\naccessing the failure address and kill that task in the end.\n\n\nWe used self-developed dax device (which is 2M aligned mapping) , to\nperform error injection to random address.  It turned out that error\ninjected to non-2M-aligned address was causing endless MCE until panic.\nBecause page_mapped_in_vma() kept resulting wrong address and the task\naccessing the failure address was never killed properly:\n\n\n[ 3783.719419] Memory failure: 0x200c9742: recovery action for dax page: \nRecovered\n[ 3784.049006] mce: Uncorrected hardware memory error in user-access at \n200c9742380\n[ 3784.049190] Memory failure: 0x200c9742: recovery action for dax page: \nRecovered\n[ 3784.448042] mce: Uncorrected hardware memory error in user-access at \n200c9742380\n[ 3784.448186] Memory failure: 0x200c9742: recovery action for dax page: \nRecovered\n[ 3784.792026] mce: Uncorrected hardware memory error in user-access at \n200c9742380\n[ 3784.792179] Memory failure: 0x200c9742: recovery action for dax page: \nRecovered\n[ 3785.162502] mce: Uncorrected hardware memory error in user-access at \n200c9742380\n[ 3785.162633] Memory failure: 0x200c9742: recovery action for dax page: \nRecovered\n[ 3785.461116] mce: Uncorrected hardware memory error in user-access at \n200c9742380\n[ 3785.461247] Memory failure: 0x200c9742: recovery action for dax page: \nRecovered\n[ 3785.764730] mce: Uncorrected hardware memory error in user-access at \n200c9742380\n[ 3785.764859] Memory failure: 0x200c9742: recovery action for dax page: \nRecovered\n[ 3786.042128] mce: Uncorrected hardware memory error in user-access at \n200c9742380\n[ 3786.042259] Memory failure: 0x200c9742: recovery action for dax page: \nRecovered\n[ 3786.464293] mce: Uncorrected hardware memory error in user-access at \n200c9742380\n[ 3786.464423] Memory failure: 0x200c9742: recovery action for dax page: \nRecovered\n[ 3786.818090] mce: Uncorrected hardware memory error in user-access at \n200c9742380\n[ 3786.818217] Memory failure: 0x200c9742: recovery action for dax page: \nRecovered\n[ 3787.085297] mce: Uncorrected hardware memory error in user-access at \n200c9742380\n[ 3787.085424] Memory failure: 0x200c9742: recovery action for dax page: \nRecovered\n\nIt took us several weeks to pinpoint this problem,\u00a0 but we eventually\nused bpftrace to trace the page fault and mce address and successfully\nidentified the issue.\n\n\nJoao added:\n\n; Likely we never reproduce in production because we always pin\n: device-dax regions in the region align they provide (Qemu does\n: similarly with prealloc in hugetlb/file backed memory).  I think this\n: bug requires that we touch *unpinned* device-dax regions unaligned to\n: the device-dax selected alignment (page size i.e.  4K/2M/1G)"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-05-04T09:44:01.036Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/9c4198dfdca818c5ce19c764d90eabd156bbc6da"
        },
        {
          "url": "https://git.kernel.org/stable/c/b822007e8db341d6f175c645ed79866db501ad86"
        },
        {
          "url": "https://git.kernel.org/stable/c/e877427d218159ac29c9326100920d24330c9ee6"
        },
        {
          "url": "https://git.kernel.org/stable/c/7fcbd9785d4c17ea533c42f20a9083a83f301fa6"
        }
      ],
      "title": "device-dax: correct pgoff align in dax_set_mapping()",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-50022",
    "datePublished": "2024-10-21T19:39:27.873Z",
    "dateReserved": "2024-10-21T12:17:06.064Z",
    "dateUpdated": "2025-11-03T22:24:33.602Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html\"}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2025-11-03T22:24:33.602Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-50022\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-10-22T13:27:15.558211Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-10-22T13:27:18.704Z\"}}], \"cna\": {\"title\": \"device-dax: correct pgoff align in dax_set_mapping()\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"b9b5777f09be84d0de472ded2253d2f5101427f2\", \"lessThan\": \"9c4198dfdca818c5ce19c764d90eabd156bbc6da\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"b9b5777f09be84d0de472ded2253d2f5101427f2\", \"lessThan\": \"b822007e8db341d6f175c645ed79866db501ad86\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"b9b5777f09be84d0de472ded2253d2f5101427f2\", \"lessThan\": \"e877427d218159ac29c9326100920d24330c9ee6\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"b9b5777f09be84d0de472ded2253d2f5101427f2\", \"lessThan\": \"7fcbd9785d4c17ea533c42f20a9083a83f301fa6\", \"versionType\": \"git\"}], \"programFiles\": [\"drivers/dax/device.c\"], \"defaultStatus\": \"unaffected\"}, {\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"5.17\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.17\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"6.1.113\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.1.*\"}, {\"status\": \"unaffected\", \"version\": \"6.6.57\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.6.*\"}, {\"status\": \"unaffected\", \"version\": \"6.11.4\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"6.11.*\"}, {\"status\": \"unaffected\", \"version\": \"6.12\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"drivers/dax/device.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/9c4198dfdca818c5ce19c764d90eabd156bbc6da\"}, {\"url\": \"https://git.kernel.org/stable/c/b822007e8db341d6f175c645ed79866db501ad86\"}, {\"url\": \"https://git.kernel.org/stable/c/e877427d218159ac29c9326100920d24330c9ee6\"}, {\"url\": \"https://git.kernel.org/stable/c/7fcbd9785d4c17ea533c42f20a9083a83f301fa6\"}], \"x_generator\": {\"engine\": \"bippy-1.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndevice-dax: correct pgoff align in dax_set_mapping()\\n\\npgoff should be aligned using ALIGN_DOWN() instead of ALIGN().  Otherwise,\\nvmf-\u003eaddress not aligned to fault_size will be aligned to the next\\nalignment, that can result in memory failure getting the wrong address.\\n\\nIt\u0027s a subtle situation that only can be observed in\\npage_mapped_in_vma() after the page is page fault handled by\\ndev_dax_huge_fault.  Generally, there is little chance to perform\\npage_mapped_in_vma in dev-dax\u0027s page unless in specific error injection\\nto the dax device to trigger an MCE - memory-failure.  In that case,\\npage_mapped_in_vma() will be triggered to determine which task is\\naccessing the failure address and kill that task in the end.\\n\\n\\nWe used self-developed dax device (which is 2M aligned mapping) , to\\nperform error injection to random address.  It turned out that error\\ninjected to non-2M-aligned address was causing endless MCE until panic.\\nBecause page_mapped_in_vma() kept resulting wrong address and the task\\naccessing the failure address was never killed properly:\\n\\n\\n[ 3783.719419] Memory failure: 0x200c9742: recovery action for dax page: \\nRecovered\\n[ 3784.049006] mce: Uncorrected hardware memory error in user-access at \\n200c9742380\\n[ 3784.049190] Memory failure: 0x200c9742: recovery action for dax page: \\nRecovered\\n[ 3784.448042] mce: Uncorrected hardware memory error in user-access at \\n200c9742380\\n[ 3784.448186] Memory failure: 0x200c9742: recovery action for dax page: \\nRecovered\\n[ 3784.792026] mce: Uncorrected hardware memory error in user-access at \\n200c9742380\\n[ 3784.792179] Memory failure: 0x200c9742: recovery action for dax page: \\nRecovered\\n[ 3785.162502] mce: Uncorrected hardware memory error in user-access at \\n200c9742380\\n[ 3785.162633] Memory failure: 0x200c9742: recovery action for dax page: \\nRecovered\\n[ 3785.461116] mce: Uncorrected hardware memory error in user-access at \\n200c9742380\\n[ 3785.461247] Memory failure: 0x200c9742: recovery action for dax page: \\nRecovered\\n[ 3785.764730] mce: Uncorrected hardware memory error in user-access at \\n200c9742380\\n[ 3785.764859] Memory failure: 0x200c9742: recovery action for dax page: \\nRecovered\\n[ 3786.042128] mce: Uncorrected hardware memory error in user-access at \\n200c9742380\\n[ 3786.042259] Memory failure: 0x200c9742: recovery action for dax page: \\nRecovered\\n[ 3786.464293] mce: Uncorrected hardware memory error in user-access at \\n200c9742380\\n[ 3786.464423] Memory failure: 0x200c9742: recovery action for dax page: \\nRecovered\\n[ 3786.818090] mce: Uncorrected hardware memory error in user-access at \\n200c9742380\\n[ 3786.818217] Memory failure: 0x200c9742: recovery action for dax page: \\nRecovered\\n[ 3787.085297] mce: Uncorrected hardware memory error in user-access at \\n200c9742380\\n[ 3787.085424] Memory failure: 0x200c9742: recovery action for dax page: \\nRecovered\\n\\nIt took us several weeks to pinpoint this problem,\\u00a0 but we eventually\\nused bpftrace to trace the page fault and mce address and successfully\\nidentified the issue.\\n\\n\\nJoao added:\\n\\n; Likely we never reproduce in production because we always pin\\n: device-dax regions in the region align they provide (Qemu does\\n: similarly with prealloc in hugetlb/file backed memory).  I think this\\n: bug requires that we touch *unpinned* device-dax regions unaligned to\\n: the device-dax selected alignment (page size i.e.  4K/2M/1G)\"}], \"cpeApplicability\": [{\"nodes\": [{\"negate\": false, \"cpeMatch\": [{\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.1.113\", \"versionStartIncluding\": \"5.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.6.57\", \"versionStartIncluding\": \"5.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.11.4\", \"versionStartIncluding\": \"5.17\"}, {\"criteria\": \"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\", \"vulnerable\": true, \"versionEndExcluding\": \"6.12\", \"versionStartIncluding\": \"5.17\"}], \"operator\": \"OR\"}]}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2025-05-04T09:44:01.036Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-50022\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2025-11-03T22:24:33.602Z\", \"dateReserved\": \"2024-10-21T12:17:06.064Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-10-21T19:39:27.873Z\", \"assignerShortName\": \"Linux\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.