Action not permitted
Modal body text goes here.
cve-2021-47072
Vulnerability from cvelistv5
{ "containers": { "adp": [ { "metrics": [ { "other": { "content": { "id": "CVE-2021-47072", "options": [ { "Exploitation": "none" }, { "Automatable": "no" }, { "Technical Impact": "partial" } ], "role": "CISA Coordinator", "timestamp": "2024-03-11T16:49:49.252452Z", "version": "2.0.3" }, "type": "ssvc" } } ], "providerMetadata": { "dateUpdated": "2024-06-04T17:13:49.970Z", "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP" }, "title": "CISA ADP Vulnrichment" }, { "providerMetadata": { "dateUpdated": "2024-08-04T05:24:39.601Z", "orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE" }, "references": [ { "tags": [ "x_transferred" ], "url": "https://git.kernel.org/stable/c/6d0924c5b742036b4f20a0ffdf2b6cf3f963f5f6" }, { "tags": [ "x_transferred" ], "url": "https://git.kernel.org/stable/c/54a40fc3a1da21b52dbf19f72fdc27a2ec740760" } ], "title": "CVE Program Container" } ], "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Linux", "programFiles": [ "fs/btrfs/tree-log.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "lessThan": "6d0924c5b742", "status": "affected", "version": "64d6b281ba4d", "versionType": "git" }, { "lessThan": "54a40fc3a1da", "status": "affected", "version": "64d6b281ba4d", "versionType": "git" } ] }, { "defaultStatus": "affected", "product": "Linux", "programFiles": [ "fs/btrfs/tree-log.c" ], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [ { "status": "affected", "version": "5.12" }, { "lessThan": "5.12", "status": "unaffected", "version": "0", "versionType": "semver" }, { "lessThanOrEqual": "5.12.*", "status": "unaffected", "version": "5.12.7", "versionType": "semver" }, { "lessThanOrEqual": "*", "status": "unaffected", "version": "5.13", "versionType": "original_commit_for_fix" } ] } ], "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix removed dentries still existing after log is synced\n\nWhen we move one inode from one directory to another and both the inode\nand its previous parent directory were logged before, we are not supposed\nto have the dentry for the old parent if we have a power failure after the\nlog is synced. Only the new dentry is supposed to exist.\n\nGenerally this works correctly, however there is a scenario where this is\nnot currently working, because the old parent of the file/directory that\nwas moved is not authoritative for a range that includes the dir index and\ndir item keys of the old dentry. This case is better explained with the\nfollowing example and reproducer:\n\n # The test requires a very specific layout of keys and items in the\n # fs/subvolume btree to trigger the bug. So we want to make sure that\n # on whatever platform we are, we have the same leaf/node size.\n #\n # Currently in btrfs the node/leaf size can not be smaller than the page\n # size (but it can be greater than the page size). So use the largest\n # supported node/leaf size (64K).\n\n $ mkfs.btrfs -f -n 65536 /dev/sdc\n $ mount /dev/sdc /mnt\n\n # \"testdir\" is inode 257.\n $ mkdir /mnt/testdir\n $ chmod 755 /mnt/testdir\n\n # Create several empty files to have the directory \"testdir\" with its\n # items spread over several leaves (7 in this case).\n $ for ((i = 1; i \u003c= 1200; i++)); do\n echo -n \u003e /mnt/testdir/file$i\n done\n\n # Create our test directory \"dira\", inode number 1458, which gets all\n # its items in leaf 7.\n #\n # The BTRFS_DIR_ITEM_KEY item for inode 257 (\"testdir\") that points to\n # the entry named \"dira\" is in leaf 2, while the BTRFS_DIR_INDEX_KEY\n # item that points to that entry is in leaf 3.\n #\n # For this particular filesystem node size (64K), file count and file\n # names, we endup with the directory entry items from inode 257 in\n # leaves 2 and 3, as previously mentioned - what matters for triggering\n # the bug exercised by this test case is that those items are not placed\n # in leaf 1, they must be placed in a leaf different from the one\n # containing the inode item for inode 257.\n #\n # The corresponding BTRFS_DIR_ITEM_KEY and BTRFS_DIR_INDEX_KEY items for\n # the parent inode (257) are the following:\n #\n # item 460 key (257 DIR_ITEM 3724298081) itemoff 48344 itemsize 34\n # location key (1458 INODE_ITEM 0) type DIR\n # transid 6 data_len 0 name_len 4\n # name: dira\n #\n # and:\n #\n # item 771 key (257 DIR_INDEX 1202) itemoff 36673 itemsize 34\n # location key (1458 INODE_ITEM 0) type DIR\n # transid 6 data_len 0 name_len 4\n # name: dira\n\n $ mkdir /mnt/testdir/dira\n\n # Make sure everything done so far is durably persisted.\n $ sync\n\n # Now do a change to inode 257 (\"testdir\") that does not result in\n # COWing leaves 2 and 3 - the leaves that contain the directory items\n # pointing to inode 1458 (directory \"dira\").\n #\n # Changing permissions, the owner/group, updating or adding a xattr,\n # etc, will not change (COW) leaves 2 and 3. So for the sake of\n # simplicity change the permissions of inode 257, which results in\n # updating its inode item and therefore change (COW) only leaf 1.\n\n $ chmod 700 /mnt/testdir\n\n # Now fsync directory inode 257.\n #\n # Since only the first leaf was changed/COWed, we log the inode item of\n # inode 257 and only the dentries found in the first leaf, all have a\n # key type of BTRFS_DIR_ITEM_KEY, and no keys of type\n # BTRFS_DIR_INDEX_KEY, because they sort after the former type and none\n # exist in the first leaf.\n #\n # We also log 3 items that represent ranges for dir items and dir\n # indexes for which the log is authoritative:\n #\n # 1) a key of type BTRFS_DIR_LOG_ITEM_KEY, which indicates the log is\n # authoritative for all BTRFS_DIR_ITEM_KEY keys that have an offset\n # in the range [0, 2285968570] (the offset here is th\n---truncated---" } ], "providerMetadata": { "dateUpdated": "2024-11-04T11:58:53.489Z", "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux" }, "references": [ { "url": "https://git.kernel.org/stable/c/6d0924c5b742036b4f20a0ffdf2b6cf3f963f5f6" }, { "url": "https://git.kernel.org/stable/c/54a40fc3a1da21b52dbf19f72fdc27a2ec740760" } ], "title": "btrfs: fix removed dentries still existing after log is synced", "x_generator": { "engine": "bippy-9e1c9544281a" } } }, "cveMetadata": { "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "assignerShortName": "Linux", "cveId": "CVE-2021-47072", "datePublished": "2024-03-01T21:15:10.710Z", "dateReserved": "2024-02-29T22:33:44.297Z", "dateUpdated": "2024-11-04T11:58:53.489Z", "state": "PUBLISHED" }, "dataType": "CVE_RECORD", "dataVersion": "5.1", "meta": { "nvd": "{\"cve\":{\"id\":\"CVE-2021-47072\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-03-01T22:15:47.010\",\"lastModified\":\"2024-03-01T22:22:25.913\",\"vulnStatus\":\"Awaiting Analysis\",\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nbtrfs: fix removed dentries still existing after log is synced\\n\\nWhen we move one inode from one directory to another and both the inode\\nand its previous parent directory were logged before, we are not supposed\\nto have the dentry for the old parent if we have a power failure after the\\nlog is synced. Only the new dentry is supposed to exist.\\n\\nGenerally this works correctly, however there is a scenario where this is\\nnot currently working, because the old parent of the file/directory that\\nwas moved is not authoritative for a range that includes the dir index and\\ndir item keys of the old dentry. This case is better explained with the\\nfollowing example and reproducer:\\n\\n # The test requires a very specific layout of keys and items in the\\n # fs/subvolume btree to trigger the bug. So we want to make sure that\\n # on whatever platform we are, we have the same leaf/node size.\\n #\\n # Currently in btrfs the node/leaf size can not be smaller than the page\\n # size (but it can be greater than the page size). So use the largest\\n # supported node/leaf size (64K).\\n\\n $ mkfs.btrfs -f -n 65536 /dev/sdc\\n $ mount /dev/sdc /mnt\\n\\n # \\\"testdir\\\" is inode 257.\\n $ mkdir /mnt/testdir\\n $ chmod 755 /mnt/testdir\\n\\n # Create several empty files to have the directory \\\"testdir\\\" with its\\n # items spread over several leaves (7 in this case).\\n $ for ((i = 1; i \u003c= 1200; i++)); do\\n echo -n \u003e /mnt/testdir/file$i\\n done\\n\\n # Create our test directory \\\"dira\\\", inode number 1458, which gets all\\n # its items in leaf 7.\\n #\\n # The BTRFS_DIR_ITEM_KEY item for inode 257 (\\\"testdir\\\") that points to\\n # the entry named \\\"dira\\\" is in leaf 2, while the BTRFS_DIR_INDEX_KEY\\n # item that points to that entry is in leaf 3.\\n #\\n # For this particular filesystem node size (64K), file count and file\\n # names, we endup with the directory entry items from inode 257 in\\n # leaves 2 and 3, as previously mentioned - what matters for triggering\\n # the bug exercised by this test case is that those items are not placed\\n # in leaf 1, they must be placed in a leaf different from the one\\n # containing the inode item for inode 257.\\n #\\n # The corresponding BTRFS_DIR_ITEM_KEY and BTRFS_DIR_INDEX_KEY items for\\n # the parent inode (257) are the following:\\n #\\n # item 460 key (257 DIR_ITEM 3724298081) itemoff 48344 itemsize 34\\n # location key (1458 INODE_ITEM 0) type DIR\\n # transid 6 data_len 0 name_len 4\\n # name: dira\\n #\\n # and:\\n #\\n # item 771 key (257 DIR_INDEX 1202) itemoff 36673 itemsize 34\\n # location key (1458 INODE_ITEM 0) type DIR\\n # transid 6 data_len 0 name_len 4\\n # name: dira\\n\\n $ mkdir /mnt/testdir/dira\\n\\n # Make sure everything done so far is durably persisted.\\n $ sync\\n\\n # Now do a change to inode 257 (\\\"testdir\\\") that does not result in\\n # COWing leaves 2 and 3 - the leaves that contain the directory items\\n # pointing to inode 1458 (directory \\\"dira\\\").\\n #\\n # Changing permissions, the owner/group, updating or adding a xattr,\\n # etc, will not change (COW) leaves 2 and 3. So for the sake of\\n # simplicity change the permissions of inode 257, which results in\\n # updating its inode item and therefore change (COW) only leaf 1.\\n\\n $ chmod 700 /mnt/testdir\\n\\n # Now fsync directory inode 257.\\n #\\n # Since only the first leaf was changed/COWed, we log the inode item of\\n # inode 257 and only the dentries found in the first leaf, all have a\\n # key type of BTRFS_DIR_ITEM_KEY, and no keys of type\\n # BTRFS_DIR_INDEX_KEY, because they sort after the former type and none\\n # exist in the first leaf.\\n #\\n # We also log 3 items that represent ranges for dir items and dir\\n # indexes for which the log is authoritative:\\n #\\n # 1) a key of type BTRFS_DIR_LOG_ITEM_KEY, which indicates the log is\\n # authoritative for all BTRFS_DIR_ITEM_KEY keys that have an offset\\n # in the range [0, 2285968570] (the offset here is th\\n---truncated---\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: btrfs: corrige las dentries eliminadas que a\u00fan existen despu\u00e9s de sincronizar el registro. Cuando movemos un inodo de un directorio a otro y tanto el inodo como su directorio principal anterior se registraron antes, se supone que no tener la dentry del padre anterior si tenemos un corte de energ\u00eda despu\u00e9s de sincronizar el registro. Se supone que s\u00f3lo existe el nuevo dentry. En general, esto funciona correctamente, sin embargo, hay un escenario en el que esto no funciona actualmente, porque el padre antiguo del archivo/directorio que se movi\u00f3 no tiene autoridad para un rango que incluye el \u00edndice de directorio y las claves de elemento de directorio del dentry anterior. Este caso se explica mejor con el siguiente ejemplo y reproductor: # La prueba requiere un dise\u00f1o muy espec\u00edfico de claves y elementos en el \u00e1rbol # fs/subvolume para activar el error. Por eso queremos asegurarnos de que # en cualquier plataforma en la que estemos, tengamos el mismo tama\u00f1o de hoja/nodo. # # Actualmente en btrfs el tama\u00f1o del nodo/hoja no puede ser menor que el tama\u00f1o de la p\u00e1gina # (pero puede ser mayor que el tama\u00f1o de la p\u00e1gina). Por lo tanto, utilice el mayor tama\u00f1o de nodo/hoja admitido (64K). $ mkfs.btrfs -f -n 65536 /dev/sdc $ mount /dev/sdc /mnt # \\\"testdir\\\" is inode 257. $ mkdir /mnt/testdir $ chmod 755 /mnt/testdir # Create several empty files to have the directory \\\"testdir\\\" with its # items spread over several leaves (7 in this case). $ for ((i = 1; i \u0026lt;= 1200; i++)); do echo -n \u0026gt; /mnt/testdir/file$i done # Create our test directory \\\"dira\\\", inode number 1458, which gets all # its items in leaf 7. # # The BTRFS_DIR_ITEM_KEY item for inode 257 (\\\"testdir\\\") that points to # the entry named \\\"dira\\\" is in leaf 2, while the BTRFS_DIR_INDEX_KEY # item that points to that entry is in leaf 3. # # For this particular filesystem node size (64K), file count and file # names, we endup with the directory entry items from inode 257 in # leaves 2 and 3, as previously mentioned - what matters for triggering # the bug exercised by this test case is that those items are not placed # in leaf 1, they must be placed in a leaf different from the one # containing the inode item for inode 257. # # The corresponding BTRFS_DIR_ITEM_KEY and BTRFS_DIR_INDEX_KEY items for # the parent inode (257) are the following: # # item 460 key (257 DIR_ITEM 3724298081) itemoff 48344 itemsize 34 # location key (1458 INODE_ITEM 0) type DIR # transid 6 data_len 0 name_len 4 # name: dira # # and: # # item 771 key (257 DIR_INDEX 1202) itemoff 36673 itemsize 34 # location key (1458 INODE_ITEM 0) type DIR # transid 6 data_len 0 name_len 4 # name: dira $ mkdir /mnt/testdir/dira # Make sure everything done so far is durably persisted. $ sync # Now do a change to inode 257 (\\\"testdir\\\") that does not result in # COWing leaves 2 and 3 - the leaves that contain the directory items # pointing to inode 1458 (directory \\\"dira\\\"). # # Changing permissions, the owner/group, updating or adding a xattr, # etc, will not change (COW) leaves 2 and 3. So for the sake of # simplicity change the permissions of inode 257, which results in # updating its inode item and therefore change (COW) only leaf 1. $ chmod 700 /mnt/testdir # Now fsync directory inode 257. # # Since only the first leaf was changed/COWed, we log the inode item of # inode 257 and only the dentries found in the first leaf, all have a # key type of BTRFS_DIR_ITEM_KEY, and no keys of type # BTRFS_DIR_INDEX_KEY, because they sort after the former type and none # exist in the first leaf. # # We also log 3 items that represent ranges for dir items and dir # indexes for which the log is authoritative: # # 1) a key of type BTRFS_DIR_LOG_ITEM_KEY, which indicates the log is # authoritative for all BTRFS_DIR_ITEM_KEY keys that have an offset # in the range [0, 2285968570] (the offset here is th ---truncated--- \"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/54a40fc3a1da21b52dbf19f72fdc27a2ec740760\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/6d0924c5b742036b4f20a0ffdf2b6cf3f963f5f6\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}" } }
wid-sec-w-2024-0534
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": "Der Kernel stellt den Kern des Linux Betriebssystems dar.", "title": "Produktbeschreibung" }, { "category": "summary", "text": "Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand herbeizuf\u00fchren oder einen nicht 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-0534 - CSAF Version", "url": "https://wid.cert-bund.de/.well-known/csaf/white/2024/wid-sec-w-2024-0534.json" }, { "category": "self", "summary": "WID-SEC-2024-0534 - Portal Version", "url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2024-0534" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:0855-1 vom 2024-03-12", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-March/018151.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:0900-1 vom 2024-03-14", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-March/018167.html" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030141-CVE-2021-47069-5797@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030141-CVE-2021-47070-0525@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030141-CVE-2021-47071-cd46@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030141-CVE-2021-47072-52d4@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47073-704a@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47074-46a7@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47075-8d12@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47076-a6b6@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47077-994b@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47078-71f9@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47079-3934@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030142-CVE-2021-47080-eb20@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030143-CVE-2021-47081-e590@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030251-CVE-2023-52518-bcfa@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030252-CVE-2022-48627-c7bf@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52559-680e@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030252-CVE-2023-52560-c3de@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52561-89b2@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52563-269f@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030253-CVE-2023-52564-88cb@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52565-07ce@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52566-69f0@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030254-CVE-2023-52567-38c1@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52568-b5c6@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52569-a9c1@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52570-0789@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030255-CVE-2023-52571-087e@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030255-CVE-2024-26621-9300@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030256-CVE-2023-52572-2b92@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030256-CVE-2023-52573-531c@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030256-CVE-2023-52574-a423@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030256-CVE-2023-52575-34bf@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030257-CVE-2023-52576-7ee2@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030257-CVE-2023-52577-2638@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030257-CVE-2023-52578-50cb@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030257-CVE-2023-52579-af56@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030258-CVE-2023-52580-c37e@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030258-CVE-2023-52581-2165@gregkh/" }, { "category": "external", "summary": "CVE Announce auf lore.kernel.org vom 2024-03-03", "url": "http://lore.kernel.org/linux-cve-announce/2024030258-CVE-2023-52582-07c8@gregkh/" }, { "category": "external", "summary": "RedHat Bugzilla vom 2024-03-03", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2267507" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-86jx-fj9h-9hp8" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-f8jx-pmvg-jgfh" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-fh4f-4w54-vgrf" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-h234-f9wp-jpmr" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-hr4c-2jrx-4v7g" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-j6qg-38wf-82gm" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-mvcc-fjcm-33jm" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-mx24-9c8c-52xx" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-r9r6-c43w-4hr8" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-vhp7-fvvc-gp4m" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-vvwp-xfww-2qhh" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-w2cg-jcf6-hrgr" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-x9q8-72p3-mmvx" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-xc3g-cm27-mcmg" }, { "category": "external", "summary": "GitHub Advisory Database vom 2024-03-03", "url": "https://github.com/advisories/GHSA-xqf9-qrgq-fxfv" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:0856-1 vom 2024-03-13", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-March/018155.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:0857-1 vom 2024-03-13", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-March/018154.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:0900-2 vom 2024-03-15", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-March/018182.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:0975-1 vom 2024-03-22", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-March/018186.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:0925-1 vom 2024-03-22", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-March/018205.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:0976-1 vom 2024-03-22", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-March/018185.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:0926-1 vom 2024-03-22", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-March/018204.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:0977-1 vom 2024-03-22", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-March/018210.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1320-1 vom 2024-04-16", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-April/018372.html" }, { "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:1321-1 vom 2024-04-17", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-April/018375.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: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: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:1454-1 vom 2024-04-26", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-April/018431.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": "Red Hat Security Advisory RHSA-2024:2394 vom 2024-04-30", "url": "https://access.redhat.com/errata/RHSA-2024:2394" }, { "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": "Dell Security Advisory DSA-2024-198 vom 2024-05-08", "url": "https://www.dell.com/support/kbdoc/000224827/dsa-2024-=" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1645-1 vom 2024-05-14", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-May/018527.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:1642-1 vom 2024-05-14", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-May/018530.html" }, { "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: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:1650-1 vom 2024-05-15", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-May/018533.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-6778-1 vom 2024-05-16", "url": "https://ubuntu.com/security/notices/USN-6778-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6777-1 vom 2024-05-16", "url": "https://ubuntu.com/security/notices/USN-6777-1" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6777-2 vom 2024-05-20", "url": "https://ubuntu.com/security/notices/USN-6777-2" }, { "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": "Ubuntu Security Notice USN-6777-3 vom 2024-05-22", "url": "https://ubuntu.com/security/notices/USN-6777-3" }, { "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:3138 vom 2024-05-22", "url": "https://access.redhat.com/errata/RHSA-2024:3138" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6777-4 vom 2024-05-23", "url": "https://ubuntu.com/security/notices/USN-6777-4" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:3462 vom 2024-05-29", "url": "https://access.redhat.com/errata/RHSA-2024:3462" }, { "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:3530 vom 2024-05-31", "url": "https://access.redhat.com/errata/RHSA-2024:3530" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:3528 vom 2024-05-31", "url": "https://access.redhat.com/errata/RHSA-2024:3528" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:3529 vom 2024-05-31", "url": "https://access.redhat.com/errata/RHSA-2024:3529" }, { "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": "IBM Security Bulletin 7156774 vom 2024-06-07", "url": "https://www.ibm.com/support/pages/node/7156774" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1979-1 vom 2024-06-11", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-June/018685.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:1983-1 vom 2024-06-11", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-June/018700.html" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:3810 vom 2024-06-11", "url": "https://access.redhat.com/errata/RHSA-2024:3810" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6831-1 vom 2024-06-12", "url": "https://ubuntu.com/security/notices/USN-6831-1" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:2010-1 vom 2024-06-12", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-June/018711.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:2183-1 vom 2024-06-24", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-June/018808.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:2184-1 vom 2024-06-24", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-June/018807.html" }, { "category": "external", "summary": "SUSE Security Update SUSE-SU-2024:2185-1 vom 2024-06-24", "url": "https://lists.suse.com/pipermail/sle-security-updates/2024-June/018809.html" }, { "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": "Oracle Linux Security Advisory ELSA-2024-4211 vom 2024-07-03", "url": "https://linux.oracle.com/errata/ELSA-2024-4211.html" }, { "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": "Ubuntu Security Notice USN-6867-1 vom 2024-07-04", "url": "https://ubuntu.com/security/notices/USN-6867-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:4321 vom 2024-07-10", "url": "https://access.redhat.com/errata/RHSA-2024:4321" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6896-1 vom 2024-07-12", "url": "https://ubuntu.com/security/notices/USN-6896-1" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4533 vom 2024-07-15", "url": "https://access.redhat.com/errata/RHSA-2024:4533" }, { "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": "Red Hat Security Advisory RHSA-2024:4554 vom 2024-07-16", "url": "https://access.redhat.com/errata/RHSA-2024:4554" }, { "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": "Ubuntu Security Notice USN-6896-2 vom 2024-07-16", "url": "https://ubuntu.com/security/notices/USN-6896-2" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4583 vom 2024-07-17", "url": "https://access.redhat.com/errata/RHSA-2024:4583" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6896-3 vom 2024-07-17", "url": "https://ubuntu.com/security/notices/USN-6896-3" }, { "category": "external", "summary": "Oracle Linux Security Advisory ELSA-2024-4583 vom 2024-07-19", "url": "https://linux.oracle.com/errata/ELSA-2024-4583.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-6896-4 vom 2024-07-19", "url": "https://ubuntu.com/security/notices/USN-6896-4" }, { "category": "external", "summary": "Ubuntu Security Notice USN-6896-5 vom 2024-07-23", "url": "https://ubuntu.com/security/notices/USN-6896-5" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4823 vom 2024-07-24", "url": "https://access.redhat.com/errata/RHSA-2024:4823" }, { "category": "external", "summary": "Red Hat Security Advisory RHSA-2024:4831 vom 2024-07-24", "url": "https://access.redhat.com/errata/RHSA-2024:4831" } ], "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:36:01.156+00:00", "engine": { "name": "BSI-WID", "version": "1.3.0" } }, "id": "WID-SEC-W-2024-0534", "initial_release_date": "2024-03-03T23:00:00.000+00:00", "revision_history": [ { "date": "2024-03-03T23:00:00.000+00:00", "number": "1", "summary": "Initiale Fassung" }, { "date": "2024-03-12T23:00:00.000+00:00", "number": "2", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-03-14T23:00:00.000+00:00", "number": "3", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-03-17T23:00:00.000+00:00", "number": "4", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-03-24T23:00:00.000+00:00", "number": "5", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-04-16T22:00:00.000+00:00", "number": "6", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-04-18T22:00:00.000+00:00", "number": "7", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-04-21T22:00:00.000+00:00", "number": "8", "summary": "Doppelte Eintragung korrigiert" }, { "date": "2024-04-28T22:00:00.000+00:00", "number": "9", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-04-29T22:00:00.000+00:00", "number": "10", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-05-01T22:00:00.000+00:00", "number": "11", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-05-02T22:00:00.000+00:00", "number": "12", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-05-07T22:00:00.000+00:00", "number": "13", "summary": "Neue Updates von Dell aufgenommen" }, { "date": "2024-05-14T22:00:00.000+00:00", "number": "14", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-05-15T22:00:00.000+00:00", "number": "15", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-05-16T22:00:00.000+00:00", "number": "16", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-05-20T22:00:00.000+00:00", "number": "17", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-05-21T22:00:00.000+00:00", "number": "18", "summary": "Neue Updates von SUSE und Ubuntu aufgenommen" }, { "date": "2024-05-23T22:00:00.000+00:00", "number": "19", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-05-28T22:00:00.000+00:00", "number": "20", "summary": "Neue Updates von Red Hat aufgenommen" }, { "date": "2024-05-30T22:00:00.000+00:00", "number": "21", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-06-02T22:00:00.000+00:00", "number": "22", "summary": "Neue Updates von Red Hat aufgenommen" }, { "date": "2024-06-04T22:00:00.000+00:00", "number": "23", "summary": "Neue Updates von Red Hat aufgenommen" }, { "date": "2024-06-06T22:00:00.000+00:00", "number": "24", "summary": "Neue Updates von Oracle Linux aufgenommen" }, { "date": "2024-06-09T22:00:00.000+00:00", "number": "25", "summary": "Neue Updates von IBM aufgenommen" }, { "date": "2024-06-10T22:00:00.000+00:00", "number": "26", "summary": "Neue Updates von SUSE aufgenommen" }, { "date": "2024-06-11T22:00:00.000+00:00", "number": "27", "summary": "Neue Updates von SUSE und Red Hat aufgenommen" }, { "date": "2024-06-12T22:00:00.000+00:00", "number": "28", "summary": "Neue Updates von Ubuntu und SUSE aufgenommen" }, { "date": "2024-06-24T22:00:00.000+00:00", "number": "29", "summary": "Neue Updates von SUSE 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 Oracle Linux und Dell aufgenommen" }, { "date": "2024-07-03T22:00:00.000+00:00", "number": "33", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-07-07T22:00:00.000+00:00", "number": "34", "summary": "Neue Updates von Red Hat aufgenommen" }, { "date": "2024-07-10T22:00:00.000+00:00", "number": "35", "summary": "Neue Updates von Red Hat aufgenommen" }, { "date": "2024-07-14T22:00:00.000+00:00", "number": "36", "summary": "Neue Updates von Ubuntu und Red Hat aufgenommen" }, { "date": "2024-07-15T22:00:00.000+00:00", "number": "37", "summary": "Neue Updates von Rocky Enterprise Software Foundation und Red Hat aufgenommen" }, { "date": "2024-07-16T22:00:00.000+00:00", "number": "38", "summary": "Neue Updates von Ubuntu und Red Hat aufgenommen" }, { "date": "2024-07-17T22:00:00.000+00:00", "number": "39", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-07-18T22:00:00.000+00:00", "number": "40", "summary": "Neue Updates von Oracle Linux und Red Hat aufgenommen" }, { "date": "2024-07-22T22:00:00.000+00:00", "number": "41", "summary": "Neue Updates von Ubuntu aufgenommen" }, { "date": "2024-07-24T22:00:00.000+00:00", "number": "42", "summary": "Neue Updates von Red Hat aufgenommen" } ], "status": "final", "version": "42" } }, "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", "name": "virtual", "product": { "name": "Dell NetWorker virtual", "product_id": "T034583", "product_identification_helper": { "cpe": "cpe:/a:dell:networker:virtual" } } }, { "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": "EMC Avamar", "product": { "name": "EMC Avamar", "product_id": "T014381", "product_identification_helper": { "cpe": "cpe:/a:emc:avamar:-" } } } ], "category": "vendor", "name": "EMC" }, { "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": "T033208", "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": [ { "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-2021-47069", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47069" }, { "cve": "CVE-2021-47070", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47070" }, { "cve": "CVE-2021-47071", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47071" }, { "cve": "CVE-2021-47072", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47072" }, { "cve": "CVE-2021-47073", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47073" }, { "cve": "CVE-2021-47074", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47074" }, { "cve": "CVE-2021-47075", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47075" }, { "cve": "CVE-2021-47076", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47076" }, { "cve": "CVE-2021-47077", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47077" }, { "cve": "CVE-2021-47078", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47078" }, { "cve": "CVE-2021-47079", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47079" }, { "cve": "CVE-2021-47080", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47080" }, { "cve": "CVE-2021-47081", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2021-47081" }, { "cve": "CVE-2022-48627", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2022-48627" }, { "cve": "CVE-2022-48628", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2022-48628" }, { "cve": "CVE-2023-52505", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52505" }, { "cve": "CVE-2023-52518", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52518" }, { "cve": "CVE-2023-52519", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52519" }, { "cve": "CVE-2023-52520", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52520" }, { "cve": "CVE-2023-52521", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52521" }, { "cve": "CVE-2023-52522", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52522" }, { "cve": "CVE-2023-52523", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52523" }, { "cve": "CVE-2023-52524", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52524" }, { "cve": "CVE-2023-52525", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52525" }, { "cve": "CVE-2023-52526", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52526" }, { "cve": "CVE-2023-52527", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52527" }, { "cve": "CVE-2023-52528", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52528" }, { "cve": "CVE-2023-52529", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52529" }, { "cve": "CVE-2023-52531", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52531" }, { "cve": "CVE-2023-52532", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52532" }, { "cve": "CVE-2023-52559", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52559" }, { "cve": "CVE-2023-52560", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52560" }, { "cve": "CVE-2023-52561", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52561" }, { "cve": "CVE-2023-52562", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52562" }, { "cve": "CVE-2023-52563", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52563" }, { "cve": "CVE-2023-52564", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52564" }, { "cve": "CVE-2023-52565", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52565" }, { "cve": "CVE-2023-52566", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52566" }, { "cve": "CVE-2023-52567", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52567" }, { "cve": "CVE-2023-52568", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52568" }, { "cve": "CVE-2023-52569", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52569" }, { "cve": "CVE-2023-52570", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52570" }, { "cve": "CVE-2023-52571", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52571" }, { "cve": "CVE-2023-52572", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52572" }, { "cve": "CVE-2023-52573", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52573" }, { "cve": "CVE-2023-52574", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52574" }, { "cve": "CVE-2023-52575", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52575" }, { "cve": "CVE-2023-52576", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52576" }, { "cve": "CVE-2023-52577", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52577" }, { "cve": "CVE-2023-52578", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52578" }, { "cve": "CVE-2023-52579", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52579" }, { "cve": "CVE-2023-52580", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52580" }, { "cve": "CVE-2023-52581", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52581" }, { "cve": "CVE-2023-52582", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2023-52582" }, { "cve": "CVE-2024-26621", "notes": [ { "category": "description", "text": "Es bestehen mehrere Schwachstellen im Linux-Kernel. Diese Fehler bestehen in mehreren Komponenten und Subsystemen wie btrfs, nvmet oder dccp aufgrund mehrerer sicherheitsrelevanter Probleme wie einer use-after-free, einer race condition oder einer NULL pointer dereference. Ein lokaler Angreifer kann diese Schwachstellen ausnutzen, um einen \u0027Denial of Service\u0027-Zustand auszul\u00f6sen und einen nicht spezifizierten Angriff durchzuf\u00fchren." } ], "product_status": { "known_affected": [ "T014381", "2951", "T002207", "T033208", "67646", "T000126", "T021415", "T034583", "T004914", "T032255", "T035785" ] }, "release_date": "2024-03-03T23:00:00Z", "title": "CVE-2024-26621" } ] }
ghsa-qcc7-grh2-48hx
Vulnerability from github
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix removed dentries still existing after log is synced
When we move one inode from one directory to another and both the inode and its previous parent directory were logged before, we are not supposed to have the dentry for the old parent if we have a power failure after the log is synced. Only the new dentry is supposed to exist.
Generally this works correctly, however there is a scenario where this is not currently working, because the old parent of the file/directory that was moved is not authoritative for a range that includes the dir index and dir item keys of the old dentry. This case is better explained with the following example and reproducer:
# The test requires a very specific layout of keys and items in the # fs/subvolume btree to trigger the bug. So we want to make sure that # on whatever platform we are, we have the same leaf/node size. # # Currently in btrfs the node/leaf size can not be smaller than the page # size (but it can be greater than the page size). So use the largest # supported node/leaf size (64K).
$ mkfs.btrfs -f -n 65536 /dev/sdc $ mount /dev/sdc /mnt
# "testdir" is inode 257. $ mkdir /mnt/testdir $ chmod 755 /mnt/testdir
# Create several empty files to have the directory "testdir" with its # items spread over several leaves (7 in this case). $ for ((i = 1; i <= 1200; i++)); do echo -n > /mnt/testdir/file$i done
# Create our test directory "dira", inode number 1458, which gets all # its items in leaf 7. # # The BTRFS_DIR_ITEM_KEY item for inode 257 ("testdir") that points to # the entry named "dira" is in leaf 2, while the BTRFS_DIR_INDEX_KEY # item that points to that entry is in leaf 3. # # For this particular filesystem node size (64K), file count and file # names, we endup with the directory entry items from inode 257 in # leaves 2 and 3, as previously mentioned - what matters for triggering # the bug exercised by this test case is that those items are not placed # in leaf 1, they must be placed in a leaf different from the one # containing the inode item for inode 257. # # The corresponding BTRFS_DIR_ITEM_KEY and BTRFS_DIR_INDEX_KEY items for # the parent inode (257) are the following: # # item 460 key (257 DIR_ITEM 3724298081) itemoff 48344 itemsize 34 # location key (1458 INODE_ITEM 0) type DIR # transid 6 data_len 0 name_len 4 # name: dira # # and: # # item 771 key (257 DIR_INDEX 1202) itemoff 36673 itemsize 34 # location key (1458 INODE_ITEM 0) type DIR # transid 6 data_len 0 name_len 4 # name: dira
$ mkdir /mnt/testdir/dira
# Make sure everything done so far is durably persisted. $ sync
# Now do a change to inode 257 ("testdir") that does not result in # COWing leaves 2 and 3 - the leaves that contain the directory items # pointing to inode 1458 (directory "dira"). # # Changing permissions, the owner/group, updating or adding a xattr, # etc, will not change (COW) leaves 2 and 3. So for the sake of # simplicity change the permissions of inode 257, which results in # updating its inode item and therefore change (COW) only leaf 1.
$ chmod 700 /mnt/testdir
# Now fsync directory inode 257. # # Since only the first leaf was changed/COWed, we log the inode item of # inode 257 and only the dentries found in the first leaf, all have a # key type of BTRFS_DIR_ITEM_KEY, and no keys of type # BTRFS_DIR_INDEX_KEY, because they sort after the former type and none # exist in the first leaf. # # We also log 3 items that represent ranges for dir items and dir # indexes for which the log is authoritative: # # 1) a key of type BTRFS_DIR_LOG_ITEM_KEY, which indicates the log is # authoritative for all BTRFS_DIR_ITEM_KEY keys that have an offset # in the range [0, 2285968570] (the offset here is th ---truncated---
{ "affected": [], "aliases": [ "CVE-2021-47072" ], "database_specific": { "cwe_ids": [], "github_reviewed": false, "github_reviewed_at": null, "nvd_published_at": "2024-03-01T22:15:47Z", "severity": null }, "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix removed dentries still existing after log is synced\n\nWhen we move one inode from one directory to another and both the inode\nand its previous parent directory were logged before, we are not supposed\nto have the dentry for the old parent if we have a power failure after the\nlog is synced. Only the new dentry is supposed to exist.\n\nGenerally this works correctly, however there is a scenario where this is\nnot currently working, because the old parent of the file/directory that\nwas moved is not authoritative for a range that includes the dir index and\ndir item keys of the old dentry. This case is better explained with the\nfollowing example and reproducer:\n\n # The test requires a very specific layout of keys and items in the\n # fs/subvolume btree to trigger the bug. So we want to make sure that\n # on whatever platform we are, we have the same leaf/node size.\n #\n # Currently in btrfs the node/leaf size can not be smaller than the page\n # size (but it can be greater than the page size). So use the largest\n # supported node/leaf size (64K).\n\n $ mkfs.btrfs -f -n 65536 /dev/sdc\n $ mount /dev/sdc /mnt\n\n # \"testdir\" is inode 257.\n $ mkdir /mnt/testdir\n $ chmod 755 /mnt/testdir\n\n # Create several empty files to have the directory \"testdir\" with its\n # items spread over several leaves (7 in this case).\n $ for ((i = 1; i \u003c= 1200; i++)); do\n echo -n \u003e /mnt/testdir/file$i\n done\n\n # Create our test directory \"dira\", inode number 1458, which gets all\n # its items in leaf 7.\n #\n # The BTRFS_DIR_ITEM_KEY item for inode 257 (\"testdir\") that points to\n # the entry named \"dira\" is in leaf 2, while the BTRFS_DIR_INDEX_KEY\n # item that points to that entry is in leaf 3.\n #\n # For this particular filesystem node size (64K), file count and file\n # names, we endup with the directory entry items from inode 257 in\n # leaves 2 and 3, as previously mentioned - what matters for triggering\n # the bug exercised by this test case is that those items are not placed\n # in leaf 1, they must be placed in a leaf different from the one\n # containing the inode item for inode 257.\n #\n # The corresponding BTRFS_DIR_ITEM_KEY and BTRFS_DIR_INDEX_KEY items for\n # the parent inode (257) are the following:\n #\n # item 460 key (257 DIR_ITEM 3724298081) itemoff 48344 itemsize 34\n # location key (1458 INODE_ITEM 0) type DIR\n # transid 6 data_len 0 name_len 4\n # name: dira\n #\n # and:\n #\n # item 771 key (257 DIR_INDEX 1202) itemoff 36673 itemsize 34\n # location key (1458 INODE_ITEM 0) type DIR\n # transid 6 data_len 0 name_len 4\n # name: dira\n\n $ mkdir /mnt/testdir/dira\n\n # Make sure everything done so far is durably persisted.\n $ sync\n\n # Now do a change to inode 257 (\"testdir\") that does not result in\n # COWing leaves 2 and 3 - the leaves that contain the directory items\n # pointing to inode 1458 (directory \"dira\").\n #\n # Changing permissions, the owner/group, updating or adding a xattr,\n # etc, will not change (COW) leaves 2 and 3. So for the sake of\n # simplicity change the permissions of inode 257, which results in\n # updating its inode item and therefore change (COW) only leaf 1.\n\n $ chmod 700 /mnt/testdir\n\n # Now fsync directory inode 257.\n #\n # Since only the first leaf was changed/COWed, we log the inode item of\n # inode 257 and only the dentries found in the first leaf, all have a\n # key type of BTRFS_DIR_ITEM_KEY, and no keys of type\n # BTRFS_DIR_INDEX_KEY, because they sort after the former type and none\n # exist in the first leaf.\n #\n # We also log 3 items that represent ranges for dir items and dir\n # indexes for which the log is authoritative:\n #\n # 1) a key of type BTRFS_DIR_LOG_ITEM_KEY, which indicates the log is\n # authoritative for all BTRFS_DIR_ITEM_KEY keys that have an offset\n # in the range [0, 2285968570] (the offset here is th\n---truncated---", "id": "GHSA-qcc7-grh2-48hx", "modified": "2024-03-02T00:31:30Z", "published": "2024-03-02T00:31:30Z", "references": [ { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2021-47072" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/54a40fc3a1da21b52dbf19f72fdc27a2ec740760" }, { "type": "WEB", "url": "https://git.kernel.org/stable/c/6d0924c5b742036b4f20a0ffdf2b6cf3f963f5f6" } ], "schema_version": "1.4.0", "severity": [] }
gsd-2021-47072
Vulnerability from gsd
{ "gsd": { "metadata": { "exploitCode": "unknown", "remediation": "unknown", "reportConfidence": "confirmed", "type": "vulnerability" }, "osvSchema": { "aliases": [ "CVE-2021-47072" ], "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix removed dentries still existing after log is synced\n\nWhen we move one inode from one directory to another and both the inode\nand its previous parent directory were logged before, we are not supposed\nto have the dentry for the old parent if we have a power failure after the\nlog is synced. Only the new dentry is supposed to exist.\n\nGenerally this works correctly, however there is a scenario where this is\nnot currently working, because the old parent of the file/directory that\nwas moved is not authoritative for a range that includes the dir index and\ndir item keys of the old dentry. This case is better explained with the\nfollowing example and reproducer:\n\n # The test requires a very specific layout of keys and items in the\n # fs/subvolume btree to trigger the bug. So we want to make sure that\n # on whatever platform we are, we have the same leaf/node size.\n #\n # Currently in btrfs the node/leaf size can not be smaller than the page\n # size (but it can be greater than the page size). So use the largest\n # supported node/leaf size (64K).\n\n $ mkfs.btrfs -f -n 65536 /dev/sdc\n $ mount /dev/sdc /mnt\n\n # \"testdir\" is inode 257.\n $ mkdir /mnt/testdir\n $ chmod 755 /mnt/testdir\n\n # Create several empty files to have the directory \"testdir\" with its\n # items spread over several leaves (7 in this case).\n $ for ((i = 1; i \u003c= 1200; i++)); do\n echo -n \u003e /mnt/testdir/file$i\n done\n\n # Create our test directory \"dira\", inode number 1458, which gets all\n # its items in leaf 7.\n #\n # The BTRFS_DIR_ITEM_KEY item for inode 257 (\"testdir\") that points to\n # the entry named \"dira\" is in leaf 2, while the BTRFS_DIR_INDEX_KEY\n # item that points to that entry is in leaf 3.\n #\n # For this particular filesystem node size (64K), file count and file\n # names, we endup with the directory entry items from inode 257 in\n # leaves 2 and 3, as previously mentioned - what matters for triggering\n # the bug exercised by this test case is that those items are not placed\n # in leaf 1, they must be placed in a leaf different from the one\n # containing the inode item for inode 257.\n #\n # The corresponding BTRFS_DIR_ITEM_KEY and BTRFS_DIR_INDEX_KEY items for\n # the parent inode (257) are the following:\n #\n # item 460 key (257 DIR_ITEM 3724298081) itemoff 48344 itemsize 34\n # location key (1458 INODE_ITEM 0) type DIR\n # transid 6 data_len 0 name_len 4\n # name: dira\n #\n # and:\n #\n # item 771 key (257 DIR_INDEX 1202) itemoff 36673 itemsize 34\n # location key (1458 INODE_ITEM 0) type DIR\n # transid 6 data_len 0 name_len 4\n # name: dira\n\n $ mkdir /mnt/testdir/dira\n\n # Make sure everything done so far is durably persisted.\n $ sync\n\n # Now do a change to inode 257 (\"testdir\") that does not result in\n # COWing leaves 2 and 3 - the leaves that contain the directory items\n # pointing to inode 1458 (directory \"dira\").\n #\n # Changing permissions, the owner/group, updating or adding a xattr,\n # etc, will not change (COW) leaves 2 and 3. So for the sake of\n # simplicity change the permissions of inode 257, which results in\n # updating its inode item and therefore change (COW) only leaf 1.\n\n $ chmod 700 /mnt/testdir\n\n # Now fsync directory inode 257.\n #\n # Since only the first leaf was changed/COWed, we log the inode item of\n # inode 257 and only the dentries found in the first leaf, all have a\n # key type of BTRFS_DIR_ITEM_KEY, and no keys of type\n # BTRFS_DIR_INDEX_KEY, because they sort after the former type and none\n # exist in the first leaf.\n #\n # We also log 3 items that represent ranges for dir items and dir\n # indexes for which the log is authoritative:\n #\n # 1) a key of type BTRFS_DIR_LOG_ITEM_KEY, which indicates the log is\n # authoritative for all BTRFS_DIR_ITEM_KEY keys that have an offset\n # in the range [0, 2285968570] (the offset here is th\n---truncated---", "id": "GSD-2021-47072", "modified": "2024-03-01T06:04:48.338118Z", "schema_version": "1.4.0" } }, "namespaces": { "cve.org": { "CVE_data_meta": { "ASSIGNER": "cve@kernel.org", "ID": "CVE-2021-47072", "STATE": "PUBLIC" }, "affects": { "vendor": { "vendor_data": [ { "product": { "product_data": [ { "product_name": "Linux", "version": { "version_data": [ { "version_affected": "\u003c", "version_name": "64d6b281ba4d", "version_value": "6d0924c5b742" }, { "version_value": "not down converted", "x_cve_json_5_version_data": { "defaultStatus": "affected", "versions": [ { "status": "affected", "version": "5.12" }, { "lessThan": "5.12", "status": "unaffected", "version": "0", "versionType": "custom" }, { "lessThanOrEqual": "5.12.*", "status": "unaffected", "version": "5.12.7", "versionType": "custom" }, { "lessThanOrEqual": "*", "status": "unaffected", "version": "5.13", "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\nbtrfs: fix removed dentries still existing after log is synced\n\nWhen we move one inode from one directory to another and both the inode\nand its previous parent directory were logged before, we are not supposed\nto have the dentry for the old parent if we have a power failure after the\nlog is synced. Only the new dentry is supposed to exist.\n\nGenerally this works correctly, however there is a scenario where this is\nnot currently working, because the old parent of the file/directory that\nwas moved is not authoritative for a range that includes the dir index and\ndir item keys of the old dentry. This case is better explained with the\nfollowing example and reproducer:\n\n # The test requires a very specific layout of keys and items in the\n # fs/subvolume btree to trigger the bug. So we want to make sure that\n # on whatever platform we are, we have the same leaf/node size.\n #\n # Currently in btrfs the node/leaf size can not be smaller than the page\n # size (but it can be greater than the page size). So use the largest\n # supported node/leaf size (64K).\n\n $ mkfs.btrfs -f -n 65536 /dev/sdc\n $ mount /dev/sdc /mnt\n\n # \"testdir\" is inode 257.\n $ mkdir /mnt/testdir\n $ chmod 755 /mnt/testdir\n\n # Create several empty files to have the directory \"testdir\" with its\n # items spread over several leaves (7 in this case).\n $ for ((i = 1; i \u003c= 1200; i++)); do\n echo -n \u003e /mnt/testdir/file$i\n done\n\n # Create our test directory \"dira\", inode number 1458, which gets all\n # its items in leaf 7.\n #\n # The BTRFS_DIR_ITEM_KEY item for inode 257 (\"testdir\") that points to\n # the entry named \"dira\" is in leaf 2, while the BTRFS_DIR_INDEX_KEY\n # item that points to that entry is in leaf 3.\n #\n # For this particular filesystem node size (64K), file count and file\n # names, we endup with the directory entry items from inode 257 in\n # leaves 2 and 3, as previously mentioned - what matters for triggering\n # the bug exercised by this test case is that those items are not placed\n # in leaf 1, they must be placed in a leaf different from the one\n # containing the inode item for inode 257.\n #\n # The corresponding BTRFS_DIR_ITEM_KEY and BTRFS_DIR_INDEX_KEY items for\n # the parent inode (257) are the following:\n #\n # item 460 key (257 DIR_ITEM 3724298081) itemoff 48344 itemsize 34\n # location key (1458 INODE_ITEM 0) type DIR\n # transid 6 data_len 0 name_len 4\n # name: dira\n #\n # and:\n #\n # item 771 key (257 DIR_INDEX 1202) itemoff 36673 itemsize 34\n # location key (1458 INODE_ITEM 0) type DIR\n # transid 6 data_len 0 name_len 4\n # name: dira\n\n $ mkdir /mnt/testdir/dira\n\n # Make sure everything done so far is durably persisted.\n $ sync\n\n # Now do a change to inode 257 (\"testdir\") that does not result in\n # COWing leaves 2 and 3 - the leaves that contain the directory items\n # pointing to inode 1458 (directory \"dira\").\n #\n # Changing permissions, the owner/group, updating or adding a xattr,\n # etc, will not change (COW) leaves 2 and 3. So for the sake of\n # simplicity change the permissions of inode 257, which results in\n # updating its inode item and therefore change (COW) only leaf 1.\n\n $ chmod 700 /mnt/testdir\n\n # Now fsync directory inode 257.\n #\n # Since only the first leaf was changed/COWed, we log the inode item of\n # inode 257 and only the dentries found in the first leaf, all have a\n # key type of BTRFS_DIR_ITEM_KEY, and no keys of type\n # BTRFS_DIR_INDEX_KEY, because they sort after the former type and none\n # exist in the first leaf.\n #\n # We also log 3 items that represent ranges for dir items and dir\n # indexes for which the log is authoritative:\n #\n # 1) a key of type BTRFS_DIR_LOG_ITEM_KEY, which indicates the log is\n # authoritative for all BTRFS_DIR_ITEM_KEY keys that have an offset\n # in the range [0, 2285968570] (the offset here is th\n---truncated---" } ] }, "generator": { "engine": "bippy-1e70cc10feda" }, "problemtype": { "problemtype_data": [ { "description": [ { "lang": "eng", "value": "n/a" } ] } ] }, "references": { "reference_data": [ { "name": "https://git.kernel.org/stable/c/6d0924c5b742036b4f20a0ffdf2b6cf3f963f5f6", "refsource": "MISC", "url": "https://git.kernel.org/stable/c/6d0924c5b742036b4f20a0ffdf2b6cf3f963f5f6" }, { "name": "https://git.kernel.org/stable/c/54a40fc3a1da21b52dbf19f72fdc27a2ec740760", "refsource": "MISC", "url": "https://git.kernel.org/stable/c/54a40fc3a1da21b52dbf19f72fdc27a2ec740760" } ] } }, "nvd.nist.gov": { "cve": { "descriptions": [ { "lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: fix removed dentries still existing after log is synced\n\nWhen we move one inode from one directory to another and both the inode\nand its previous parent directory were logged before, we are not supposed\nto have the dentry for the old parent if we have a power failure after the\nlog is synced. Only the new dentry is supposed to exist.\n\nGenerally this works correctly, however there is a scenario where this is\nnot currently working, because the old parent of the file/directory that\nwas moved is not authoritative for a range that includes the dir index and\ndir item keys of the old dentry. This case is better explained with the\nfollowing example and reproducer:\n\n # The test requires a very specific layout of keys and items in the\n # fs/subvolume btree to trigger the bug. So we want to make sure that\n # on whatever platform we are, we have the same leaf/node size.\n #\n # Currently in btrfs the node/leaf size can not be smaller than the page\n # size (but it can be greater than the page size). So use the largest\n # supported node/leaf size (64K).\n\n $ mkfs.btrfs -f -n 65536 /dev/sdc\n $ mount /dev/sdc /mnt\n\n # \"testdir\" is inode 257.\n $ mkdir /mnt/testdir\n $ chmod 755 /mnt/testdir\n\n # Create several empty files to have the directory \"testdir\" with its\n # items spread over several leaves (7 in this case).\n $ for ((i = 1; i \u003c= 1200; i++)); do\n echo -n \u003e /mnt/testdir/file$i\n done\n\n # Create our test directory \"dira\", inode number 1458, which gets all\n # its items in leaf 7.\n #\n # The BTRFS_DIR_ITEM_KEY item for inode 257 (\"testdir\") that points to\n # the entry named \"dira\" is in leaf 2, while the BTRFS_DIR_INDEX_KEY\n # item that points to that entry is in leaf 3.\n #\n # For this particular filesystem node size (64K), file count and file\n # names, we endup with the directory entry items from inode 257 in\n # leaves 2 and 3, as previously mentioned - what matters for triggering\n # the bug exercised by this test case is that those items are not placed\n # in leaf 1, they must be placed in a leaf different from the one\n # containing the inode item for inode 257.\n #\n # The corresponding BTRFS_DIR_ITEM_KEY and BTRFS_DIR_INDEX_KEY items for\n # the parent inode (257) are the following:\n #\n # item 460 key (257 DIR_ITEM 3724298081) itemoff 48344 itemsize 34\n # location key (1458 INODE_ITEM 0) type DIR\n # transid 6 data_len 0 name_len 4\n # name: dira\n #\n # and:\n #\n # item 771 key (257 DIR_INDEX 1202) itemoff 36673 itemsize 34\n # location key (1458 INODE_ITEM 0) type DIR\n # transid 6 data_len 0 name_len 4\n # name: dira\n\n $ mkdir /mnt/testdir/dira\n\n # Make sure everything done so far is durably persisted.\n $ sync\n\n # Now do a change to inode 257 (\"testdir\") that does not result in\n # COWing leaves 2 and 3 - the leaves that contain the directory items\n # pointing to inode 1458 (directory \"dira\").\n #\n # Changing permissions, the owner/group, updating or adding a xattr,\n # etc, will not change (COW) leaves 2 and 3. So for the sake of\n # simplicity change the permissions of inode 257, which results in\n # updating its inode item and therefore change (COW) only leaf 1.\n\n $ chmod 700 /mnt/testdir\n\n # Now fsync directory inode 257.\n #\n # Since only the first leaf was changed/COWed, we log the inode item of\n # inode 257 and only the dentries found in the first leaf, all have a\n # key type of BTRFS_DIR_ITEM_KEY, and no keys of type\n # BTRFS_DIR_INDEX_KEY, because they sort after the former type and none\n # exist in the first leaf.\n #\n # We also log 3 items that represent ranges for dir items and dir\n # indexes for which the log is authoritative:\n #\n # 1) a key of type BTRFS_DIR_LOG_ITEM_KEY, which indicates the log is\n # authoritative for all BTRFS_DIR_ITEM_KEY keys that have an offset\n # in the range [0, 2285968570] (the offset here is th\n---truncated---" } ], "id": "CVE-2021-47072", "lastModified": "2024-03-01T22:22:25.913", "metrics": {}, "published": "2024-03-01T22:15:47.010", "references": [ { "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/54a40fc3a1da21b52dbf19f72fdc27a2ec740760" }, { "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "url": "https://git.kernel.org/stable/c/6d0924c5b742036b4f20a0ffdf2b6cf3f963f5f6" } ], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Awaiting Analysis" } } } }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.