Action not permitted
Modal body text goes here.
CVE-2024-26670
Vulnerability from cvelistv5
{ "containers": { "adp": [ { "metrics": [ { "other": { "content": { "id": "CVE-2024-26670", "options": [ { "Exploitation": "none" }, { "Automatable": "no" }, { "Technical Impact": "partial" } ], "role": "CISA Coordinator", "timestamp": "2024-06-17T19:31:09.790216Z", "version": "2.0.3" }, "type": "ssvc" } } ], "providerMetadata": { "dateUpdated": "2024-06-17T19:31:17.652Z", "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP" }, "title": "CISA ADP Vulnrichment" }, { "providerMetadata": { "dateUpdated": "2024-08-02T00:14:12.513Z", "orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE" }, "references": [ { "tags": [ "x_transferred" ], "url": "https://git.kernel.org/stable/c/58eb5c07f41704464b9acc09ab0707b6769db6c0" }, { "tags": [ "x_transferred" ], "url": "https://git.kernel.org/stable/c/baa0aaac16432019651e0d60c41cd34a0c3c3477" }, { "tags": [ "x_transferred" ], "url": "https://git.kernel.org/stable/c/832dd634bd1b4e3bbe9f10b9c9ba5db6f6f2b97f" } ], "title": "CVE Program Container" } ], "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Linux", "programFiles": [ "arch/arm64/kernel/entry.S" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "lessThan": "58eb5c07f417", "status": "affected", "version": "471470bc7052", "versionType": "git" }, { "lessThan": "baa0aaac1643", "status": "affected", "version": "471470bc7052", "versionType": "git" }, { "lessThan": "832dd634bd1b", "status": "affected", "version": "471470bc7052", "versionType": "git" } ] }, { "defaultStatus": "affected", "product": "Linux", "programFiles": [ "arch/arm64/kernel/entry.S" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "status": "affected", "version": "6.6" }, { "lessThan": "6.6", "status": "unaffected", "version": "0", "versionType": "custom" }, { "lessThanOrEqual": "6.6.*", "status": "unaffected", "version": "6.6.15", "versionType": "custom" }, { "lessThanOrEqual": "6.7.*", "status": "unaffected", "version": "6.7.3", "versionType": "custom" }, { "lessThanOrEqual": "*", "status": "unaffected", "version": "6.8", "versionType": "original_commit_for_fix" } ] } ], "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n\nCurrently the ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround isn\u0027t\nquite right, as it is supposed to be applied after the last explicit\nmemory access, but is immediately followed by an LDR.\n\nThe ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround is used to\nhandle Cortex-A520 erratum 2966298 and Cortex-A510 erratum 3117295,\nwhich are described in:\n\n* https://developer.arm.com/documentation/SDEN2444153/0600/?lang=en\n* https://developer.arm.com/documentation/SDEN1873361/1600/?lang=en\n\nIn both cases the workaround is described as:\n\n| If pagetable isolation is disabled, the context switch logic in the\n| kernel can be updated to execute the following sequence on affected\n| cores before exiting to EL0, and after all explicit memory accesses:\n|\n| 1. A non-shareable TLBI to any context and/or address, including\n| unused contexts or addresses, such as a `TLBI VALE1 Xzr`.\n|\n| 2. A DSB NSH to guarantee completion of the TLBI.\n\nThe important part being that the TLBI+DSB must be placed \"after all\nexplicit memory accesses\".\n\nUnfortunately, as-implemented, the TLBI+DSB is immediately followed by\nan LDR, as we have:\n\n| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n| \ttlbi\tvale1, xzr\n| \tdsb\tnsh\n| alternative_else_nop_endif\n| alternative_if_not ARM64_UNMAP_KERNEL_AT_EL0\n| \tldr\tlr, [sp, #S_LR]\n| \tadd\tsp, sp, #PT_REGS_SIZE\t\t// restore sp\n| \teret\n| alternative_else_nop_endif\n|\n| [ ... KPTI exception return path ... ]\n\nThis patch fixes this by reworking the logic to place the TLBI+DSB\nimmediately before the ERET, after all explicit memory accesses.\n\nThe ERET is currently in a separate alternative block, and alternatives\ncannot be nested. To account for this, the alternative block for\nARM64_UNMAP_KERNEL_AT_EL0 is replaced with a single alternative branch\nto skip the KPTI logic, with the new shape of the logic being:\n\n| alternative_insn \"b .L_skip_tramp_exit_\\@\", nop, ARM64_UNMAP_KERNEL_AT_EL0\n| \t[ ... KPTI exception return path ... ]\n| .L_skip_tramp_exit_\\@:\n|\n| \tldr\tlr, [sp, #S_LR]\n| \tadd\tsp, sp, #PT_REGS_SIZE\t\t// restore sp\n|\n| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n| \ttlbi\tvale1, xzr\n| \tdsb\tnsh\n| alternative_else_nop_endif\n| \teret\n\nThe new structure means that the workaround is only applied when KPTI is\nnot in use; this is fine as noted in the documented implications of the\nerratum:\n\n| Pagetable isolation between EL0 and higher level ELs prevents the\n| issue from occurring.\n\n... and as per the workaround description quoted above, the workaround\nis only necessary \"If pagetable isolation is disabled\"." } ], "providerMetadata": { "dateUpdated": "2024-05-29T05:20:32.990Z", "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux" }, "references": [ { "url": "https://git.kernel.org/stable/c/58eb5c07f41704464b9acc09ab0707b6769db6c0" }, { "url": "https://git.kernel.org/stable/c/baa0aaac16432019651e0d60c41cd34a0c3c3477" }, { "url": "https://git.kernel.org/stable/c/832dd634bd1b4e3bbe9f10b9c9ba5db6f6f2b97f" } ], "title": "arm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD", "x_generator": { "engine": "bippy-a5840b7849dd" } } }, "cveMetadata": { "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "assignerShortName": "Linux", "cveId": "CVE-2024-26670", "datePublished": "2024-04-02T06:43:31.201Z", "dateReserved": "2024-02-19T14:20:24.150Z", "dateUpdated": "2024-08-02T00:14:12.513Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2024-26670\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-04-02T07:15:43.760\",\"lastModified\":\"2024-04-02T12:50:42.233\",\"vulnStatus\":\"Awaiting Analysis\",\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\narm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\\n\\nCurrently the ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround isn\u0027t\\nquite right, as it is supposed to be applied after the last explicit\\nmemory access, but is immediately followed by an LDR.\\n\\nThe ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround is used to\\nhandle Cortex-A520 erratum 2966298 and Cortex-A510 erratum 3117295,\\nwhich are described in:\\n\\n* https://developer.arm.com/documentation/SDEN2444153/0600/?lang=en\\n* https://developer.arm.com/documentation/SDEN1873361/1600/?lang=en\\n\\nIn both cases the workaround is described as:\\n\\n| If pagetable isolation is disabled, the context switch logic in the\\n| kernel can be updated to execute the following sequence on affected\\n| cores before exiting to EL0, and after all explicit memory accesses:\\n|\\n| 1. A non-shareable TLBI to any context and/or address, including\\n| unused contexts or addresses, such as a `TLBI VALE1 Xzr`.\\n|\\n| 2. A DSB NSH to guarantee completion of the TLBI.\\n\\nThe important part being that the TLBI+DSB must be placed \\\"after all\\nexplicit memory accesses\\\".\\n\\nUnfortunately, as-implemented, the TLBI+DSB is immediately followed by\\nan LDR, as we have:\\n\\n| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\\n| \\ttlbi\\tvale1, xzr\\n| \\tdsb\\tnsh\\n| alternative_else_nop_endif\\n| alternative_if_not ARM64_UNMAP_KERNEL_AT_EL0\\n| \\tldr\\tlr, [sp, #S_LR]\\n| \\tadd\\tsp, sp, #PT_REGS_SIZE\\t\\t// restore sp\\n| \\teret\\n| alternative_else_nop_endif\\n|\\n| [ ... KPTI exception return path ... ]\\n\\nThis patch fixes this by reworking the logic to place the TLBI+DSB\\nimmediately before the ERET, after all explicit memory accesses.\\n\\nThe ERET is currently in a separate alternative block, and alternatives\\ncannot be nested. To account for this, the alternative block for\\nARM64_UNMAP_KERNEL_AT_EL0 is replaced with a single alternative branch\\nto skip the KPTI logic, with the new shape of the logic being:\\n\\n| alternative_insn \\\"b .L_skip_tramp_exit_\\\\@\\\", nop, ARM64_UNMAP_KERNEL_AT_EL0\\n| \\t[ ... KPTI exception return path ... ]\\n| .L_skip_tramp_exit_\\\\@:\\n|\\n| \\tldr\\tlr, [sp, #S_LR]\\n| \\tadd\\tsp, sp, #PT_REGS_SIZE\\t\\t// restore sp\\n|\\n| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\\n| \\ttlbi\\tvale1, xzr\\n| \\tdsb\\tnsh\\n| alternative_else_nop_endif\\n| \\teret\\n\\nThe new structure means that the workaround is only applied when KPTI is\\nnot in use; this is fine as noted in the documented implications of the\\nerratum:\\n\\n| Pagetable isolation between EL0 and higher level ELs prevents the\\n| issue from occurring.\\n\\n... and as per the workaround description quoted above, the workaround\\nis only necessary \\\"If pagetable isolation is disabled\\\".\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: arm64: entrada: arreglar ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD Actualmente, la soluci\u00f3n alternativa ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD no es del todo correcta, ya que se supone que debe aplicarse despu\u00e9s del \u00faltimo acceso expl\u00edcito a la memoria, pero va seguida inmediatamente por un LDR. La soluci\u00f3n alternativa ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD se utiliza para manejar las erratas Cortex-A520 2966298 y Cortex-A510 erratas 3117295, que se describen en: * https://developer.arm.com/documentation/SDEN2444153/0600/?lang=en * https:// desarrollador.arm.com/documentation/SDEN1873361/1600/?lang=en En ambos casos, la soluci\u00f3n se describe como: | Si el aislamiento de la tabla de p\u00e1ginas est\u00e1 deshabilitado, la l\u00f3gica de cambio de contexto en | El kernel se puede actualizar para ejecutar la siguiente secuencia en los afectados | n\u00facleos antes de salir a EL0 y despu\u00e9s de todos los accesos expl\u00edcitos a la memoria: | | 1. Un TLBI que no se puede compartir en cualquier contexto y/o direcci\u00f3n, incluido | contextos o direcciones no utilizados, como `TLBI VALE1 Xzr`. | | 2. Un OSD NSH para garantizar la finalizaci\u00f3n del TLBI. La parte importante es que el TLBI+DSB debe colocarse \\\"despu\u00e9s de todos los accesos expl\u00edcitos a la memoria\\\". Desafortunadamente, tal como se implement\u00f3, el TLBI+DSB es seguido inmediatamente por un LDR, como tenemos: | Alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD | tlbi vale1, xzr | dsb nsh | alternativa_else_nop_endif | alternativa_si_no ARM64_UNMAP_KERNEL_AT_EL0 | ldr lr, [sp, #S_LR] | agregar sp, sp, #PT_REGS_SIZE // restaurar sp | eremita | alternativa_else_nop_endif | | [... Ruta de retorno de excepci\u00f3n KPTI...] Este parche soluciona este problema reelaborando la l\u00f3gica para colocar TLBI+DSB inmediatamente antes de ERET, despu\u00e9s de todos los accesos expl\u00edcitos a la memoria. El ERET se encuentra actualmente en un bloque alternativo separado y las alternativas no se pueden anidar. Para tener en cuenta esto, el bloque alternativo para ARM64_UNMAP_KERNEL_AT_EL0 se reemplaza con una \u00fanica rama alternativa para omitir la l\u00f3gica KPTI, siendo la nueva forma de la l\u00f3gica: | Alternative_insn \\\"b .L_skip_tramp_exit_\\\\@\\\", nop, ARM64_UNMAP_KERNEL_AT_EL0 | [... Ruta de retorno de excepci\u00f3n KPTI...] | .L_skip_tramp_exit_\\\\@: | | ldr lr, [sp, #S_LR] | agregar sp, sp, #PT_REGS_SIZE // restaurar sp | | Alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD | tlbi vale1, xzr | dsb nsh | alternativa_else_nop_endif | eret La nueva estructura significa que la soluci\u00f3n alternativa s\u00f3lo se aplica cuando KPTI no est\u00e1 en uso; esto est\u00e1 bien, como se indica en las implicaciones documentadas de la fe de erratas: | El aislamiento de la tabla de paginaci\u00f3n entre EL0 y los EL de nivel superior evita que | que ocurra el problema. ... y seg\u00fan la descripci\u00f3n de la soluci\u00f3n citada anteriormente, la soluci\u00f3n s\u00f3lo es necesaria \\\"si el aislamiento de la tabla de p\u00e1ginas est\u00e1 deshabilitado\\\".\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/58eb5c07f41704464b9acc09ab0707b6769db6c0\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/832dd634bd1b4e3bbe9f10b9c9ba5db6f6f2b97f\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/baa0aaac16432019651e0d60c41cd34a0c3c3477\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}" } }
gsd-2024-26670
Vulnerability from gsd
{ "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "aliases": [ "CVE-2024-26670" ], "details": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n\nCurrently the ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround isn\u0027t\nquite right, as it is supposed to be applied after the last explicit\nmemory access, but is immediately followed by an LDR.\n\nThe ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround is used to\nhandle Cortex-A520 erratum 2966298 and Cortex-A510 erratum 3117295,\nwhich are described in:\n\n* https://developer.arm.com/documentation/SDEN2444153/0600/?lang=en\n* https://developer.arm.com/documentation/SDEN1873361/1600/?lang=en\n\nIn both cases the workaround is described as:\n\n| If pagetable isolation is disabled, the context switch logic in the\n| kernel can be updated to execute the following sequence on affected\n| cores before exiting to EL0, and after all explicit memory accesses:\n|\n| 1. A non-shareable TLBI to any context and/or address, including\n| unused contexts or addresses, such as a `TLBI VALE1 Xzr`.\n|\n| 2. A DSB NSH to guarantee completion of the TLBI.\n\nThe important part being that the TLBI+DSB must be placed \"after all\nexplicit memory accesses\".\n\nUnfortunately, as-implemented, the TLBI+DSB is immediately followed by\nan LDR, as we have:\n\n| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n| \ttlbi\tvale1, xzr\n| \tdsb\tnsh\n| alternative_else_nop_endif\n| alternative_if_not ARM64_UNMAP_KERNEL_AT_EL0\n| \tldr\tlr, [sp, #S_LR]\n| \tadd\tsp, sp, #PT_REGS_SIZE\t\t// restore sp\n| \teret\n| alternative_else_nop_endif\n|\n| [ ... KPTI exception return path ... ]\n\nThis patch fixes this by reworking the logic to place the TLBI+DSB\nimmediately before the ERET, after all explicit memory accesses.\n\nThe ERET is currently in a separate alternative block, and alternatives\ncannot be nested. To account for this, the alternative block for\nARM64_UNMAP_KERNEL_AT_EL0 is replaced with a single alternative branch\nto skip the KPTI logic, with the new shape of the logic being:\n\n| alternative_insn \"b .L_skip_tramp_exit_\\@\", nop, ARM64_UNMAP_KERNEL_AT_EL0\n| \t[ ... KPTI exception return path ... ]\n| .L_skip_tramp_exit_\\@:\n|\n| \tldr\tlr, [sp, #S_LR]\n| \tadd\tsp, sp, #PT_REGS_SIZE\t\t// restore sp\n|\n| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n| \ttlbi\tvale1, xzr\n| \tdsb\tnsh\n| alternative_else_nop_endif\n| \teret\n\nThe new structure means that the workaround is only applied when KPTI is\nnot in use; this is fine as noted in the documented implications of the\nerratum:\n\n| Pagetable isolation between EL0 and higher level ELs prevents the\n| issue from occurring.\n\n... and as per the workaround description quoted above, the workaround\nis only necessary \"If pagetable isolation is disabled\".", "id": "GSD-2024-26670", "modified": "2024-02-20T06:02:29.146023Z", "schema_version": "1.4.0" } }, "namespaces": { "cve.org": { "CVE_data_meta": { "ASSIGNER": "cve@kernel.org", "ID": "CVE-2024-26670", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "Linux", "version": { "version_data": [ { "version_affected": "\u003c", "version_name": "471470bc7052", "version_value": "58eb5c07f417" }, { "version_value": "not down converted", "x_cve_json_5_version_data": { "defaultStatus": "affected", "versions": [ { "status": "affected", "version": "6.6" }, { "lessThan": "6.6", "status": "unaffected", "version": "0", "versionType": "custom" }, { "lessThanOrEqual": "6.6.*", "status": "unaffected", "version": "6.6.15", "versionType": "custom" }, { "lessThanOrEqual": "6.7.*", "status": "unaffected", "version": "6.7.3", "versionType": "custom" }, { "lessThanOrEqual": "*", "status": "unaffected", "version": "6.8", "versionType": "original_commit_for_fix" } ] } } ] } } ] }, "vendor_name": "Linux" } ] } }, "data_format": "MITRE", "data_type": "CVE", "data_version": "4.0", "description": { "description_data": [ { "lang": "eng", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n\nCurrently the ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround isn\u0027t\nquite right, as it is supposed to be applied after the last explicit\nmemory access, but is immediately followed by an LDR.\n\nThe ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround is used to\nhandle Cortex-A520 erratum 2966298 and Cortex-A510 erratum 3117295,\nwhich are described in:\n\n* https://developer.arm.com/documentation/SDEN2444153/0600/?lang=en\n* https://developer.arm.com/documentation/SDEN1873361/1600/?lang=en\n\nIn both cases the workaround is described as:\n\n| If pagetable isolation is disabled, the context switch logic in the\n| kernel can be updated to execute the following sequence on affected\n| cores before exiting to EL0, and after all explicit memory accesses:\n|\n| 1. A non-shareable TLBI to any context and/or address, including\n| unused contexts or addresses, such as a `TLBI VALE1 Xzr`.\n|\n| 2. A DSB NSH to guarantee completion of the TLBI.\n\nThe important part being that the TLBI+DSB must be placed \"after all\nexplicit memory accesses\".\n\nUnfortunately, as-implemented, the TLBI+DSB is immediately followed by\nan LDR, as we have:\n\n| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n| \ttlbi\tvale1, xzr\n| \tdsb\tnsh\n| alternative_else_nop_endif\n| alternative_if_not ARM64_UNMAP_KERNEL_AT_EL0\n| \tldr\tlr, [sp, #S_LR]\n| \tadd\tsp, sp, #PT_REGS_SIZE\t\t// restore sp\n| \teret\n| alternative_else_nop_endif\n|\n| [ ... KPTI exception return path ... ]\n\nThis patch fixes this by reworking the logic to place the TLBI+DSB\nimmediately before the ERET, after all explicit memory accesses.\n\nThe ERET is currently in a separate alternative block, and alternatives\ncannot be nested. To account for this, the alternative block for\nARM64_UNMAP_KERNEL_AT_EL0 is replaced with a single alternative branch\nto skip the KPTI logic, with the new shape of the logic being:\n\n| alternative_insn \"b .L_skip_tramp_exit_\\@\", nop, ARM64_UNMAP_KERNEL_AT_EL0\n| \t[ ... KPTI exception return path ... ]\n| .L_skip_tramp_exit_\\@:\n|\n| \tldr\tlr, [sp, #S_LR]\n| \tadd\tsp, sp, #PT_REGS_SIZE\t\t// restore sp\n|\n| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n| \ttlbi\tvale1, xzr\n| \tdsb\tnsh\n| alternative_else_nop_endif\n| \teret\n\nThe new structure means that the workaround is only applied when KPTI is\nnot in use; this is fine as noted in the documented implications of the\nerratum:\n\n| Pagetable isolation between EL0 and higher level ELs prevents the\n| issue from occurring.\n\n... and as per the workaround description quoted above, the workaround\nis only necessary \"If pagetable isolation is disabled\"." } ] }, "generator": { "engine": "bippy-b4257b672505" }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "n/a" } ] } ] }, "references": { "reference_data": [ { "name": "https://git.kernel.org/stable/c/58eb5c07f41704464b9acc09ab0707b6769db6c0", "refsource": "MISC", "url": "https://git.kernel.org/stable/c/58eb5c07f41704464b9acc09ab0707b6769db6c0" }, { "name": "https://git.kernel.org/stable/c/baa0aaac16432019651e0d60c41cd34a0c3c3477", "refsource": "MISC", "url": "https://git.kernel.org/stable/c/baa0aaac16432019651e0d60c41cd34a0c3c3477" }, { "name": "https://git.kernel.org/stable/c/832dd634bd1b4e3bbe9f10b9c9ba5db6f6f2b97f", "refsource": "MISC", "url": "https://git.kernel.org/stable/c/832dd634bd1b4e3bbe9f10b9c9ba5db6f6f2b97f" } ] } }, "nvd.nist.gov": { "cve": { "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n\nCurrently the ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround isn\u0027t\nquite right, as it is supposed to be applied after the last explicit\nmemory access, but is immediately followed by an LDR.\n\nThe ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround is used to\nhandle Cortex-A520 erratum 2966298 and Cortex-A510 erratum 3117295,\nwhich are described in:\n\n* https://developer.arm.com/documentation/SDEN2444153/0600/?lang=en\n* https://developer.arm.com/documentation/SDEN1873361/1600/?lang=en\n\nIn both cases the workaround is described as:\n\n| If pagetable isolation is disabled, the context switch logic in the\n| kernel can be updated to execute the following sequence on affected\n| cores before exiting to EL0, and after all explicit memory accesses:\n|\n| 1. A non-shareable TLBI to any context and/or address, including\n| unused contexts or addresses, such as a `TLBI VALE1 Xzr`.\n|\n| 2. A DSB NSH to guarantee completion of the TLBI.\n\nThe important part being that the TLBI+DSB must be placed \"after all\nexplicit memory accesses\".\n\nUnfortunately, as-implemented, the TLBI+DSB is immediately followed by\nan LDR, as we have:\n\n| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n| \ttlbi\tvale1, xzr\n| \tdsb\tnsh\n| alternative_else_nop_endif\n| alternative_if_not ARM64_UNMAP_KERNEL_AT_EL0\n| \tldr\tlr, [sp, #S_LR]\n| \tadd\tsp, sp, #PT_REGS_SIZE\t\t// restore sp\n| \teret\n| alternative_else_nop_endif\n|\n| [ ... KPTI exception return path ... ]\n\nThis patch fixes this by reworking the logic to place the TLBI+DSB\nimmediately before the ERET, after all explicit memory accesses.\n\nThe ERET is currently in a separate alternative block, and alternatives\ncannot be nested. To account for this, the alternative block for\nARM64_UNMAP_KERNEL_AT_EL0 is replaced with a single alternative branch\nto skip the KPTI logic, with the new shape of the logic being:\n\n| alternative_insn \"b .L_skip_tramp_exit_\\@\", nop, ARM64_UNMAP_KERNEL_AT_EL0\n| \t[ ... KPTI exception return path ... ]\n| .L_skip_tramp_exit_\\@:\n|\n| \tldr\tlr, [sp, #S_LR]\n| \tadd\tsp, sp, #PT_REGS_SIZE\t\t// restore sp\n|\n| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n| \ttlbi\tvale1, xzr\n| \tdsb\tnsh\n| alternative_else_nop_endif\n| \teret\n\nThe new structure means that the workaround is only applied when KPTI is\nnot in use; this is fine as noted in the documented implications of the\nerratum:\n\n| Pagetable isolation between EL0 and higher level ELs prevents the\n| issue from occurring.\n\n... and as per the workaround description quoted above, the workaround\nis only necessary \"If pagetable isolation is disabled\"." }, { "lang": "es", "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: arm64: entrada: arreglar ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD Actualmente, la soluci\u00f3n alternativa ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD no es del todo correcta, ya que se supone que debe aplicarse despu\u00e9s del \u00faltimo acceso expl\u00edcito a la memoria, pero va seguida inmediatamente por un LDR. La soluci\u00f3n alternativa ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD se utiliza para manejar las erratas Cortex-A520 2966298 y Cortex-A510 erratas 3117295, que se describen en: * https://developer.arm.com/documentation/SDEN2444153/0600/?lang=en * https:// desarrollador.arm.com/documentation/SDEN1873361/1600/?lang=en En ambos casos, la soluci\u00f3n se describe como: | Si el aislamiento de la tabla de p\u00e1ginas est\u00e1 deshabilitado, la l\u00f3gica de cambio de contexto en | El kernel se puede actualizar para ejecutar la siguiente secuencia en los afectados | n\u00facleos antes de salir a EL0 y despu\u00e9s de todos los accesos expl\u00edcitos a la memoria: | | 1. Un TLBI que no se puede compartir en cualquier contexto y/o direcci\u00f3n, incluido | contextos o direcciones no utilizados, como `TLBI VALE1 Xzr`. | | 2. Un OSD NSH para garantizar la finalizaci\u00f3n del TLBI. La parte importante es que el TLBI+DSB debe colocarse \"despu\u00e9s de todos los accesos expl\u00edcitos a la memoria\". Desafortunadamente, tal como se implement\u00f3, el TLBI+DSB es seguido inmediatamente por un LDR, como tenemos: | Alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD | tlbi vale1, xzr | dsb nsh | alternativa_else_nop_endif | alternativa_si_no ARM64_UNMAP_KERNEL_AT_EL0 | ldr lr, [sp, #S_LR] | agregar sp, sp, #PT_REGS_SIZE // restaurar sp | eremita | alternativa_else_nop_endif | | [... Ruta de retorno de excepci\u00f3n KPTI...] Este parche soluciona este problema reelaborando la l\u00f3gica para colocar TLBI+DSB inmediatamente antes de ERET, despu\u00e9s de todos los accesos expl\u00edcitos a la memoria. El ERET se encuentra actualmente en un bloque alternativo separado y las alternativas no se pueden anidar. Para tener en cuenta esto, el bloque alternativo para ARM64_UNMAP_KERNEL_AT_EL0 se reemplaza con una \u00fanica rama alternativa para omitir la l\u00f3gica KPTI, siendo la nueva forma de la l\u00f3gica: | Alternative_insn \"b .L_skip_tramp_exit_\\@\", nop, ARM64_UNMAP_KERNEL_AT_EL0 | [... Ruta de retorno de excepci\u00f3n KPTI...] | .L_skip_tramp_exit_\\@: | | ldr lr, [sp, #S_LR] | agregar sp, sp, #PT_REGS_SIZE // restaurar sp | | Alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD | tlbi vale1, xzr | dsb nsh | alternativa_else_nop_endif | eret La nueva estructura significa que la soluci\u00f3n alternativa s\u00f3lo se aplica cuando KPTI no est\u00e1 en uso; esto est\u00e1 bien, como se indica en las implicaciones documentadas de la fe de erratas: | El aislamiento de la tabla de paginaci\u00f3n entre EL0 y los EL de nivel superior evita que | que ocurra el problema. ... y seg\u00fan la descripci\u00f3n de la soluci\u00f3n citada anteriormente, la soluci\u00f3n s\u00f3lo es necesaria \"si el aislamiento de la tabla de p\u00e1ginas est\u00e1 deshabilitado\"." } ], "id": "CVE-2024-26670", "lastModified": "2024-04-02T12:50:42.233", "metrics": {}, "published": "2024-04-02T07:15:43.760", "references": [ { "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/58eb5c07f41704464b9acc09ab0707b6769db6c0" }, { "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/832dd634bd1b4e3bbe9f10b9c9ba5db6f6f2b97f" }, { "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/baa0aaac16432019651e0d60c41cd34a0c3c3477" } ], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Awaiting Analysis" } } } }
ghsa-vpp3-8c88-m6w7
Vulnerability from github
In the Linux kernel, the following vulnerability has been resolved:
arm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD
Currently the ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround isn't quite right, as it is supposed to be applied after the last explicit memory access, but is immediately followed by an LDR.
The ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround is used to handle Cortex-A520 erratum 2966298 and Cortex-A510 erratum 3117295, which are described in:
- https://developer.arm.com/documentation/SDEN2444153/0600/?lang=en
- https://developer.arm.com/documentation/SDEN1873361/1600/?lang=en
In both cases the workaround is described as:
| If pagetable isolation is disabled, the context switch logic in the
| kernel can be updated to execute the following sequence on affected
| cores before exiting to EL0, and after all explicit memory accesses:
|
| 1. A non-shareable TLBI to any context and/or address, including
| unused contexts or addresses, such as a TLBI VALE1 Xzr
.
|
| 2. A DSB NSH to guarantee completion of the TLBI.
The important part being that the TLBI+DSB must be placed "after all explicit memory accesses".
Unfortunately, as-implemented, the TLBI+DSB is immediately followed by an LDR, as we have:
| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD | tlbi vale1, xzr | dsb nsh | alternative_else_nop_endif | alternative_if_not ARM64_UNMAP_KERNEL_AT_EL0 | ldr lr, [sp, #S_LR] | add sp, sp, #PT_REGS_SIZE // restore sp | eret | alternative_else_nop_endif | | [ ... KPTI exception return path ... ]
This patch fixes this by reworking the logic to place the TLBI+DSB immediately before the ERET, after all explicit memory accesses.
The ERET is currently in a separate alternative block, and alternatives cannot be nested. To account for this, the alternative block for ARM64_UNMAP_KERNEL_AT_EL0 is replaced with a single alternative branch to skip the KPTI logic, with the new shape of the logic being:
| alternative_insn "b .L_skip_tramp_exit_\@", nop, ARM64_UNMAP_KERNEL_AT_EL0 | [ ... KPTI exception return path ... ] | .L_skip_tramp_exit_\@: | | ldr lr, [sp, #S_LR] | add sp, sp, #PT_REGS_SIZE // restore sp | | alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD | tlbi vale1, xzr | dsb nsh | alternative_else_nop_endif | eret
The new structure means that the workaround is only applied when KPTI is not in use; this is fine as noted in the documented implications of the erratum:
| Pagetable isolation between EL0 and higher level ELs prevents the | issue from occurring.
... and as per the workaround description quoted above, the workaround is only necessary "If pagetable isolation is disabled".
{ "affected": [], "aliases": [ "CVE-2024-26670" ], "database_specific": { "cwe_ids": [], "github_reviewed": false, "github_reviewed_at": null, "nvd_published_at": "2024-04-02T07:15:43Z", "severity": null }, "details": "In the Linux kernel, the following vulnerability has been resolved:\n\narm64: entry: fix ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n\nCurrently the ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround isn\u0027t\nquite right, as it is supposed to be applied after the last explicit\nmemory access, but is immediately followed by an LDR.\n\nThe ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD workaround is used to\nhandle Cortex-A520 erratum 2966298 and Cortex-A510 erratum 3117295,\nwhich are described in:\n\n* https://developer.arm.com/documentation/SDEN2444153/0600/?lang=en\n* https://developer.arm.com/documentation/SDEN1873361/1600/?lang=en\n\nIn both cases the workaround is described as:\n\n| If pagetable isolation is disabled, the context switch logic in the\n| kernel can be updated to execute the following sequence on affected\n| cores before exiting to EL0, and after all explicit memory accesses:\n|\n| 1. A non-shareable TLBI to any context and/or address, including\n| unused contexts or addresses, such as a `TLBI VALE1 Xzr`.\n|\n| 2. A DSB NSH to guarantee completion of the TLBI.\n\nThe important part being that the TLBI+DSB must be placed \"after all\nexplicit memory accesses\".\n\nUnfortunately, as-implemented, the TLBI+DSB is immediately followed by\nan LDR, as we have:\n\n| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n| \ttlbi\tvale1, xzr\n| \tdsb\tnsh\n| alternative_else_nop_endif\n| alternative_if_not ARM64_UNMAP_KERNEL_AT_EL0\n| \tldr\tlr, [sp, #S_LR]\n| \tadd\tsp, sp, #PT_REGS_SIZE\t\t// restore sp\n| \teret\n| alternative_else_nop_endif\n|\n| [ ... KPTI exception return path ... ]\n\nThis patch fixes this by reworking the logic to place the TLBI+DSB\nimmediately before the ERET, after all explicit memory accesses.\n\nThe ERET is currently in a separate alternative block, and alternatives\ncannot be nested. To account for this, the alternative block for\nARM64_UNMAP_KERNEL_AT_EL0 is replaced with a single alternative branch\nto skip the KPTI logic, with the new shape of the logic being:\n\n| alternative_insn \"b .L_skip_tramp_exit_\\@\", nop, ARM64_UNMAP_KERNEL_AT_EL0\n| \t[ ... KPTI exception return path ... ]\n| .L_skip_tramp_exit_\\@:\n|\n| \tldr\tlr, [sp, #S_LR]\n| \tadd\tsp, sp, #PT_REGS_SIZE\t\t// restore sp\n|\n| alternative_if ARM64_WORKAROUND_SPECULATIVE_UNPRIV_LOAD\n| \ttlbi\tvale1, xzr\n| \tdsb\tnsh\n| alternative_else_nop_endif\n| \teret\n\nThe new structure means that the workaround is only applied when KPTI is\nnot in use; this is fine as noted in the documented implications of the\nerratum:\n\n| Pagetable isolation between EL0 and higher level ELs prevents the\n| issue from occurring.\n\n... and as per the workaround description quoted above, the workaround\nis only necessary \"If pagetable isolation is disabled\".", "id": "GHSA-vpp3-8c88-m6w7", "modified": "2024-04-02T09:30:41Z", "published": "2024-04-02T09:30:41Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-26670" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/58eb5c07f41704464b9acc09ab0707b6769db6c0" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/832dd634bd1b4e3bbe9f10b9c9ba5db6f6f2b97f" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/baa0aaac16432019651e0d60c41cd34a0c3c3477" } ], "schema_version": "1.4.0", "severity": [] }
wid-sec-w-2024-0749
Vulnerability from csaf_certbund
Notes
{ "document": { "aggregate_severity": { "text": "mittel" }, "category": "csaf_base", "csaf_version": "2.0", "distribution": { "tlp": { "label": "WHITE", "url": "https://www.first.org/tlp/" } }, "lang": "de-DE", "notes": [ { "category": "legal_disclaimer", "text": "Das BSI ist als Anbieter f\u00fcr die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch daf\u00fcr verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgf\u00e4ltig im Einzelfall zu pr\u00fcfen." }, { "category": "description", "text": "Linux ist ein verbreitetes Open Source Betriebssystem.", "title": "Produktbeschreibung" }, { "category": "summary", "text": "Ein lokaler Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren.", "title": "Angriff" }, { "category": "general", "text": "- Linux", "title": "Betroffene Betriebssysteme" } ], "publisher": { "category": "other", "contact_details": "csaf-provider@cert-bund.de", "name": "Bundesamt f\u00fcr Sicherheit in der Informationstechnik", "namespace": "https://www.bsi.bund.de" }, "references": [ { "category": "self", "summary": "WID-SEC-W-2024-0749 - CSAF Version", "url": "https://wid.cert-bund.de/.well-known/csaf/white/2024/wid-sec-w-2024-0749.json" }, { "category": "self", "summary": "WID-SEC-2024-0749 - Portal Version", "url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2024-0749" }, { "category": "external", "summary": "Kernel CVE-2023-52629 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024032949-CVE-2023-52629-a508@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2023-52630 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040219-CVE-2023-52630-a529@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2023-52631 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040222-CVE-2023-52631-ea7b@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2023-52632 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040218-CVE-2023-52632-f7bb@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2023-52633 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040218-CVE-2023-52633-d020@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2023-52634 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040219-CVE-2023-52634-27e0@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2023-52635 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040219-CVE-2023-52635-8b18@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2023-52636 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040249-CVE-2023-52636-d965@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26653 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040122-CVE-2024-26653-7903@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26654 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040142-CVE-2024-26654-aa6c@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26655 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040124-CVE-2024-26655-265a@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26656 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040247-CVE-2024-26656-ffaa@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26657 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040250-CVE-2024-26657-25a0@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26658 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040222-CVE-2024-26658-1451@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26659 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040222-CVE-2024-26659-e4f6@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26660 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040222-CVE-2024-26660-3f40@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26661 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26661-bef6@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26662 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26662-863c@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26663 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26663-9705@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26664 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040223-CVE-2024-26664-03db@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26665 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040224-CVE-2024-26665-5daa@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26666 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040224-CVE-2024-26666-fcfe@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26667 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040224-CVE-2024-26667-cf72@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26673 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040212-CVE-2024-26673-b2d3@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26668 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040235-CVE-2024-26668-636e@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26669 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040237-CVE-2024-26669-ca3c@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26670 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040238-CVE-2024-26670-ecbd@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26671 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040219-CVE-2024-26671-2543@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26672 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040219-CVE-2024-26672-e96e@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26674 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040252-CVE-2024-26674-4ff9@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26675 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040252-CVE-2024-26675-5b19@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26676 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040252-CVE-2024-26676-222f@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26677 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040252-CVE-2024-26677-8bc6@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26678 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26678-2cf0@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26679 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26679-d520@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26680 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26680-d16c@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26681 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040253-CVE-2024-26681-7e46@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26682 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040254-CVE-2024-26682-f2b2@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26683 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040254-CVE-2024-26683-8614@gregkh/" }, { "category": "external", "summary": "Kernel CVE-2024-26684 Announcement vom 2024-04-01", "url": "http://lore.kernel.org/linux-cve-announce/2024040254-CVE-2024-26684-7ce8@gregkh/" }, { "category": "external", "summary": "Fedora Security Advisory FEDORA-2024-7DD4B3B9A4 vom 2024-04-04", "url": "https://bodhi.fedoraproject.org/updates/FEDORA-2024-7dd4b3b9a4" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1322-1 vom 2024-04-17", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-April/018374.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1332-2 vom 2024-04-18", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-April/018378.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1332-1 vom 2024-04-18", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-April/018376.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1322-2 vom 2024-04-18", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-April/018377.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1466-1 vom 2024-04-29", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-April/018438.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1480-1 vom 2024-04-30", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-April/018444.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1490-1 vom 2024-05-03", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-May/018445.html" }, { "category": "external", "summary": "Debian Security Advisory DSA-5681 vom 2024-05-06", "url": "https://lists.debian.org/debian-security-announce/2024/msg00090.html" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6766-1 vom 2024-05-07", "url": "https://ubuntu.com/security/notices/USN-6766-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6765-1 vom 2024-05-07", "url": "https://ubuntu.com/security/notices/USN-6765-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6767-1 vom 2024-05-07", "url": "https://ubuntu.com/security/notices/USN-6767-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6767-2 vom 2024-05-14", "url": "https://ubuntu.com/security/notices/USN-6767-2" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1643-1 vom 2024-05-14", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-May/018529.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1644-1 vom 2024-05-14", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-May/018528.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1648-1 vom 2024-05-14", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-May/018524.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1646-1 vom 2024-05-14", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-May/018526.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1659-1 vom 2024-05-15", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-May/018538.html" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6766-2 vom 2024-05-15", "url": "https://ubuntu.com/security/notices/USN-6766-2" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6766-3 vom 2024-05-20", "url": "https://ubuntu.com/security/notices/USN-6766-3" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1648-2 vom 2024-05-21", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-May/018572.html" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:3138 vom 2024-05-22", "url": "https://access.redhat.com/errata/RHSA-2024:3138" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:2950 vom 2024-05-22", "url": "https://access.redhat.com/errata/RHSA-2024:2950" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:3306 vom 2024-05-23", "url": "https://access.redhat.com/errata/RHSA-2024:3306" }, { "category": "external", "summary": "Oracle Linux Security Advisory ELSA-2024-3306 vom 2024-05-25", "url": "https://linux.oracle.com/errata/ELSA-2024-3306.html" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6795-1 vom 2024-05-28", "url": "https://ubuntu.com/security/notices/USN-6795-1" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:3461 vom 2024-05-29", "url": "https://access.redhat.com/errata/RHSA-2024:3461" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:3460 vom 2024-05-29", "url": "https://access.redhat.com/errata/RHSA-2024:3460" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1870-1 vom 2024-05-30", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-May/018634.html" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:3618 vom 2024-06-05", "url": "https://access.redhat.com/errata/RHSA-2024:3618" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:3627 vom 2024-06-05", "url": "https://access.redhat.com/errata/RHSA-2024:3627" }, { "category": "external", "summary": "Oracle Linux Security Advisory ELSA-2024-3618 vom 2024-06-06", "url": "https://linux.oracle.com/errata/ELSA-2024-3618.html" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6816-1 vom 2024-06-08", "url": "https://ubuntu.com/security/notices/USN-6816-1" }, { "category": "external", "summary": "IBM Security Bulletin 7156774 vom 2024-06-07", "url": "https://www.ibm.com/support/pages/node/7156774" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6819-1 vom 2024-06-08", "url": "https://ubuntu.com/security/notices/USN-6819-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6820-1 vom 2024-06-08", "url": "https://ubuntu.com/security/notices/USN-6820-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6818-1 vom 2024-06-08", "url": "https://ubuntu.com/security/notices/USN-6818-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6817-1 vom 2024-06-08", "url": "https://ubuntu.com/security/notices/USN-6817-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6821-1 vom 2024-06-08", "url": "https://ubuntu.com/security/notices/USN-6821-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6818-2 vom 2024-06-10", "url": "https://ubuntu.com/security/notices/USN-6818-2" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6828-1 vom 2024-06-11", "url": "https://ubuntu.com/security/notices/USN-6828-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6820-2 vom 2024-06-11", "url": "https://ubuntu.com/security/notices/USN-6820-2" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6819-2 vom 2024-06-12", "url": "https://ubuntu.com/security/notices/USN-6819-2" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:2008-1 vom 2024-06-12", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-June/018706.html" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6819-3 vom 2024-06-12", "url": "https://ubuntu.com/security/notices/USN-6819-3" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6818-3 vom 2024-06-14", "url": "https://ubuntu.com/security/notices/USN-6818-3" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6817-3 vom 2024-06-14", "url": "https://ubuntu.com/security/notices/USN-6817-3" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6818-4 vom 2024-06-19", "url": "https://ubuntu.com/security/notices/USN-6818-4" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:2135-1 vom 2024-06-21", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-June/018783.html" }, { "category": "external", "summary": "Debian Security Advisory DLA-3842 vom 2024-06-25", "url": "https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:2190-1 vom 2024-06-25", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-June/018819.html" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6819-4 vom 2024-06-26", "url": "https://ubuntu.com/security/notices/USN-6819-4" }, { "category": "external", "summary": "Debian Security Advisory DLA-3840 vom 2024-06-27", "url": "https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4211 vom 2024-07-02", "url": "https://access.redhat.com/errata/RHSA-2024:4211" }, { "category": "external", "summary": "Dell Security Advisory DSA-2024-022 vom 2024-07-03", "url": "https://www.dell.com/support/kbdoc/de-de/000226633/dsa-2024-022-security-update-for-dell-networker-vproxy-multiple-component-vulnerabilities" }, { "category": "external", "summary": "Oracle Linux Security Advisory ELSA-2024-4211 vom 2024-07-03", "url": "https://linux.oracle.com/errata/ELSA-2024-4211.html" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6871-1 vom 2024-07-04", "url": "https://ubuntu.com/security/notices/USN-6871-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6878-1 vom 2024-07-04", "url": "https://ubuntu.com/security/notices/USN-6878-1" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4352 vom 2024-07-08", "url": "https://access.redhat.com/errata/RHSA-2024:4352" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4412 vom 2024-07-09", "url": "https://access.redhat.com/errata/RHSA-2024:4412" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4415 vom 2024-07-09", "url": "https://access.redhat.com/errata/RHSA-2024:4415" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4321 vom 2024-07-10", "url": "https://access.redhat.com/errata/RHSA-2024:4321" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6892-1 vom 2024-07-10", "url": "https://ubuntu.com/security/notices/USN-6892-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6895-1 vom 2024-07-12", "url": "https://ubuntu.com/security/notices/USN-6895-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6898-1 vom 2024-07-15", "url": "https://ubuntu.com/security/notices/USN-6898-1" }, { "category": "external", "summary": "Rocky Linux Security Advisory RLSA-2024:4352 vom 2024-07-15", "url": "https://errata.build.resf.org/RLSA-2024:4352" }, { "category": "external", "summary": "Rocky Linux Security Advisory RLSA-2024:4211 vom 2024-07-15", "url": "https://errata.build.resf.org/RLSA-2024:4211" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6895-2 vom 2024-07-16", "url": "https://ubuntu.com/security/notices/USN-6895-2" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6898-2 vom 2024-07-17", "url": "https://ubuntu.com/security/notices/USN-6898-2" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6900-1 vom 2024-07-17", "url": "https://ubuntu.com/security/notices/USN-6900-1" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:2561-1 vom 2024-07-18", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-July/019001.html" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4631 vom 2024-07-18", "url": "https://access.redhat.com/errata/RHSA-2024:4631" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6895-3 vom 2024-07-19", "url": "https://ubuntu.com/security/notices/USN-6895-3" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6898-3 vom 2024-07-19", "url": "https://ubuntu.com/security/notices/USN-6898-3" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:2571-1 vom 2024-07-22", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-July/019019.html" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6898-4 vom 2024-07-23", "url": "https://ubuntu.com/security/notices/USN-6898-4" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4740 vom 2024-07-24", "url": "https://access.redhat.com/errata/RHSA-2024:4740" }, { "category": "external", "summary": "SEM 2024.2.1 release notes vom 2024-07-23", "url": "https://documentation.solarwinds.com/en/success_center/sem/content/release_notes/sem_2024-2-1_release_notes.htm" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4831 vom 2024-07-24", "url": "https://access.redhat.com/errata/RHSA-2024:4831" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4823 vom 2024-07-24", "url": "https://access.redhat.com/errata/RHSA-2024:4823" } ], "source_lang": "en-US", "title": "Linux Kernel: Mehrere Schwachstellen", "tracking": { "current_release_date": "2024-07-24T22:00:00.000+00:00", "generator": { "date": "2024-07-25T08:35:45.860+00:00", "engine": { "name": "BSI-WID", "version": "1.3.0" } }, "id": "WID-SEC-W-2024-0749", "initial_release_date": "2024-04-01T22:00:00.000+00:00", "revision_history": [ { "date": "2024-04-01T22:00:00.000+00:00", "number": "1", "summary": "Initiale Fassung" }, { "date": "2024-04-03T22:00:00.000+00:00", "number": "2", "summary": "Neue Updates von Fedora aufgenommen" }, { "date": "2024-04-16T22:00:00.000+00:00", "number": "3", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-04-18T22:00:00.000+00:00", "number": "4", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-04-29T22:00:00.000+00:00", "number": "5", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-05-01T22:00:00.000+00:00", "number": "6", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-05-02T22:00:00.000+00:00", "number": "7", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-05-06T22:00:00.000+00:00", "number": "8", "summary": "Neue Updates von Debian aufgenommen" }, { "date": "2024-05-07T22:00:00.000+00:00", "number": "9", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-05-13T22:00:00.000+00:00", "number": "10", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-05-14T22:00:00.000+00:00", "number": "11", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-05-15T22:00:00.000+00:00", "number": "12", "summary": "Neue Updates von SUSE und Ubuntu aufgenommen" }, { "date": "2024-05-20T22:00:00.000+00:00", "number": "13", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-05-21T22:00:00.000+00:00", "number": "14", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-05-22T22:00:00.000+00:00", "number": "15", "summary": "Neue Updates von Red Hat aufgenommen" }, { "date": "2024-05-26T22:00:00.000+00:00", "number": "16", "summary": "Neue Updates von Oracle Linux aufgenommen" }, { "date": "2024-05-28T22:00:00.000+00:00", "number": "17", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-05-30T22:00:00.000+00:00", "number": "18", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-06-04T22:00:00.000+00:00", "number": "19", "summary": "Neue Updates von Red Hat aufgenommen" }, { "date": "2024-06-06T22:00:00.000+00:00", "number": "20", "summary": "Neue Updates von Oracle Linux aufgenommen" }, { "date": "2024-06-09T22:00:00.000+00:00", "number": "21", "summary": "Neue Updates von Ubuntu und IBM aufgenommen" }, { "date": "2024-06-10T22:00:00.000+00:00", "number": "22", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-06-11T22:00:00.000+00:00", "number": "23", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-06-12T22:00:00.000+00:00", "number": "24", "summary": "Neue Updates von SUSE und Ubuntu aufgenommen" }, { "date": "2024-06-16T22:00:00.000+00:00", "number": "25", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-06-18T22:00:00.000+00:00", "number": "26", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-06-23T22:00:00.000+00:00", "number": "27", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-06-25T22:00:00.000+00:00", "number": "28", "summary": "Neue Updates von Debian und SUSE aufgenommen" }, { "date": "2024-06-26T22:00:00.000+00:00", "number": "29", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-06-27T22:00:00.000+00:00", "number": "30", "summary": "Neue Updates von Debian aufgenommen" }, { "date": "2024-07-01T22:00:00.000+00:00", "number": "31", "summary": "Neue Updates von Red Hat aufgenommen" }, { "date": "2024-07-02T22:00:00.000+00:00", "number": "32", "summary": "Neue Updates von Dell und Oracle Linux aufgenommen" }, { "date": "2024-07-03T22:00:00.000+00:00", "number": "33", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-07-04T22:00:00.000+00:00", "number": "34", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-07-07T22:00:00.000+00:00", "number": "35", "summary": "Neue Updates von Red Hat aufgenommen" }, { "date": "2024-07-09T22:00:00.000+00:00", "number": "36", "summary": "Neue Updates von Red Hat aufgenommen" }, { "date": "2024-07-10T22:00:00.000+00:00", "number": "37", "summary": "Neue Updates von Red Hat und Ubuntu aufgenommen" }, { "date": "2024-07-14T22:00:00.000+00:00", "number": "38", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-07-15T22:00:00.000+00:00", "number": "39", "summary": "Neue Updates von Ubuntu und Rocky Enterprise Software Foundation aufgenommen" }, { "date": "2024-07-17T22:00:00.000+00:00", "number": "40", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-07-18T22:00:00.000+00:00", "number": "41", "summary": "Neue Updates von SUSE und Red Hat aufgenommen" }, { "date": "2024-07-22T22:00:00.000+00:00", "number": "42", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-07-23T22:00:00.000+00:00", "number": "43", "summary": "Neue Updates von Red Hat aufgenommen" }, { "date": "2024-07-24T22:00:00.000+00:00", "number": "44", "summary": "Neue Updates von Red Hat aufgenommen" } ], "status": "final", "version": "44" } }, "product_tree": { "branches": [ { "branches": [ { "category": "product_name", "name": "Debian Linux", "product": { "name": "Debian Linux", "product_id": "2951", "product_identification_helper": { "cpe": "cpe:/o:debian:debian_linux:-" } } } ], "category": "vendor", "name": "Debian" }, { "branches": [ { "branches": [ { "category": "product_version_range", "name": "\u003c19.11", "product": { "name": "Dell NetWorker \u003c19.11", "product_id": "T035785", "product_identification_helper": { "cpe": "cpe:/a:dell:networker:19.11" } } } ], "category": "product_name", "name": "NetWorker" } ], "category": "vendor", "name": "Dell" }, { "branches": [ { "category": "product_name", "name": "Fedora Linux", "product": { "name": "Fedora Linux", "product_id": "74185", "product_identification_helper": { "cpe": "cpe:/o:fedoraproject:fedora:-" } } } ], "category": "vendor", "name": "Fedora" }, { "branches": [ { "category": "product_name", "name": "IBM QRadar SIEM", "product": { "name": "IBM QRadar SIEM", "product_id": "T021415", "product_identification_helper": { "cpe": "cpe:/a:ibm:qradar_siem:-" } } } ], "category": "vendor", "name": "IBM" }, { "branches": [ { "category": "product_name", "name": "Open Source Linux Kernel", "product": { "name": "Open Source Linux Kernel", "product_id": "T033834", "product_identification_helper": { "cpe": "cpe:/o:linux:linux_kernel:-" } } } ], "category": "vendor", "name": "Open Source" }, { "branches": [ { "category": "product_name", "name": "Oracle Linux", "product": { "name": "Oracle Linux", "product_id": "T004914", "product_identification_helper": { "cpe": "cpe:/o:oracle:linux:-" } } } ], "category": "vendor", "name": "Oracle" }, { "branches": [ { "category": "product_name", "name": "RESF Rocky Linux", "product": { "name": "RESF Rocky Linux", "product_id": "T032255", "product_identification_helper": { "cpe": "cpe:/o:resf:rocky_linux:-" } } } ], "category": "vendor", "name": "RESF" }, { "branches": [ { "category": "product_name", "name": "Red Hat Enterprise Linux", "product": { "name": "Red Hat Enterprise Linux", "product_id": "67646", "product_identification_helper": { "cpe": "cpe:/o:redhat:enterprise_linux:-" } } } ], "category": "vendor", "name": "Red Hat" }, { "branches": [ { "category": "product_name", "name": "SUSE Linux", "product": { "name": "SUSE Linux", "product_id": "T002207", "product_identification_helper": { "cpe": "cpe:/o:suse:suse_linux:-" } } } ], "category": "vendor", "name": "SUSE" }, { "branches": [ { "branches": [ { "category": "product_version_range", "name": "\u003c2024.2", "product": { "name": "SolarWinds Security Event Manager \u003c2024.2", "product_id": "T034244", "product_identification_helper": { "cpe": "cpe:/a:solarwinds:security_event_manager:2024.2" } } } ], "category": "product_name", "name": "Security Event Manager" } ], "category": "vendor", "name": "SolarWinds" }, { "branches": [ { "category": "product_name", "name": "Ubuntu Linux", "product": { "name": "Ubuntu Linux", "product_id": "T000126", "product_identification_helper": { "cpe": "cpe:/o:canonical:ubuntu_linux:-" } } } ], "category": "vendor", "name": "Ubuntu" } ] }, "vulnerabilities": [ { "cve": "CVE-2023-52629", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2023-52629" }, { "cve": "CVE-2023-52630", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2023-52630" }, { "cve": "CVE-2023-52631", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2023-52631" }, { "cve": "CVE-2023-52632", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2023-52632" }, { "cve": "CVE-2023-52633", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2023-52633" }, { "cve": "CVE-2023-52634", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2023-52634" }, { "cve": "CVE-2023-52635", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2023-52635" }, { "cve": "CVE-2023-52636", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2023-52636" }, { "cve": "CVE-2024-26653", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26653" }, { "cve": "CVE-2024-26654", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26654" }, { "cve": "CVE-2024-26655", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26655" }, { "cve": "CVE-2024-26656", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26656" }, { "cve": "CVE-2024-26657", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26657" }, { "cve": "CVE-2024-26658", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26658" }, { "cve": "CVE-2024-26659", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26659" }, { "cve": "CVE-2024-26660", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26660" }, { "cve": "CVE-2024-26661", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26661" }, { "cve": "CVE-2024-26662", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26662" }, { "cve": "CVE-2024-26663", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26663" }, { "cve": "CVE-2024-26664", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26664" }, { "cve": "CVE-2024-26665", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26665" }, { "cve": "CVE-2024-26666", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26666" }, { "cve": "CVE-2024-26667", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26667" }, { "cve": "CVE-2024-26668", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26668" }, { "cve": "CVE-2024-26669", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26669" }, { "cve": "CVE-2024-26670", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26670" }, { "cve": "CVE-2024-26671", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26671" }, { "cve": "CVE-2024-26672", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26672" }, { "cve": "CVE-2024-26673", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26673" }, { "cve": "CVE-2024-26674", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26674" }, { "cve": "CVE-2024-26675", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26675" }, { "cve": "CVE-2024-26676", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26676" }, { "cve": "CVE-2024-26677", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26677" }, { "cve": "CVE-2024-26678", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26678" }, { "cve": "CVE-2024-26679", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26679" }, { "cve": "CVE-2024-26680", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26680" }, { "cve": "CVE-2024-26681", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26681" }, { "cve": "CVE-2024-26682", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26682" }, { "cve": "CVE-2024-26683", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26683" }, { "cve": "CVE-2024-26684", "notes": [ { "category": "description", "text": "Im Linux-Kernel existieren verschiedene Schwachstellen in mehreren Komponenten und Subsystemen, wie z.B. \"blk-iocost\", \"drm/amd/display\" oder \"um: time-travel\". Sie sind unter anderem auf eine NULL Pointer Dereferenzierung, ein Use-After-Free oder ein Speicherleck zur\u00fcckzuf\u00fchren. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen Denial-of-Service Zustand herbeizuf\u00fchren oder einen nicht n\u00e4her spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "2951", "T002207", "67646", "T000126", "T021415", "T033834", "T004914", "T032255", "T035785", "74185", "T034244" ] }, "release_date": "2024-04-01T22:00:00Z", "title": "CVE-2024-26684" } ] }