cve-2024-57929
Vulnerability from cvelistv5
Published
2025-01-19 11:52
Modified
2025-02-02 10:15
Severity ?
EPSS score ?
0.07% (0.18271)
Summary
In the Linux kernel, the following vulnerability has been resolved: dm array: fix releasing a faulty array block twice in dm_array_cursor_end When dm_bm_read_lock() fails due to locking or checksum errors, it releases the faulty block implicitly while leaving an invalid output pointer behind. The caller of dm_bm_read_lock() should not operate on this invalid dm_block pointer, or it will lead to undefined result. For example, the dm_array_cursor incorrectly caches the invalid pointer on reading a faulty array block, causing a double release in dm_array_cursor_end(), then hitting the BUG_ON in dm-bufio cache_put(). Reproduce steps: 1. initialize a cache device dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0 65536 linear /dev/sdc 8192" dmsetup create corig --table "0 524288 linear /dev/sdc $262144" dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 dmsetup create cache --table "0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" 2. wipe the second array block offline dmsteup remove cache cmeta cdata corig mapping_root=$(dd if=/dev/sdc bs=1c count=8 skip=192 \ 2>/dev/null | hexdump -e '1/8 "%u\n"') ablock=$(dd if=/dev/sdc bs=1c count=8 skip=$((4096*mapping_root+2056)) \ 2>/dev/null | hexdump -e '1/8 "%u\n"') dd if=/dev/zero of=/dev/sdc bs=4k count=1 seek=$ablock 3. try reopen the cache device dmsetup create cmeta --table "0 8192 linear /dev/sdc 0" dmsetup create cdata --table "0 65536 linear /dev/sdc 8192" dmsetup create corig --table "0 524288 linear /dev/sdc $262144" dmsetup create cache --table "0 524288 cache /dev/mapper/cmeta \ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0" Kernel logs: (snip) device-mapper: array: array_block_check failed: blocknr 0 != wanted 10 device-mapper: block manager: array validator check failed for block 10 device-mapper: array: get_ablock failed device-mapper: cache metadata: dm_array_cursor_next for mapping failed ------------[ cut here ]------------ kernel BUG at drivers/md/dm-bufio.c:638! Fix by setting the cached block pointer to NULL on errors. In addition to the reproducer described above, this fix can be verified using the "array_cursor/damaged" test in dm-unit: dm-unit run /pdata/array_cursor/damaged --kernel-dir <KERNEL_DIR>
Impacted products
Vendor Product Version
Linux Linux Version: fdd1315aa5f022fe6574efdc2d9535f75a0ee255
Version: fdd1315aa5f022fe6574efdc2d9535f75a0ee255
Version: fdd1315aa5f022fe6574efdc2d9535f75a0ee255
Version: fdd1315aa5f022fe6574efdc2d9535f75a0ee255
Version: fdd1315aa5f022fe6574efdc2d9535f75a0ee255
Version: fdd1315aa5f022fe6574efdc2d9535f75a0ee255
Version: fdd1315aa5f022fe6574efdc2d9535f75a0ee255
Create a notification for this product.
   Linux Linux Version: 4.9
Create a notification for this product.
Show details on NVD website


