cve-2024-50303
Vulnerability from cvelistv5
Published
2024-11-19 17:19
Modified
2024-12-19 09:37
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: resource,kexec: walk_system_ram_res_rev must retain resource flags walk_system_ram_res_rev() erroneously discards resource flags when passing the information to the callback. This causes systems with IORESOURCE_SYSRAM_DRIVER_MANAGED memory to have these resources selected during kexec to store kexec buffers if that memory happens to be at placed above normal system ram. This leads to undefined behavior after reboot. If the kexec buffer is never touched, nothing happens. If the kexec buffer is touched, it could lead to a crash (like below) or undefined behavior. Tested on a system with CXL memory expanders with driver managed memory, TPM enabled, and CONFIG_IMA_KEXEC=y. Adding printk's showed the flags were being discarded and as a result the check for IORESOURCE_SYSRAM_DRIVER_MANAGED passes. find_next_iomem_res: name(System RAM (kmem)) start(10000000000) end(1034fffffff) flags(83000200) locate_mem_hole_top_down: start(10000000000) end(1034fffffff) flags(0) [.] BUG: unable to handle page fault for address: ffff89834ffff000 [.] #PF: supervisor read access in kernel mode [.] #PF: error_code(0x0000) - not-present page [.] PGD c04c8bf067 P4D c04c8bf067 PUD c04c8be067 PMD 0 [.] Oops: 0000 [#1] SMP [.] RIP: 0010:ima_restore_measurement_list+0x95/0x4b0 [.] RSP: 0018:ffffc900000d3a80 EFLAGS: 00010286 [.] RAX: 0000000000001000 RBX: 0000000000000000 RCX: ffff89834ffff000 [.] RDX: 0000000000000018 RSI: ffff89834ffff000 RDI: ffff89834ffff018 [.] RBP: ffffc900000d3ba0 R08: 0000000000000020 R09: ffff888132b8a900 [.] R10: 4000000000000000 R11: 000000003a616d69 R12: 0000000000000000 [.] R13: ffffffff8404ac28 R14: 0000000000000000 R15: ffff89834ffff000 [.] FS: 0000000000000000(0000) GS:ffff893d44640000(0000) knlGS:0000000000000000 [.] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [.] ata5: SATA link down (SStatus 0 SControl 300) [.] CR2: ffff89834ffff000 CR3: 000001034d00f001 CR4: 0000000000770ef0 [.] PKRU: 55555554 [.] Call Trace: [.] <TASK> [.] ? __die+0x78/0xc0 [.] ? page_fault_oops+0x2a8/0x3a0 [.] ? exc_page_fault+0x84/0x130 [.] ? asm_exc_page_fault+0x22/0x30 [.] ? ima_restore_measurement_list+0x95/0x4b0 [.] ? template_desc_init_fields+0x317/0x410 [.] ? crypto_alloc_tfm_node+0x9c/0xc0 [.] ? init_ima_lsm+0x30/0x30 [.] ima_load_kexec_buffer+0x72/0xa0 [.] ima_init+0x44/0xa0 [.] __initstub__kmod_ima__373_1201_init_ima7+0x1e/0xb0 [.] ? init_ima_lsm+0x30/0x30 [.] do_one_initcall+0xad/0x200 [.] ? idr_alloc_cyclic+0xaa/0x110 [.] ? new_slab+0x12c/0x420 [.] ? new_slab+0x12c/0x420 [.] ? number+0x12a/0x430 [.] ? sysvec_apic_timer_interrupt+0xa/0x80 [.] ? asm_sysvec_apic_timer_interrupt+0x16/0x20 [.] ? parse_args+0xd4/0x380 [.] ? parse_args+0x14b/0x380 [.] kernel_init_freeable+0x1c1/0x2b0 [.] ? rest_init+0xb0/0xb0 [.] kernel_init+0x16/0x1a0 [.] ret_from_fork+0x2f/0x40 [.] ? rest_init+0xb0/0xb0 [.] ret_from_fork_asm+0x11/0x20 [.] </TASK>
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/b125a0def25a082ae944c9615208bf359abdb61cPatch
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/dc9031b7919bd346514ea9a720f433b8daf3970dPatch
Impacted products
Vendor Product Version
Linux Linux Version: 7acf164b259d9007264d9d8501da1023f140a3b4
Version: 7acf164b259d9007264d9d8501da1023f140a3b4
 Create a notification for this product.
   Linux Linux Version: 6.8
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "kernel/resource.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "dc9031b7919bd346514ea9a720f433b8daf3970d",
              "status": "affected",
              "version": "7acf164b259d9007264d9d8501da1023f140a3b4",
              "versionType": "git"
            },
            {
              "lessThan": "b125a0def25a082ae944c9615208bf359abdb61c",
              "status": "affected",
              "version": "7acf164b259d9007264d9d8501da1023f140a3b4",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "kernel/resource.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "6.8"
            },
            {
              "lessThan": "6.8",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.11.*",
              "status": "unaffected",
              "version": "6.11.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.12",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nresource,kexec: walk_system_ram_res_rev must retain resource flags\n\nwalk_system_ram_res_rev() erroneously discards resource flags when passing\nthe information to the callback.\n\nThis causes systems with IORESOURCE_SYSRAM_DRIVER_MANAGED memory to have\nthese resources selected during kexec to store kexec buffers if that\nmemory happens to be at placed above normal system ram.\n\nThis leads to undefined behavior after reboot.  If the kexec buffer is\nnever touched, nothing happens.  If the kexec buffer is touched, it could\nlead to a crash (like below) or undefined behavior.\n\nTested on a system with CXL memory expanders with driver managed memory,\nTPM enabled, and CONFIG_IMA_KEXEC=y.  Adding printk\u0027s showed the flags\nwere being discarded and as a result the check for\nIORESOURCE_SYSRAM_DRIVER_MANAGED passes.\n\nfind_next_iomem_res: name(System RAM (kmem))\n\t\t     start(10000000000)\n\t\t     end(1034fffffff)\n\t\t     flags(83000200)\n\nlocate_mem_hole_top_down: start(10000000000) end(1034fffffff) flags(0)\n\n[.] BUG: unable to handle page fault for address: ffff89834ffff000\n[.] #PF: supervisor read access in kernel mode\n[.] #PF: error_code(0x0000) - not-present page\n[.] PGD c04c8bf067 P4D c04c8bf067 PUD c04c8be067 PMD 0\n[.] Oops: 0000 [#1] SMP\n[.] RIP: 0010:ima_restore_measurement_list+0x95/0x4b0\n[.] RSP: 0018:ffffc900000d3a80 EFLAGS: 00010286\n[.] RAX: 0000000000001000 RBX: 0000000000000000 RCX: ffff89834ffff000\n[.] RDX: 0000000000000018 RSI: ffff89834ffff000 RDI: ffff89834ffff018\n[.] RBP: ffffc900000d3ba0 R08: 0000000000000020 R09: ffff888132b8a900\n[.] R10: 4000000000000000 R11: 000000003a616d69 R12: 0000000000000000\n[.] R13: ffffffff8404ac28 R14: 0000000000000000 R15: ffff89834ffff000\n[.] FS:  0000000000000000(0000) GS:ffff893d44640000(0000) knlGS:0000000000000000\n[.] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[.] ata5: SATA link down (SStatus 0 SControl 300)\n[.] CR2: ffff89834ffff000 CR3: 000001034d00f001 CR4: 0000000000770ef0\n[.] PKRU: 55555554\n[.] Call Trace:\n[.]  \u003cTASK\u003e\n[.]  ? __die+0x78/0xc0\n[.]  ? page_fault_oops+0x2a8/0x3a0\n[.]  ? exc_page_fault+0x84/0x130\n[.]  ? asm_exc_page_fault+0x22/0x30\n[.]  ? ima_restore_measurement_list+0x95/0x4b0\n[.]  ? template_desc_init_fields+0x317/0x410\n[.]  ? crypto_alloc_tfm_node+0x9c/0xc0\n[.]  ? init_ima_lsm+0x30/0x30\n[.]  ima_load_kexec_buffer+0x72/0xa0\n[.]  ima_init+0x44/0xa0\n[.]  __initstub__kmod_ima__373_1201_init_ima7+0x1e/0xb0\n[.]  ? init_ima_lsm+0x30/0x30\n[.]  do_one_initcall+0xad/0x200\n[.]  ? idr_alloc_cyclic+0xaa/0x110\n[.]  ? new_slab+0x12c/0x420\n[.]  ? new_slab+0x12c/0x420\n[.]  ? number+0x12a/0x430\n[.]  ? sysvec_apic_timer_interrupt+0xa/0x80\n[.]  ? asm_sysvec_apic_timer_interrupt+0x16/0x20\n[.]  ? parse_args+0xd4/0x380\n[.]  ? parse_args+0x14b/0x380\n[.]  kernel_init_freeable+0x1c1/0x2b0\n[.]  ? rest_init+0xb0/0xb0\n[.]  kernel_init+0x16/0x1a0\n[.]  ret_from_fork+0x2f/0x40\n[.]  ? rest_init+0xb0/0xb0\n[.]  ret_from_fork_asm+0x11/0x20\n[.]  \u003c/TASK\u003e"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-12-19T09:37:48.281Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/dc9031b7919bd346514ea9a720f433b8daf3970d"
        },
        {
          "url": "https://git.kernel.org/stable/c/b125a0def25a082ae944c9615208bf359abdb61c"
        }
      ],
      "title": "resource,kexec: walk_system_ram_res_rev must retain resource flags",
      "x_generator": {
        "engine": "bippy-5f407fcff5a0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-50303",
    "datePublished": "2024-11-19T17:19:29.585Z",
    "dateReserved": "2024-10-21T19:36:19.987Z",
    "dateUpdated": "2024-12-19T09:37:48.281Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-50303\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-11-19T18:15:22.263\",\"lastModified\":\"2024-11-27T21:29:30.267\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nresource,kexec: walk_system_ram_res_rev must retain resource flags\\n\\nwalk_system_ram_res_rev() erroneously discards resource flags when passing\\nthe information to the callback.\\n\\nThis causes systems with IORESOURCE_SYSRAM_DRIVER_MANAGED memory to have\\nthese resources selected during kexec to store kexec buffers if that\\nmemory happens to be at placed above normal system ram.\\n\\nThis leads to undefined behavior after reboot.  If the kexec buffer is\\nnever touched, nothing happens.  If the kexec buffer is touched, it could\\nlead to a crash (like below) or undefined behavior.\\n\\nTested on a system with CXL memory expanders with driver managed memory,\\nTPM enabled, and CONFIG_IMA_KEXEC=y.  Adding printk\u0027s showed the flags\\nwere being discarded and as a result the check for\\nIORESOURCE_SYSRAM_DRIVER_MANAGED passes.\\n\\nfind_next_iomem_res: name(System RAM (kmem))\\n\\t\\t     start(10000000000)\\n\\t\\t     end(1034fffffff)\\n\\t\\t     flags(83000200)\\n\\nlocate_mem_hole_top_down: start(10000000000) end(1034fffffff) flags(0)\\n\\n[.] BUG: unable to handle page fault for address: ffff89834ffff000\\n[.] #PF: supervisor read access in kernel mode\\n[.] #PF: error_code(0x0000) - not-present page\\n[.] PGD c04c8bf067 P4D c04c8bf067 PUD c04c8be067 PMD 0\\n[.] Oops: 0000 [#1] SMP\\n[.] RIP: 0010:ima_restore_measurement_list+0x95/0x4b0\\n[.] RSP: 0018:ffffc900000d3a80 EFLAGS: 00010286\\n[.] RAX: 0000000000001000 RBX: 0000000000000000 RCX: ffff89834ffff000\\n[.] RDX: 0000000000000018 RSI: ffff89834ffff000 RDI: ffff89834ffff018\\n[.] RBP: ffffc900000d3ba0 R08: 0000000000000020 R09: ffff888132b8a900\\n[.] R10: 4000000000000000 R11: 000000003a616d69 R12: 0000000000000000\\n[.] R13: ffffffff8404ac28 R14: 0000000000000000 R15: ffff89834ffff000\\n[.] FS:  0000000000000000(0000) GS:ffff893d44640000(0000) knlGS:0000000000000000\\n[.] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\\n[.] ata5: SATA link down (SStatus 0 SControl 300)\\n[.] CR2: ffff89834ffff000 CR3: 000001034d00f001 CR4: 0000000000770ef0\\n[.] PKRU: 55555554\\n[.] Call Trace:\\n[.]  \u003cTASK\u003e\\n[.]  ? __die+0x78/0xc0\\n[.]  ? page_fault_oops+0x2a8/0x3a0\\n[.]  ? exc_page_fault+0x84/0x130\\n[.]  ? asm_exc_page_fault+0x22/0x30\\n[.]  ? ima_restore_measurement_list+0x95/0x4b0\\n[.]  ? template_desc_init_fields+0x317/0x410\\n[.]  ? crypto_alloc_tfm_node+0x9c/0xc0\\n[.]  ? init_ima_lsm+0x30/0x30\\n[.]  ima_load_kexec_buffer+0x72/0xa0\\n[.]  ima_init+0x44/0xa0\\n[.]  __initstub__kmod_ima__373_1201_init_ima7+0x1e/0xb0\\n[.]  ? init_ima_lsm+0x30/0x30\\n[.]  do_one_initcall+0xad/0x200\\n[.]  ? idr_alloc_cyclic+0xaa/0x110\\n[.]  ? new_slab+0x12c/0x420\\n[.]  ? new_slab+0x12c/0x420\\n[.]  ? number+0x12a/0x430\\n[.]  ? sysvec_apic_timer_interrupt+0xa/0x80\\n[.]  ? asm_sysvec_apic_timer_interrupt+0x16/0x20\\n[.]  ? parse_args+0xd4/0x380\\n[.]  ? parse_args+0x14b/0x380\\n[.]  kernel_init_freeable+0x1c1/0x2b0\\n[.]  ? rest_init+0xb0/0xb0\\n[.]  kernel_init+0x16/0x1a0\\n[.]  ret_from_fork+0x2f/0x40\\n[.]  ? rest_init+0xb0/0xb0\\n[.]  ret_from_fork_asm+0x11/0x20\\n[.]  \u003c/TASK\u003e\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: resource,kexec: walk_system_ram_res_rev debe conservar los indicadores de recursos walk_system_ram_res_rev() descarta err\u00f3neamente los indicadores de recursos al pasar la informaci\u00f3n a la devoluci\u00f3n de llamada. Esto hace que los sistemas con memoria IORESOURCE_SYSRAM_DRIVER_MANAGED tengan estos recursos seleccionados durante kexec para almacenar b\u00faferes kexec si esa memoria est\u00e1 ubicada por encima de la RAM normal del sistema. Esto conduce a un comportamiento indefinido despu\u00e9s del reinicio. Si nunca se toca el b\u00fafer kexec, no sucede nada. Si se toca el b\u00fafer kexec, podr\u00eda provocar un bloqueo (como a continuaci\u00f3n) o un comportamiento indefinido. Probado en un sistema con expansores de memoria CXL con memoria administrada por el controlador, TPM habilitado y CONFIG_IMA_KEXEC=y. Agregar printk mostr\u00f3 que los indicadores se descartaban y, como resultado, la verificaci\u00f3n de IORESOURCE_SYSRAM_DRIVER_MANAGED pasa. find_next_iomem_res: name(System RAM (kmem)) start(10000000000) end(1034fffffff) flags(83000200) locate_mem_hole_top_down: start(10000000000) end(1034fffffff) flags(0) [.] ERROR: no se puede manejar el error de p\u00e1gina para la direcci\u00f3n: ffff89834ffff000 [.] #PF: acceso de lectura del supervisor en modo kernel [.] #PF: error_code(0x0000) - p\u00e1gina no presente [.] PGD c04c8bf067 P4D c04c8bf067 PUD c04c8be067 PMD 0 [.] Oops: 0000 [#1] SMP [.] RIP: 0010:lista_de_mediciones_de_restauraci\u00f3n_ima+0x95/0x4b0 [.] RSP: 0018:ffffc900000d3a80 EFLAGS: 00010286 [.] RAX: 0000000000001000 RBX: 0000000000000000 RCX: ffff89834ffff000 [.] RDX: 0000000000000018 RSI: ffff89834ffff000 RDI: ffff89834ffff018 [.] RBP: ffffc900000d3ba0 R08: 0000000000000020 R09: ffff888132b8a900 [.] R10: 4000000000000000 R11: 000000003a616d69 R12: 0000000000000000 [.] R13: ffffffff8404ac28 R14: 0000000000000000 R15: ffff89834ffff000 [.] FS: 000000000000000(0000) GS:ffff893d44640000(0000) knlGS:0000000000000000 [.] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [.] ata5: enlace SATA inactivo (SStatus 0 SControl 300) [.] CR2: ffff89834ffff000 CR3: 000001034d00f001 CR4: 0000000000770ef0 [.] PKRU: 55555554 [.] Seguimiento de llamadas: [.]  [.] ? __die+0x78/0xc0 [.] ? page_fault_oops+0x2a8/0x3a0 [.] ? exc_page_fault+0x84/0x130 [.] ? asm_exc_page_fault+0x22/0x30 [.] ? ima_restore_measurement_list+0x95/0x4b0 [.] ? plantilla_desc_init_fields+0x317/0x410 [.] ? crypto_alloc_tfm_node+0x9c/0xc0 [.] ? init_ima_lsm+0x30/0x30 [.] ima_load_kexec_buffer+0x72/0xa0 [.] ima_init+0x44/0xa0 [.] __initstub__kmod_ima__373_1201_init_ima7+0x1e/0xb0 [.] ? init_ima_lsm+0x30/0x30 [.] hacer_una_initcall+0xad/0x200 [.] ? idr_alloc_cyclic+0xaa/0x110 [.] ? nueva_losa+0x12c/0x420 [.] ? nueva_losa+0x12c/0x420 [.] ? numero+0x12a/0x430 [.] ? sysvec_apic_timer_interrupt+0xa/0x80 [.] ? asm_sysvec_apic_timer_interrupt+0x16/0x20 [.] ? analizar_args+0xd4/0x380 [.] ? analizar_args+0x14b/0x380 [.] kernel_init_freeable+0x1c1/0x2b0 [.] ? rest_init+0xb0/0xb0 [.] kernel_init+0x16/0x1a0 [.] ret_from_fork+0x2f/0x40 [.] ? rest_init+0xb0/0xb0 [.] ret_desde_fork_asm+0x11/0x20 [.] \"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.8\",\"versionEndExcluding\":\"6.11.7\",\"matchCriteriaId\":\"40C0D9F3-9632-46FE-AA28-8CD73B52DEE7\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"7F361E1D-580F-4A2D-A509-7615F73167A1\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc2:*:*:*:*:*:*\",\"matchCriteriaId\":\"925478D0-3E3D-4E6F-ACD5-09F28D5DF82C\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc3:*:*:*:*:*:*\",\"matchCriteriaId\":\"3C95E234-D335-4B6C-96BF-E2CEBD8654ED\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc4:*:*:*:*:*:*\",\"matchCriteriaId\":\"E0F717D8-3014-4F84-8086-0124B2111379\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc5:*:*:*:*:*:*\",\"matchCriteriaId\":\"24DBE6C7-2AAE-4818-AED2-E131F153D2FA\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.12:rc6:*:*:*:*:*:*\",\"matchCriteriaId\":\"24B88717-53F5-42AA-9B72-14C707639E3F\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/b125a0def25a082ae944c9615208bf359abdb61c\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/dc9031b7919bd346514ea9a720f433b8daf3970d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]}]}}"
  }
}


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 seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.