cve-2022-48797
Vulnerability from cvelistv5
Published
2024-07-16 11:43
Modified
2024-12-19 08:07
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: mm: don't try to NUMA-migrate COW pages that have other uses Oded Gabbay reports that enabling NUMA balancing causes corruption with his Gaudi accelerator test load: "All the details are in the bug, but the bottom line is that somehow, this patch causes corruption when the numa balancing feature is enabled AND we don't use process affinity AND we use GUP to pin pages so our accelerator can DMA to/from system memory. Either disabling numa balancing, using process affinity to bind to specific numa-node or reverting this patch causes the bug to disappear" and Oded bisected the issue to commit 09854ba94c6a ("mm: do_wp_page() simplification"). Now, the NUMA balancing shouldn't actually be changing the writability of a page, and as such shouldn't matter for COW. But it appears it does. Suspicious. However, regardless of that, the condition for enabling NUMA faults in change_pte_range() is nonsensical. It uses "page_mapcount(page)" to decide if a COW page should be NUMA-protected or not, and that makes absolutely no sense. The number of mappings a page has is irrelevant: not only does GUP get a reference to a page as in Oded's case, but the other mappings migth be paged out and the only reference to them would be in the page count. Since we should never try to NUMA-balance a page that we can't move anyway due to other references, just fix the code to use 'page_count()'. Oded confirms that that fixes his issue. Now, this does imply that something in NUMA balancing ends up changing page protections (other than the obvious one of making the page inaccessible to get the NUMA faulting information). Otherwise the COW simplification wouldn't matter - since doing the GUP on the page would make sure it's writable. The cause of that permission change would be good to figure out too, since it clearly results in spurious COW events - but fixing the nonsensical test that just happened to work before is obviously the CorrectThing(tm) to do regardless.
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/254090925e16abd914c87b4ad1b489440d89c4c3
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/80d47f5de5e311cbc0d01ebb6ee684e8f4c196c6
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/b3dc4b9d3ca68b370c4aeab5355007eedf948849
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/d187eeb02d18446e5e54ed6bcbf8b47e6551daea
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/254090925e16abd914c87b4ad1b489440d89c4c3
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/80d47f5de5e311cbc0d01ebb6ee684e8f4c196c6
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/b3dc4b9d3ca68b370c4aeab5355007eedf948849
af854a3a-2127-422b-91ae-364da2661108https://git.kernel.org/stable/c/d187eeb02d18446e5e54ed6bcbf8b47e6551daea
Impacted products
Vendor Product Version
Linux Linux Version: 09854ba94c6aad7886996bfbee2530b3d8a7f4f4
Version: 09854ba94c6aad7886996bfbee2530b3d8a7f4f4
Version: 09854ba94c6aad7886996bfbee2530b3d8a7f4f4
Version: 09854ba94c6aad7886996bfbee2530b3d8a7f4f4
 Create a notification for this product.
   Linux Linux Version: 5.9
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2024-08-03T15:25:01.608Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://git.kernel.org/stable/c/254090925e16abd914c87b4ad1b489440d89c4c3",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://git.kernel.org/stable/c/b3dc4b9d3ca68b370c4aeab5355007eedf948849",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://git.kernel.org/stable/c/d187eeb02d18446e5e54ed6bcbf8b47e6551daea",
               },
               {
                  tags: [
                     "x_transferred",
                  ],
                  url: "https://git.kernel.org/stable/c/80d47f5de5e311cbc0d01ebb6ee684e8f4c196c6",
               },
            ],
            title: "CVE Program Container",
         },
         {
            metrics: [
               {
                  other: {
                     content: {
                        id: "CVE-2022-48797",
                        options: [
                           {
                              Exploitation: "none",
                           },
                           {
                              Automatable: "no",
                           },
                           {
                              "Technical Impact": "partial",
                           },
                        ],
                        role: "CISA Coordinator",
                        timestamp: "2024-09-10T16:59:16.178583Z",
                        version: "2.0.3",
                     },
                     type: "ssvc",
                  },
               },
            ],
            providerMetadata: {
               dateUpdated: "2024-09-11T17:34:14.839Z",
               orgId: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
               shortName: "CISA-ADP",
            },
            title: "CISA ADP Vulnrichment",
         },
      ],
      cna: {
         affected: [
            {
               defaultStatus: "unaffected",
               product: "Linux",
               programFiles: [
                  "mm/mprotect.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     lessThan: "254090925e16abd914c87b4ad1b489440d89c4c3",
                     status: "affected",
                     version: "09854ba94c6aad7886996bfbee2530b3d8a7f4f4",
                     versionType: "git",
                  },
                  {
                     lessThan: "b3dc4b9d3ca68b370c4aeab5355007eedf948849",
                     status: "affected",
                     version: "09854ba94c6aad7886996bfbee2530b3d8a7f4f4",
                     versionType: "git",
                  },
                  {
                     lessThan: "d187eeb02d18446e5e54ed6bcbf8b47e6551daea",
                     status: "affected",
                     version: "09854ba94c6aad7886996bfbee2530b3d8a7f4f4",
                     versionType: "git",
                  },
                  {
                     lessThan: "80d47f5de5e311cbc0d01ebb6ee684e8f4c196c6",
                     status: "affected",
                     version: "09854ba94c6aad7886996bfbee2530b3d8a7f4f4",
                     versionType: "git",
                  },
               ],
            },
            {
               defaultStatus: "affected",
               product: "Linux",
               programFiles: [
                  "mm/mprotect.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     status: "affected",
                     version: "5.9",
                  },
                  {
                     lessThan: "5.9",
                     status: "unaffected",
                     version: "0",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "5.10.*",
                     status: "unaffected",
                     version: "5.10.102",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "5.15.*",
                     status: "unaffected",
                     version: "5.15.25",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "5.16.*",
                     status: "unaffected",
                     version: "5.16.11",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "*",
                     status: "unaffected",
                     version: "5.17",
                     versionType: "original_commit_for_fix",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "In the Linux kernel, the following vulnerability has been resolved:\n\nmm: don't try to NUMA-migrate COW pages that have other uses\n\nOded Gabbay reports that enabling NUMA balancing causes corruption with\nhis Gaudi accelerator test load:\n\n \"All the details are in the bug, but the bottom line is that somehow,\n  this patch causes corruption when the numa balancing feature is\n  enabled AND we don't use process affinity AND we use GUP to pin pages\n  so our accelerator can DMA to/from system memory.\n\n  Either disabling numa balancing, using process affinity to bind to\n  specific numa-node or reverting this patch causes the bug to\n  disappear\"\n\nand Oded bisected the issue to commit 09854ba94c6a (\"mm: do_wp_page()\nsimplification\").\n\nNow, the NUMA balancing shouldn't actually be changing the writability\nof a page, and as such shouldn't matter for COW.  But it appears it\ndoes.  Suspicious.\n\nHowever, regardless of that, the condition for enabling NUMA faults in\nchange_pte_range() is nonsensical.  It uses \"page_mapcount(page)\" to\ndecide if a COW page should be NUMA-protected or not, and that makes\nabsolutely no sense.\n\nThe number of mappings a page has is irrelevant: not only does GUP get a\nreference to a page as in Oded's case, but the other mappings migth be\npaged out and the only reference to them would be in the page count.\n\nSince we should never try to NUMA-balance a page that we can't move\nanyway due to other references, just fix the code to use 'page_count()'.\nOded confirms that that fixes his issue.\n\nNow, this does imply that something in NUMA balancing ends up changing\npage protections (other than the obvious one of making the page\ninaccessible to get the NUMA faulting information).  Otherwise the COW\nsimplification wouldn't matter - since doing the GUP on the page would\nmake sure it's writable.\n\nThe cause of that permission change would be good to figure out too,\nsince it clearly results in spurious COW events - but fixing the\nnonsensical test that just happened to work before is obviously the\nCorrectThing(tm) to do regardless.",
            },
         ],
         providerMetadata: {
            dateUpdated: "2024-12-19T08:07:55.101Z",
            orgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            shortName: "Linux",
         },
         references: [
            {
               url: "https://git.kernel.org/stable/c/254090925e16abd914c87b4ad1b489440d89c4c3",
            },
            {
               url: "https://git.kernel.org/stable/c/b3dc4b9d3ca68b370c4aeab5355007eedf948849",
            },
            {
               url: "https://git.kernel.org/stable/c/d187eeb02d18446e5e54ed6bcbf8b47e6551daea",
            },
            {
               url: "https://git.kernel.org/stable/c/80d47f5de5e311cbc0d01ebb6ee684e8f4c196c6",
            },
         ],
         title: "mm: don't try to NUMA-migrate COW pages that have other uses",
         x_generator: {
            engine: "bippy-5f407fcff5a0",
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      assignerShortName: "Linux",
      cveId: "CVE-2022-48797",
      datePublished: "2024-07-16T11:43:51.547Z",
      dateReserved: "2024-07-16T11:38:08.895Z",
      dateUpdated: "2024-12-19T08:07:55.101Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2022-48797\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-07-16T12:15:04.360\",\"lastModified\":\"2024-11-21T07:34:02.710\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmm: don't try to NUMA-migrate COW pages that have other uses\\n\\nOded Gabbay reports that enabling NUMA balancing causes corruption with\\nhis Gaudi accelerator test load:\\n\\n \\\"All the details are in the bug, but the bottom line is that somehow,\\n  this patch causes corruption when the numa balancing feature is\\n  enabled AND we don't use process affinity AND we use GUP to pin pages\\n  so our accelerator can DMA to/from system memory.\\n\\n  Either disabling numa balancing, using process affinity to bind to\\n  specific numa-node or reverting this patch causes the bug to\\n  disappear\\\"\\n\\nand Oded bisected the issue to commit 09854ba94c6a (\\\"mm: do_wp_page()\\nsimplification\\\").\\n\\nNow, the NUMA balancing shouldn't actually be changing the writability\\nof a page, and as such shouldn't matter for COW.  But it appears it\\ndoes.  Suspicious.\\n\\nHowever, regardless of that, the condition for enabling NUMA faults in\\nchange_pte_range() is nonsensical.  It uses \\\"page_mapcount(page)\\\" to\\ndecide if a COW page should be NUMA-protected or not, and that makes\\nabsolutely no sense.\\n\\nThe number of mappings a page has is irrelevant: not only does GUP get a\\nreference to a page as in Oded's case, but the other mappings migth be\\npaged out and the only reference to them would be in the page count.\\n\\nSince we should never try to NUMA-balance a page that we can't move\\nanyway due to other references, just fix the code to use 'page_count()'.\\nOded confirms that that fixes his issue.\\n\\nNow, this does imply that something in NUMA balancing ends up changing\\npage protections (other than the obvious one of making the page\\ninaccessible to get the NUMA faulting information).  Otherwise the COW\\nsimplification wouldn't matter - since doing the GUP on the page would\\nmake sure it's writable.\\n\\nThe cause of that permission change would be good to figure out too,\\nsince it clearly results in spurious COW events - but fixing the\\nnonsensical test that just happened to work before is obviously the\\nCorrectThing(tm) to do regardless.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: mm: no intente migrar páginas COW con NUMA que tengan otros usos Oded Gabbay informa que habilitar el equilibrio de NUMA causa corrupción en la carga de prueba del acelerador Gaudí: \\\"Todos los detalles están en el error, pero la conclusión es que de alguna manera, este parche causa corrupción cuando la función de equilibrio numa está habilitada Y no usamos la afinidad de procesos Y usamos GUP para anclar páginas para que nuestro acelerador pueda DMA hacia/desde la memoria del sistema, ya sea deshabilitando. El equilibrio de numa, el uso de la afinidad del proceso para vincularse a un nodo numa específico o revertir este parche hace que el error desaparezca\\\" y Oded dividió el problema en dos para el commit 09854ba94c6a (\\\"mm: simplificación de do_wp_page()\\\"). Ahora bien, el equilibrio NUMA en realidad no debería cambiar la capacidad de escritura de una página y, como tal, no debería importarle a COW. Pero parece que sí. Sospechoso. Sin embargo, independientemente de eso, la condición para habilitar fallas NUMA en change_pte_range() no tiene sentido. Utiliza \\\"page_mapcount(page)\\\" para decidir si una página COW debe estar protegida por NUMA o no, y eso no tiene ningún sentido. El número de asignaciones que tiene una página es irrelevante: GUP no solo obtiene una referencia a una página como en el caso de Oded, sino que las otras asignaciones podrían eliminarse y la única referencia a ellas estaría en el recuento de páginas. Dado que nunca debemos intentar equilibrar NUMA una página que no podemos mover de todos modos debido a otras referencias, simplemente corrija el código para usar 'page_count()'. Oded confirma que eso soluciona su problema. Ahora bien, esto implica que algo en el equilibrio de NUMA termina cambiando las protecciones de la página (aparte de la obvia de hacer que la página sea inaccesible para obtener la información de fallas de NUMA). De lo contrario, la simplificación de COW no importaría, ya que hacer el GUP en la página garantizaría que se pueda escribir. También sería bueno descubrir la causa de ese cambio de permiso, ya que claramente da como resultado eventos COW falsos, pero arreglar la prueba sin sentido que funcionó antes es obviamente lo CorrectThing(tm) que se debe hacer de todos modos.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/254090925e16abd914c87b4ad1b489440d89c4c3\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/80d47f5de5e311cbc0d01ebb6ee684e8f4c196c6\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/b3dc4b9d3ca68b370c4aeab5355007eedf948849\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/d187eeb02d18446e5e54ed6bcbf8b47e6551daea\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/254090925e16abd914c87b4ad1b489440d89c4c3\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://git.kernel.org/stable/c/80d47f5de5e311cbc0d01ebb6ee684e8f4c196c6\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://git.kernel.org/stable/c/b3dc4b9d3ca68b370c4aeab5355007eedf948849\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://git.kernel.org/stable/c/d187eeb02d18446e5e54ed6bcbf8b47e6551daea\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}",
      vulnrichment: {
         containers: "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"https://git.kernel.org/stable/c/254090925e16abd914c87b4ad1b489440d89c4c3\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/b3dc4b9d3ca68b370c4aeab5355007eedf948849\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/d187eeb02d18446e5e54ed6bcbf8b47e6551daea\", \"tags\": [\"x_transferred\"]}, {\"url\": \"https://git.kernel.org/stable/c/80d47f5de5e311cbc0d01ebb6ee684e8f4c196c6\", \"tags\": [\"x_transferred\"]}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2024-08-03T15:25:01.608Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2022-48797\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-09-10T16:59:16.178583Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-09-11T12:42:21.578Z\"}}], \"cna\": {\"title\": \"mm: don't try to NUMA-migrate COW pages that have other uses\", \"affected\": [{\"repo\": \"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git\", \"vendor\": \"Linux\", \"product\": \"Linux\", \"versions\": [{\"status\": \"affected\", \"version\": \"09854ba94c6aad7886996bfbee2530b3d8a7f4f4\", \"lessThan\": \"254090925e16abd914c87b4ad1b489440d89c4c3\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"09854ba94c6aad7886996bfbee2530b3d8a7f4f4\", \"lessThan\": \"b3dc4b9d3ca68b370c4aeab5355007eedf948849\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"09854ba94c6aad7886996bfbee2530b3d8a7f4f4\", \"lessThan\": \"d187eeb02d18446e5e54ed6bcbf8b47e6551daea\", \"versionType\": \"git\"}, {\"status\": \"affected\", \"version\": \"09854ba94c6aad7886996bfbee2530b3d8a7f4f4\", \"lessThan\": \"80d47f5de5e311cbc0d01ebb6ee684e8f4c196c6\", \"versionType\": \"git\"}], \"programFiles\": [\"mm/mprotect.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.9\"}, {\"status\": \"unaffected\", \"version\": \"0\", \"lessThan\": \"5.9\", \"versionType\": \"semver\"}, {\"status\": \"unaffected\", \"version\": \"5.10.102\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.10.*\"}, {\"status\": \"unaffected\", \"version\": \"5.15.25\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.15.*\"}, {\"status\": \"unaffected\", \"version\": \"5.16.11\", \"versionType\": \"semver\", \"lessThanOrEqual\": \"5.16.*\"}, {\"status\": \"unaffected\", \"version\": \"5.17\", \"versionType\": \"original_commit_for_fix\", \"lessThanOrEqual\": \"*\"}], \"programFiles\": [\"mm/mprotect.c\"], \"defaultStatus\": \"affected\"}], \"references\": [{\"url\": \"https://git.kernel.org/stable/c/254090925e16abd914c87b4ad1b489440d89c4c3\"}, {\"url\": \"https://git.kernel.org/stable/c/b3dc4b9d3ca68b370c4aeab5355007eedf948849\"}, {\"url\": \"https://git.kernel.org/stable/c/d187eeb02d18446e5e54ed6bcbf8b47e6551daea\"}, {\"url\": \"https://git.kernel.org/stable/c/80d47f5de5e311cbc0d01ebb6ee684e8f4c196c6\"}], \"x_generator\": {\"engine\": \"bippy-5f407fcff5a0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\nmm: don't try to NUMA-migrate COW pages that have other uses\\n\\nOded Gabbay reports that enabling NUMA balancing causes corruption with\\nhis Gaudi accelerator test load:\\n\\n \\\"All the details are in the bug, but the bottom line is that somehow,\\n  this patch causes corruption when the numa balancing feature is\\n  enabled AND we don't use process affinity AND we use GUP to pin pages\\n  so our accelerator can DMA to/from system memory.\\n\\n  Either disabling numa balancing, using process affinity to bind to\\n  specific numa-node or reverting this patch causes the bug to\\n  disappear\\\"\\n\\nand Oded bisected the issue to commit 09854ba94c6a (\\\"mm: do_wp_page()\\nsimplification\\\").\\n\\nNow, the NUMA balancing shouldn't actually be changing the writability\\nof a page, and as such shouldn't matter for COW.  But it appears it\\ndoes.  Suspicious.\\n\\nHowever, regardless of that, the condition for enabling NUMA faults in\\nchange_pte_range() is nonsensical.  It uses \\\"page_mapcount(page)\\\" to\\ndecide if a COW page should be NUMA-protected or not, and that makes\\nabsolutely no sense.\\n\\nThe number of mappings a page has is irrelevant: not only does GUP get a\\nreference to a page as in Oded's case, but the other mappings migth be\\npaged out and the only reference to them would be in the page count.\\n\\nSince we should never try to NUMA-balance a page that we can't move\\nanyway due to other references, just fix the code to use 'page_count()'.\\nOded confirms that that fixes his issue.\\n\\nNow, this does imply that something in NUMA balancing ends up changing\\npage protections (other than the obvious one of making the page\\ninaccessible to get the NUMA faulting information).  Otherwise the COW\\nsimplification wouldn't matter - since doing the GUP on the page would\\nmake sure it's writable.\\n\\nThe cause of that permission change would be good to figure out too,\\nsince it clearly results in spurious COW events - but fixing the\\nnonsensical test that just happened to work before is obviously the\\nCorrectThing(tm) to do regardless.\"}], \"providerMetadata\": {\"orgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"shortName\": \"Linux\", \"dateUpdated\": \"2024-12-19T08:07:55.101Z\"}}}",
         cveMetadata: "{\"cveId\": \"CVE-2022-48797\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-12-19T08:07:55.101Z\", \"dateReserved\": \"2024-07-16T11:38:08.895Z\", \"assignerOrgId\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\", \"datePublished\": \"2024-07-16T11:43:51.547Z\", \"assignerShortName\": \"Linux\"}",
         dataType: "CVE_RECORD",
         dataVersion: "5.1",
      },
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



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.