{
   containers: {
      cna: {
         affected: [
            {
               defaultStatus: "unaffected",
               product: "Linux",
               programFiles: [
                  "drivers/md/persistent-data/dm-array.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     lessThan: "9c7c03d0e926762adf3a3a0ba86156fb5e19538b",
                     status: "affected",
                     version: "fdd1315aa5f022fe6574efdc2d9535f75a0ee255",
                     versionType: "git",
                  },
                  {
                     lessThan: "fc1ef07c3522e257e32702954f265debbcb096a7",
                     status: "affected",
                     version: "fdd1315aa5f022fe6574efdc2d9535f75a0ee255",
                     versionType: "git",
                  },
                  {
                     lessThan: "738994872d77e189b2d13c501a1d145e95d98f46",
                     status: "affected",
                     version: "fdd1315aa5f022fe6574efdc2d9535f75a0ee255",
                     versionType: "git",
                  },
                  {
                     lessThan: "e477021d252c007f0c6d45b5d13d341efed03979",
                     status: "affected",
                     version: "fdd1315aa5f022fe6574efdc2d9535f75a0ee255",
                     versionType: "git",
                  },
                  {
                     lessThan: "6002bec5354f86d1a2df21468f68e3ec03ede9da",
                     status: "affected",
                     version: "fdd1315aa5f022fe6574efdc2d9535f75a0ee255",
                     versionType: "git",
                  },
                  {
                     lessThan: "017c4470bff53585370028fec9341247bad358ff",
                     status: "affected",
                     version: "fdd1315aa5f022fe6574efdc2d9535f75a0ee255",
                     versionType: "git",
                  },
                  {
                     lessThan: "f2893c0804d86230ffb8f1c8703fdbb18648abc8",
                     status: "affected",
                     version: "fdd1315aa5f022fe6574efdc2d9535f75a0ee255",
                     versionType: "git",
                  },
               ],
            },
            {
               defaultStatus: "affected",
               product: "Linux",
               programFiles: [
                  "drivers/md/persistent-data/dm-array.c",
               ],
               repo: "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
               vendor: "Linux",
               versions: [
                  {
                     status: "affected",
                     version: "4.9",
                  },
                  {
                     lessThan: "4.9",
                     status: "unaffected",
                     version: "0",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "5.4.*",
                     status: "unaffected",
                     version: "5.4.290",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "5.10.*",
                     status: "unaffected",
                     version: "5.10.234",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "5.15.*",
                     status: "unaffected",
                     version: "5.15.177",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.1.*",
                     status: "unaffected",
                     version: "6.1.125",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.6.*",
                     status: "unaffected",
                     version: "6.6.72",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "6.12.*",
                     status: "unaffected",
                     version: "6.12.10",
                     versionType: "semver",
                  },
                  {
                     lessThanOrEqual: "*",
                     status: "unaffected",
                     version: "6.13",
                     versionType: "original_commit_for_fix",
                  },
               ],
            },
         ],
         descriptions: [
            {
               lang: "en",
               value: "In the Linux kernel, the following vulnerability has been resolved:\n\ndm array: fix releasing a faulty array block twice in dm_array_cursor_end\n\nWhen dm_bm_read_lock() fails due to locking or checksum errors, it\nreleases the faulty block implicitly while leaving an invalid output\npointer behind. The caller of dm_bm_read_lock() should not operate on\nthis invalid dm_block pointer, or it will lead to undefined result.\nFor example, the dm_array_cursor incorrectly caches the invalid pointer\non reading a faulty array block, causing a double release in\ndm_array_cursor_end(), then hitting the BUG_ON in dm-bufio cache_put().\n\nReproduce steps:\n\n1. initialize a cache device\n\ndmsetup create cmeta --table \"0 8192 linear /dev/sdc 0\"\ndmsetup create cdata --table \"0 65536 linear /dev/sdc 8192\"\ndmsetup create corig --table \"0 524288 linear /dev/sdc $262144\"\ndd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1\ndmsetup create cache --table \"0 524288 cache /dev/mapper/cmeta \\\n/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0\"\n\n2. wipe the second array block offline\n\ndmsteup remove cache cmeta cdata corig\nmapping_root=$(dd if=/dev/sdc bs=1c count=8 skip=192 \\\n2>/dev/null | hexdump -e '1/8 \"%u\\n\"')\nablock=$(dd if=/dev/sdc bs=1c count=8 skip=$((4096*mapping_root+2056)) \\\n2>/dev/null | hexdump -e '1/8 \"%u\\n\"')\ndd if=/dev/zero of=/dev/sdc bs=4k count=1 seek=$ablock\n\n3. try reopen the cache device\n\ndmsetup create cmeta --table \"0 8192 linear /dev/sdc 0\"\ndmsetup create cdata --table \"0 65536 linear /dev/sdc 8192\"\ndmsetup create corig --table \"0 524288 linear /dev/sdc $262144\"\ndmsetup create cache --table \"0 524288 cache /dev/mapper/cmeta \\\n/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0\"\n\nKernel logs:\n\n(snip)\ndevice-mapper: array: array_block_check failed: blocknr 0 != wanted 10\ndevice-mapper: block manager: array validator check failed for block 10\ndevice-mapper: array: get_ablock failed\ndevice-mapper: cache metadata: dm_array_cursor_next for mapping failed\n------------[ cut here ]------------\nkernel BUG at drivers/md/dm-bufio.c:638!\n\nFix by setting the cached block pointer to NULL on errors.\n\nIn addition to the reproducer described above, this fix can be\nverified using the \"array_cursor/damaged\" test in dm-unit:\n  dm-unit run /pdata/array_cursor/damaged --kernel-dir <KERNEL_DIR>",
            },
         ],
         providerMetadata: {
            dateUpdated: "2025-02-02T10:15:47.756Z",
            orgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            shortName: "Linux",
         },
         references: [
            {
               url: "https://git.kernel.org/stable/c/9c7c03d0e926762adf3a3a0ba86156fb5e19538b",
            },
            {
               url: "https://git.kernel.org/stable/c/fc1ef07c3522e257e32702954f265debbcb096a7",
            },
            {
               url: "https://git.kernel.org/stable/c/738994872d77e189b2d13c501a1d145e95d98f46",
            },
            {
               url: "https://git.kernel.org/stable/c/e477021d252c007f0c6d45b5d13d341efed03979",
            },
            {
               url: "https://git.kernel.org/stable/c/6002bec5354f86d1a2df21468f68e3ec03ede9da",
            },
            {
               url: "https://git.kernel.org/stable/c/017c4470bff53585370028fec9341247bad358ff",
            },
            {
               url: "https://git.kernel.org/stable/c/f2893c0804d86230ffb8f1c8703fdbb18648abc8",
            },
         ],
         title: "dm array: fix releasing a faulty array block twice in dm_array_cursor_end",
         x_generator: {
            engine: "bippy-5f407fcff5a0",
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      assignerShortName: "Linux",
      cveId: "CVE-2024-57929",
      datePublished: "2025-01-19T11:52:46.096Z",
      dateReserved: "2025-01-19T11:50:08.376Z",
      dateUpdated: "2025-02-02T10:15:47.756Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2024-57929\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-01-19T12:15:27.013\",\"lastModified\":\"2025-02-02T11:15:14.227\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ndm array: fix releasing a faulty array block twice in dm_array_cursor_end\\n\\nWhen dm_bm_read_lock() fails due to locking or checksum errors, it\\nreleases the faulty block implicitly while leaving an invalid output\\npointer behind. The caller of dm_bm_read_lock() should not operate on\\nthis invalid dm_block pointer, or it will lead to undefined result.\\nFor example, the dm_array_cursor incorrectly caches the invalid pointer\\non reading a faulty array block, causing a double release in\\ndm_array_cursor_end(), then hitting the BUG_ON in dm-bufio cache_put().\\n\\nReproduce steps:\\n\\n1. initialize a cache device\\n\\ndmsetup create cmeta --table \\\"0 8192 linear /dev/sdc 0\\\"\\ndmsetup create cdata --table \\\"0 65536 linear /dev/sdc 8192\\\"\\ndmsetup create corig --table \\\"0 524288 linear /dev/sdc $262144\\\"\\ndd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1\\ndmsetup create cache --table \\\"0 524288 cache /dev/mapper/cmeta \\\\\\n/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0\\\"\\n\\n2. wipe the second array block offline\\n\\ndmsteup remove cache cmeta cdata corig\\nmapping_root=$(dd if=/dev/sdc bs=1c count=8 skip=192 \\\\\\n2>/dev/null | hexdump -e '1/8 \\\"%u\\\\n\\\"')\\nablock=$(dd if=/dev/sdc bs=1c count=8 skip=$((4096*mapping_root+2056)) \\\\\\n2>/dev/null | hexdump -e '1/8 \\\"%u\\\\n\\\"')\\ndd if=/dev/zero of=/dev/sdc bs=4k count=1 seek=$ablock\\n\\n3. try reopen the cache device\\n\\ndmsetup create cmeta --table \\\"0 8192 linear /dev/sdc 0\\\"\\ndmsetup create cdata --table \\\"0 65536 linear /dev/sdc 8192\\\"\\ndmsetup create corig --table \\\"0 524288 linear /dev/sdc $262144\\\"\\ndmsetup create cache --table \\\"0 524288 cache /dev/mapper/cmeta \\\\\\n/dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0\\\"\\n\\nKernel logs:\\n\\n(snip)\\ndevice-mapper: array: array_block_check failed: blocknr 0 != wanted 10\\ndevice-mapper: block manager: array validator check failed for block 10\\ndevice-mapper: array: get_ablock failed\\ndevice-mapper: cache metadata: dm_array_cursor_next for mapping failed\\n------------[ cut here ]------------\\nkernel BUG at drivers/md/dm-bufio.c:638!\\n\\nFix by setting the cached block pointer to NULL on errors.\\n\\nIn addition to the reproducer described above, this fix can be\\nverified using the \\\"array_cursor/damaged\\\" test in dm-unit:\\n  dm-unit run /pdata/array_cursor/damaged --kernel-dir <KERNEL_DIR>\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: dm array: se corrige la liberación de un bloque de matriz defectuoso dos veces en dm_array_cursor_end Cuando dm_bm_read_lock() falla debido a errores de bloqueo o suma de comprobación, libera el bloque defectuoso implícitamente mientras deja atrás un puntero de salida no válido. El llamador de dm_bm_read_lock() no debe operar en este puntero dm_block no válido, o conducirá a un resultado indefinido. Por ejemplo, dm_array_cursor almacena en caché incorrectamente el puntero no válido al leer un bloque de matriz defectuoso, lo que causa una doble liberación en dm_array_cursor_end(), y luego alcanza el BUG_ON en dm-bufio cache_put(). Reproducir los pasos: 1. inicializar un dispositivo de caché dmsetup create cmeta --table \\\"0 8192 linear /dev/sdc 0\\\" dmsetup create cdata --table \\\"0 65536 linear /dev/sdc 8192\\\" dmsetup create corig --table \\\"0 524288 linear /dev/sdc $262144\\\" dd if=/dev/zero of=/dev/mapper/cmeta bs=4k count=1 dmsetup create cache --table \\\"0 524288 cache /dev/mapper/cmeta \\\\ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0\\\" 2. borrar el segundo bloque de matriz sin conexión dmsteup remove cache cmeta cdata corig mapping_root=$(dd if=/dev/sdc bs=1c count=8 skip=192 \\\\ 2&gt;/dev/null | hexdump -e '1/8 \\\"%u\\\\n\\\"') ablock=$(dd if=/dev/sdc bs=1c count=8 skip=$((4096*mapping_root+2056)) \\\\ 2&gt;/dev/null | hexdump -e '1/8 \\\"%u\\\\n\\\"') dd if=/dev/zero of=/dev/sdc bs=4k count=1 seek=$ablock 3. Intente volver a abrir el dispositivo de caché dmsetup create cmeta --table \\\"0 8192 lineal /dev/sdc 0\\\" dmsetup create cdata --table \\\"0 65536 lineal /dev/sdc 8192\\\" dmsetup create corig --table \\\"0 524288 lineal /dev/sdc $262144\\\" dmsetup create cache --table \\\"0 524288 caché /dev/mapper/cmeta \\\\ /dev/mapper/cdata /dev/mapper/corig 128 2 metadata2 writethrough smq 0\\\" Registros del kernel: (snip) device-mapper: array: array_block_check failed: blocknr 0 != wanted 10 device-mapper: block manager: array validator check failed for block 10 device-mapper: array: get_ablock failed device-mapper: cache metadata: dm_array_cursor_next for mapping failed ------------[ corte aquí ]------------ ¡ERROR del kernel en drivers/md/dm-bufio.c:638! Se corrige configurando el puntero de bloque en caché en NULL en caso de errores. Además del reproductor descrito anteriormente, esta corrección se puede verificar utilizando la prueba \\\"array_cursor/damaged\\\" en dm-unit: dm-unit run /pdata/array_cursor/damaged --kernel-dir \"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/017c4470bff53585370028fec9341247bad358ff\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/6002bec5354f86d1a2df21468f68e3ec03ede9da\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/738994872d77e189b2d13c501a1d145e95d98f46\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/9c7c03d0e926762adf3a3a0ba86156fb5e19538b\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/e477021d252c007f0c6d45b5d13d341efed03979\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/f2893c0804d86230ffb8f1c8703fdbb18648abc8\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/fc1ef07c3522e257e32702954f265debbcb096a7\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}",
   },
}


Log in or create an account to share your comment.

Security Advisory comment format.

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

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



Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.