CVE-2024-36027

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2024-36027", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "state": "PUBLISHED", "assignerShortName": "Linux", "dateReserved": "2024-05-17T13:50:33.159Z", "datePublished": "2024-05-30T15:10:17.129Z", "dateUpdated": "2026-08-05T11:31:41.392Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T11:31:41.392Z"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: zoned: do not flag ZEROOUT on non-dirty extent buffer\n\nBtrfs clears the content of an extent buffer marked as\nEXTENT_BUFFER_ZONED_ZEROOUT before the bio submission. This mechanism is\nintroduced to prevent a write hole of an extent buffer, which is once\nallocated, marked dirty, but turns out unnecessary and cleaned up within\none transaction operation.\n\nCurrently, btrfs_clear_buffer_dirty() marks the extent buffer as\nEXTENT_BUFFER_ZONED_ZEROOUT, and skips the entry function. If this call\nhappens while the buffer is under IO (with the WRITEBACK flag set,\nwithout the DIRTY flag), we can add the ZEROOUT flag and clear the\nbuffer's content just before a bio submission. As a result:\n\n1) it can lead to adding faulty delayed reference item which leads to a\n FS corrupted (EUCLEAN) error, and\n\n2) it writes out cleared tree node on disk\n\nThe former issue is previously discussed in [1]. The corruption happens\nwhen it runs a delayed reference update. So, on-disk data is safe.\n\n[1] https://lore.kernel.org/linux-btrfs/3f4f2a0ff1a6c818050434288925bdcf3cd719e5.1709124777.git.naohiro.aota@wdc.com/\n\nThe latter one can reach on-disk data. But, as that node is already\nprocessed by btrfs_clear_buffer_dirty(), that will be invalidated in the\nnext transaction commit anyway. So, the chance of hitting the corruption\nis relatively small.\n\nAnyway, we should skip flagging ZEROOUT on a non-DIRTY extent buffer, to\nkeep the content under IO intact."}], "metrics": [{"cvssV3_1": {"version": "3.1", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H", "baseScore": 7.1, "baseSeverity": "HIGH"}, "scenarios": [{"lang": "en", "value": "AV:L - The vulnerable path is reached through ordinary filesystem syscalls (write, unlink, fsync) on a locally mounted btrfs, driving tree COW/free and metadata writeback. No network protocol handler is involved.\nAC:L - The attacker controls both sides of the race \u2014 metadata churn produces the btrfs_clear_buffer_dirty() calls while fsync()/dirty-metadata thresholds produce concurrent writeback \u2014 and lock_extent_buffer_for_io() drops the tree lock before bio submission, leaving the window completely unguarded; clean_log_buffer() hits it on every log commit, so it can be hammered continuously.\nPR:L - Any unprivileged local user with write access to the btrfs mount can drive tree-block frees and fsync-triggered metadata writeback; there is no capability check, root requirement, or ioctl gate anywhere on the path.\nUI:N - The attacker performs the entire sequence themselves with a self-driven write/delete/fsync workload; no other user or administrator has to take any action.\nS:U - The corruption is confined to the kernel's own filesystem metadata and the mounted volume, within a single security authority. No hypervisor, IOMMU, or sandbox boundary is crossed.\nC:N - The buffer is overwritten with zeros rather than exposed \u2014 there is no out-of-bounds read, no kernel pointer leak, and the zeroed block is written with an uncomputed checksum so a subsequent read fails verification with EIO instead of returning data.\nI:H - A zeroed tree node reaches persistent storage and faulty delayed reference items corrupt the extent tree, destroying shared btrfs metadata (including log-tree nodes holding fsync-promised data) that belongs to every file and user on the volume, not just the attacker.\nA:H - The faulty delayed ref triggers btrfs_abort_transaction(-EUCLEAN), which routes through __btrfs_handle_fs_error() to btrfs_set_sb_rdonly() and forces the filesystem read-only, while the BUG_ON sites in the backref update path can panic the kernel outright and on-disk metadata/log corruption can leave the volume unmountable."}]}], "affected": [{"product": "Linux", "vendor": "Linux", "defaultStatus": "unaffected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["fs/btrfs/extent_io.c"], "versions": [{"version": "aa6313e6ff2bfbf736a2739047bba355d8241584", "lessThan": "f4b994fccbb6f294c4b31a6ca0114b09f7245043", "status": "affected", "versionType": "git"}, {"version": "aa6313e6ff2bfbf736a2739047bba355d8241584", "lessThan": "68879386180c0efd5a11e800b0525a01068c9457", "status": "affected", "versionType": "git"}]}, {"product": "Linux", "vendor": "Linux", "defaultStatus": "affected", "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "programFiles": ["fs/btrfs/extent_io.c"], "versions": [{"version": "6.8", "status": "affected"}, {"version": "0", "lessThan": "6.8", "status": "unaffected", "versionType": "semver"}, {"version": "6.8.8", "lessThanOrEqual": "6.8.*", "status": "unaffected", "versionType": "semver"}, {"version": "6.9", "lessThanOrEqual": "*", "status": "unaffected", "versionType": "original_commit_for_fix"}]}], "cpeApplicability": [{"nodes": [{"operator": "OR", "negate": false, "cpeMatch": [{"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.8", "versionEndExcluding": "6.8.8"}, {"vulnerable": true, "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "versionStartIncluding": "6.8", "versionEndExcluding": "6.9"}]}]}], "references": [{"url": "https://git.kernel.org/stable/c/f4b994fccbb6f294c4b31a6ca0114b09f7245043"}, {"url": "https://git.kernel.org/stable/c/68879386180c0efd5a11e800b0525a01068c9457"}], "title": "btrfs: zoned: do not flag ZEROOUT on non-dirty extent buffer", "x_generator": {"engine": "bippy-1.2.0"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2024-06-17T17:34:25.215751Z", "id": "CVE-2024-36027", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2024-06-17T17:34:35.864Z"}}, {"providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-02T03:30:12.531Z"}, "title": "CVE Program Container", "references": [{"url": "https://git.kernel.org/stable/c/f4b994fccbb6f294c4b31a6ca0114b09f7245043", "tags": ["x_transferred"]}, {"url": "https://git.kernel.org/stable/c/68879386180c0efd5a11e800b0525a01068c9457", "tags": ["x_transferred"]}]}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CVE Program Container", "references": [{"url": "https://git.kernel.org/stable/c/f4b994fccbb6f294c4b31a6ca0114b09f7245043", "tags": ["x_transferred"]}, {"url": "https://git.kernel.org/stable/c/68879386180c0efd5a11e800b0525a01068c9457", "tags": ["x_transferred"]}], "providerMetadata": {"orgId": "af854a3a-2127-422b-91ae-364da2661108", "shortName": "CVE", "dateUpdated": "2024-08-02T03:30:12.531Z"}}, {"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2024-36027", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2024-06-17T17:34:25.215751Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2024-06-17T17:34:26.272Z"}}], "cna": {"title": "btrfs: zoned: do not flag ZEROOUT on non-dirty extent buffer", "metrics": [{"cvssV3_1": {"version": "3.1", "baseScore": 7.1, "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H"}, "scenarios": [{"lang": "en", "value": "AV:L - The vulnerable path is reached through ordinary filesystem syscalls (write, unlink, fsync) on a locally mounted btrfs, driving tree COW/free and metadata writeback. No network protocol handler is involved.\nAC:L - The attacker controls both sides of the race \u2014 metadata churn produces the btrfs_clear_buffer_dirty() calls while fsync()/dirty-metadata thresholds produce concurrent writeback \u2014 and lock_extent_buffer_for_io() drops the tree lock before bio submission, leaving the window completely unguarded; clean_log_buffer() hits it on every log commit, so it can be hammered continuously.\nPR:L - Any unprivileged local user with write access to the btrfs mount can drive tree-block frees and fsync-triggered metadata writeback; there is no capability check, root requirement, or ioctl gate anywhere on the path.\nUI:N - The attacker performs the entire sequence themselves with a self-driven write/delete/fsync workload; no other user or administrator has to take any action.\nS:U - The corruption is confined to the kernel's own filesystem metadata and the mounted volume, within a single security authority. No hypervisor, IOMMU, or sandbox boundary is crossed.\nC:N - The buffer is overwritten with zeros rather than exposed \u2014 there is no out-of-bounds read, no kernel pointer leak, and the zeroed block is written with an uncomputed checksum so a subsequent read fails verification with EIO instead of returning data.\nI:H - A zeroed tree node reaches persistent storage and faulty delayed reference items corrupt the extent tree, destroying shared btrfs metadata (including log-tree nodes holding fsync-promised data) that belongs to every file and user on the volume, not just the attacker.\nA:H - The faulty delayed ref triggers btrfs_abort_transaction(-EUCLEAN), which routes through __btrfs_handle_fs_error() to btrfs_set_sb_rdonly() and forces the filesystem read-only, while the BUG_ON sites in the backref update path can panic the kernel outright and on-disk metadata/log corruption can leave the volume unmountable."}]}], "affected": [{"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "aa6313e6ff2bfbf736a2739047bba355d8241584", "lessThan": "f4b994fccbb6f294c4b31a6ca0114b09f7245043", "versionType": "git"}, {"status": "affected", "version": "aa6313e6ff2bfbf736a2739047bba355d8241584", "lessThan": "68879386180c0efd5a11e800b0525a01068c9457", "versionType": "git"}], "programFiles": ["fs/btrfs/extent_io.c"], "defaultStatus": "unaffected"}, {"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "product": "Linux", "versions": [{"status": "affected", "version": "6.8"}, {"status": "unaffected", "version": "0", "lessThan": "6.8", "versionType": "semver"}, {"status": "unaffected", "version": "6.8.8", "versionType": "semver", "lessThanOrEqual": "6.8.*"}, {"status": "unaffected", "version": "6.9", "versionType": "original_commit_for_fix", "lessThanOrEqual": "*"}], "programFiles": ["fs/btrfs/extent_io.c"], "defaultStatus": "affected"}], "references": [{"url": "https://git.kernel.org/stable/c/f4b994fccbb6f294c4b31a6ca0114b09f7245043"}, {"url": "https://git.kernel.org/stable/c/68879386180c0efd5a11e800b0525a01068c9457"}], "x_generator": {"engine": "bippy-1.2.0"}, "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: zoned: do not flag ZEROOUT on non-dirty extent buffer\n\nBtrfs clears the content of an extent buffer marked as\nEXTENT_BUFFER_ZONED_ZEROOUT before the bio submission. This mechanism is\nintroduced to prevent a write hole of an extent buffer, which is once\nallocated, marked dirty, but turns out unnecessary and cleaned up within\none transaction operation.\n\nCurrently, btrfs_clear_buffer_dirty() marks the extent buffer as\nEXTENT_BUFFER_ZONED_ZEROOUT, and skips the entry function. If this call\nhappens while the buffer is under IO (with the WRITEBACK flag set,\nwithout the DIRTY flag), we can add the ZEROOUT flag and clear the\nbuffer's content just before a bio submission. As a result:\n\n1) it can lead to adding faulty delayed reference item which leads to a\n FS corrupted (EUCLEAN) error, and\n\n2) it writes out cleared tree node on disk\n\nThe former issue is previously discussed in [1]. The corruption happens\nwhen it runs a delayed reference update. So, on-disk data is safe.\n\n[1] https://lore.kernel.org/linux-btrfs/3f4f2a0ff1a6c818050434288925bdcf3cd719e5.1709124777.git.naohiro.aota@wdc.com/\n\nThe latter one can reach on-disk data. But, as that node is already\nprocessed by btrfs_clear_buffer_dirty(), that will be invalidated in the\nnext transaction commit anyway. So, the chance of hitting the corruption\nis relatively small.\n\nAnyway, we should skip flagging ZEROOUT on a non-DIRTY extent buffer, to\nkeep the content under IO intact."}], "cpeApplicability": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.8.8", "versionStartIncluding": "6.8"}, {"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "6.9", "versionStartIncluding": "6.8"}], "operator": "OR"}]}], "providerMetadata": {"orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "shortName": "Linux", "dateUpdated": "2026-08-05T11:31:41.392Z"}}}, "cveMetadata": {"cveId": "CVE-2024-36027", "state": "PUBLISHED", "dateUpdated": "2026-08-05T11:31:41.392Z", "dateReserved": "2024-05-17T13:50:33.159Z", "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "datePublished": "2024-05-30T15:10:17.129Z", "assignerShortName": "Linux"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"defaultStatus": "unaffected", "product": "Linux", "programFiles": ["fs/btrfs/extent_io.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"lessThan": "f4b994fccbb6f294c4b31a6ca0114b09f7245043", "status": "affected", "version": "aa6313e6ff2bfbf736a2739047bba355d8241584", "versionType": "git"}, {"lessThan": "68879386180c0efd5a11e800b0525a01068c9457", "status": "affected", "version": "aa6313e6ff2bfbf736a2739047bba355d8241584", "versionType": "git"}]}, {"defaultStatus": "affected", "product": "Linux", "programFiles": ["fs/btrfs/extent_io.c"], "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git", "vendor": "Linux", "versions": [{"status": "affected", "version": "6.8"}, {"lessThan": "6.8", "status": "unaffected", "version": "0", "versionType": "semver"}, {"lessThanOrEqual": "6.8.*", "status": "unaffected", "version": "6.8.8", "versionType": "semver"}, {"lessThanOrEqual": "*", "status": "unaffected", "version": "6.9", "versionType": "original_commit_for_fix"}]}], "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "configurations": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*", "matchCriteriaId": "A6B3F478-AAC3-4675-897F-870080589B51", "versionEndExcluding": "6.8.8", "versionStartIncluding": "6.8", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc1:*:*:*:*:*:*", "matchCriteriaId": "22BEDD49-2C6D-402D-9DBF-6646F6ECD10B", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc2:*:*:*:*:*:*", "matchCriteriaId": "DF73CB2A-DFFD-46FB-9BFE-AA394F27EA37", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc3:*:*:*:*:*:*", "matchCriteriaId": "52048DDA-FC5A-4363-95A0-A6357B4D7F8C", "vulnerable": true}, {"criteria": "cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:*", "matchCriteriaId": "A06B2CCF-3F43-4FA9-8773-C83C3F5764B2", "vulnerable": true}], "negate": false, "operator": "OR"}]}], "cveTags": [], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nbtrfs: zoned: do not flag ZEROOUT on non-dirty extent buffer\n\nBtrfs clears the content of an extent buffer marked as\nEXTENT_BUFFER_ZONED_ZEROOUT before the bio submission. This mechanism is\nintroduced to prevent a write hole of an extent buffer, which is once\nallocated, marked dirty, but turns out unnecessary and cleaned up within\none transaction operation.\n\nCurrently, btrfs_clear_buffer_dirty() marks the extent buffer as\nEXTENT_BUFFER_ZONED_ZEROOUT, and skips the entry function. If this call\nhappens while the buffer is under IO (with the WRITEBACK flag set,\nwithout the DIRTY flag), we can add the ZEROOUT flag and clear the\nbuffer's content just before a bio submission. As a result:\n\n1) it can lead to adding faulty delayed reference item which leads to a\n FS corrupted (EUCLEAN) error, and\n\n2) it writes out cleared tree node on disk\n\nThe former issue is previously discussed in [1]. The corruption happens\nwhen it runs a delayed reference update. So, on-disk data is safe.\n\n[1] https://lore.kernel.org/linux-btrfs/3f4f2a0ff1a6c818050434288925bdcf3cd719e5.1709124777.git.naohiro.aota@wdc.com/\n\nThe latter one can reach on-disk data. But, as that node is already\nprocessed by btrfs_clear_buffer_dirty(), that will be invalidated in the\nnext transaction commit anyway. So, the chance of hitting the corruption\nis relatively small.\n\nAnyway, we should skip flagging ZEROOUT on a non-DIRTY extent buffer, to\nkeep the content under IO intact."}, {"lang": "es", "value": "En el kernel de Linux, se resolvi\u00f3 la siguiente vulnerabilidad: btrfs: zonado: no marcar ZEROOUT en el b\u00fafer de extensi\u00f3n no sucio Btrfs borra el contenido de un b\u00fafer de extensi\u00f3n marcado como EXTENT_BUFFER_ZONED_ZEROOUT antes del env\u00edo de la biograf\u00eda. Este mecanismo se introduce para evitar un agujero de escritura en un b\u00fafer de extensi\u00f3n, que una vez asignado, se marca como sucio, pero resulta innecesario y se limpia dentro de una operaci\u00f3n de transacci\u00f3n. Actualmente, btrfs_clear_buffer_dirty() marca el b\u00fafer de extensi\u00f3n como EXTENT_BUFFER_ZONED_ZEROOUT y omite la funci\u00f3n de entrada. Si esta llamada ocurre mientras el b\u00fafer est\u00e1 bajo IO (con el indicador WRITEBACK configurado, sin el indicador DIRTY), podemos agregar el indicador ZEROOUT y borrar el contenido del b\u00fafer justo antes de enviar una biograf\u00eda. Como resultado: 1) puede provocar que se agregue un elemento de referencia retrasado defectuoso, lo que provoca un error de FS da\u00f1ado (EUCLEAN), y 2) escribe el nodo del \u00e1rbol borrado en el disco. El primer problema se analiz\u00f3 anteriormente en [1]. La corrupci\u00f3n ocurre cuando ejecuta una actualizaci\u00f3n de referencia retrasada. Por lo tanto, los datos en el disco est\u00e1n seguros. [1] https://lore.kernel.org/linux-btrfs/3f4f2a0ff1a6c818050434288925bdcf3cd719e5.1709124777.git.naohiro.aota@wdc.com/ Este \u00faltimo puede acceder a datos en disco. Pero, como ese nodo ya est\u00e1 procesado por btrfs_clear_buffer_dirty(), de todos modos se invalidar\u00e1 en la pr\u00f3xima confirmaci\u00f3n de transacci\u00f3n. Por lo tanto, la posibilidad de combatir la corrupci\u00f3n es relativamente peque\u00f1a. De todos modos, debemos omitir marcar ZEROOUT en un b\u00fafer de extensi\u00f3n que no sea DIRTY, para mantener intacto el contenido bajo IO."}], "id": "CVE-2024-36027", "lastModified": "2026-08-04T11:18:24.157", "metrics": {"cvssMetricV31": [{"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "baseScore": 7.1, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 1.8, "impactScore": 5.2, "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "type": "Secondary"}, {"cvssData": {"attackComplexity": "LOW", "attackVector": "LOCAL", "availabilityImpact": "HIGH", "baseScore": 7.1, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "HIGH", "privilegesRequired": "LOW", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H", "version": "3.1"}, "exploitabilityScore": 1.8, "impactScore": 5.2, "source": "nvd@nist.gov", "type": "Primary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2024-36027", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2024-06-17T17:34:25.215751Z", "version": "2.0.3"}}]}, "published": "2024-05-30T16:15:11.070", "references": [{"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/68879386180c0efd5a11e800b0525a01068c9457"}, {"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/f4b994fccbb6f294c4b31a6ca0114b09f7245043"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/68879386180c0efd5a11e800b0525a01068c9457"}, {"source": "af854a3a-2127-422b-91ae-364da2661108", "tags": ["Patch"], "url": "https://git.kernel.org/stable/c/f4b994fccbb6f294c4b31a6ca0114b09f7245043"}], "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67", "vulnStatus": "Modified", "weaknesses": [{"description": [{"lang": "en", "value": "NVD-CWE-noinfo"}], "source": "nvd@nist.gov", "type": "Primary"}]}

{"bugzilla": {"description": "kernel: btrfs: zoned: do not flag ZEROOUT on non-dirty extent buffer", "id": "2284415", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2284415"}, "csaw": false, "cvss3": {"cvss3_base_score": "5.5", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H", "status": "draft"}, "cwe": "CWE-367", "details": ["In the Linux kernel, the following vulnerability has been resolved:\nbtrfs: zoned: do not flag ZEROOUT on non-dirty extent buffer\nBtrfs clears the content of an extent buffer marked as\nEXTENT_BUFFER_ZONED_ZEROOUT before the bio submission. This mechanism is\nintroduced to prevent a write hole of an extent buffer, which is once\nallocated, marked dirty, but turns out unnecessary and cleaned up within\none transaction operation.\nCurrently, btrfs_clear_buffer_dirty() marks the extent buffer as\nEXTENT_BUFFER_ZONED_ZEROOUT, and skips the entry function. If this call\nhappens while the buffer is under IO (with the WRITEBACK flag set,\nwithout the DIRTY flag), we can add the ZEROOUT flag and clear the\nbuffer's content just before a bio submission. As a result:\n1) it can lead to adding faulty delayed reference item which leads to a\nFS corrupted (EUCLEAN) error, and\n2) it writes out cleared tree node on disk\nThe former issue is previously discussed in [1]. The corruption happens\nwhen it runs a delayed reference update. So, on-disk data is safe.\n[1] https://lore.kernel.org/linux-btrfs/3f4f2a0ff1a6c818050434288925bdcf3cd719e5.1709124777.git.naohiro.aota@wdc.com/\nThe latter one can reach on-disk data. But, as that node is already\nprocessed by btrfs_clear_buffer_dirty(), that will be invalidated in the\nnext transaction commit anyway. So, the chance of hitting the corruption\nis relatively small.\nAnyway, we should skip flagging ZEROOUT on a non-DIRTY extent buffer, to\nkeep the content under IO intact."], "name": "CVE-2024-36027", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:6", "fix_state": "Out of support scope", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 6"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Out of support scope", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:7", "fix_state": "Out of support scope", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 7"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "kernel", "product_name": "Red Hat Enterprise Linux 9"}, {"cpe": "cpe:/o:redhat:enterprise_linux:9", "fix_state": "Not affected", "package_name": "kernel-rt", "product_name": "Red Hat Enterprise Linux 9"}], "public_date": "2024-05-30T00:00:00Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2024-36027\nhttps://nvd.nist.gov/vuln/detail/CVE-2024-36027\nhttps://lore.kernel.org/linux-cve-announce/2024053021-CVE-2024-36027-2bf9@gregkh/T"], "threat_severity": "Moderate"}

{"created": "2025-07-12T15:42:32.643380+00:00", "updated": "2025-07-12T15:42:32.643428+00:00", "vendors": ["linux", "linux$PRODUCT$linux_kernel"]}