cve-2021-47406
Vulnerability from cvelistv5
Published
2024-05-21 15:03
Modified
2024-11-04 12:05
Severity ?
5.5 (Medium) - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Summary
ext4: add error checking to ext4_ext_replay_set_iblocks()
References
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/1fd95c05d8f742abfe906620780aee4dbe1a2db0
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/27e10c5d31ff1d222c7f797f1ee96d422859ba67
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/a63474dbf692dd09b50fed592bc41f6de5f102fc
Impacted products
LinuxLinux
LinuxLinux
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "cvssV3_1": {
              "attackComplexity": "LOW",
              "attackVector": "LOCAL",
              "availabilityImpact": "HIGH",
              "baseScore": 5.5,
              "baseSeverity": "MEDIUM",
              "confidentialityImpact": "NONE",
              "integrityImpact": "NONE",
              "privilegesRequired": "LOW",
              "scope": "UNCHANGED",
              "userInteraction": "NONE",
              "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
              "version": "3.1"
            }
          },
          {
            "other": {
              "content": {
                "id": "CVE-2021-47406",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-05-29T18:09:07.067363Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "problemTypes": [
          {
            "descriptions": [
              {
                "description": "CWE-noinfo Not enough information",
                "lang": "en",
                "type": "CWE"
              }
            ]
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-11-01T19:15:09.194Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-04T05:39:59.310Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/a63474dbf692dd09b50fed592bc41f6de5f102fc"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/27e10c5d31ff1d222c7f797f1ee96d422859ba67"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/1fd95c05d8f742abfe906620780aee4dbe1a2db0"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ext4/extents.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "a63474dbf692",
              "status": "affected",
              "version": "8016e29f4362",
              "versionType": "git"
            },
            {
              "lessThan": "27e10c5d31ff",
              "status": "affected",
              "version": "8016e29f4362",
              "versionType": "git"
            },
            {
              "lessThan": "1fd95c05d8f7",
              "status": "affected",
              "version": "8016e29f4362",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ext4/extents.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.10"
            },
            {
              "lessThan": "5.10",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.10.*",
              "status": "unaffected",
              "version": "5.10.71",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.14.*",
              "status": "unaffected",
              "version": "5.14.10",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "5.15",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\next4: add error checking to ext4_ext_replay_set_iblocks()\n\nIf the call to ext4_map_blocks() fails due to an corrupted file\nsystem, ext4_ext_replay_set_iblocks() can get stuck in an infinite\nloop.  This could be reproduced by running generic/526 with a file\nsystem that has inline_data and fast_commit enabled.  The system will\nrepeatedly log to the console:\n\nEXT4-fs warning (device dm-3): ext4_block_to_path:105: block 1074800922 \u003e max in inode 131076\n\nand the stack that it gets stuck in is:\n\n   ext4_block_to_path+0xe3/0x130\n   ext4_ind_map_blocks+0x93/0x690\n   ext4_map_blocks+0x100/0x660\n   skip_hole+0x47/0x70\n   ext4_ext_replay_set_iblocks+0x223/0x440\n   ext4_fc_replay_inode+0x29e/0x3b0\n   ext4_fc_replay+0x278/0x550\n   do_one_pass+0x646/0xc10\n   jbd2_journal_recover+0x14a/0x270\n   jbd2_journal_load+0xc4/0x150\n   ext4_load_journal+0x1f3/0x490\n   ext4_fill_super+0x22d4/0x2c00\n\nWith this patch, generic/526 still fails, but system is no longer\nlocking up in a tight loop.  It\u0027s likely the root casue is that\nfast_commit replay is corrupting file systems with inline_data, and we\nprobably need to add better error handling in the fast commit replay\ncode path beyond what is done here, which essentially just breaks the\ninfinite loop without reporting the to the higher levels of the code."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-11-04T12:05:18.966Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/a63474dbf692dd09b50fed592bc41f6de5f102fc"
        },
        {
          "url": "https://git.kernel.org/stable/c/27e10c5d31ff1d222c7f797f1ee96d422859ba67"
        },
        {
          "url": "https://git.kernel.org/stable/c/1fd95c05d8f742abfe906620780aee4dbe1a2db0"
        }
      ],
      "title": "ext4: add error checking to ext4_ext_replay_set_iblocks()",
      "x_generator": {
        "engine": "bippy-9e1c9544281a"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2021-47406",
    "datePublished": "2024-05-21T15:03:59.334Z",
    "dateReserved": "2024-05-21T14:58:30.817Z",
    "dateUpdated": "2024-11-04T12:05:18.966Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2021-47406\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-05-21T15:15:26.170\",\"lastModified\":\"2024-11-01T20:35:00.870\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\next4: add error checking to ext4_ext_replay_set_iblocks()\\n\\nIf the call to ext4_map_blocks() fails due to an corrupted file\\nsystem, ext4_ext_replay_set_iblocks() can get stuck in an infinite\\nloop.  This could be reproduced by running generic/526 with a file\\nsystem that has inline_data and fast_commit enabled.  The system will\\nrepeatedly log to the console:\\n\\nEXT4-fs warning (device dm-3): ext4_block_to_path:105: block 1074800922 \u003e max in inode 131076\\n\\nand the stack that it gets stuck in is:\\n\\n   ext4_block_to_path+0xe3/0x130\\n   ext4_ind_map_blocks+0x93/0x690\\n   ext4_map_blocks+0x100/0x660\\n   skip_hole+0x47/0x70\\n   ext4_ext_replay_set_iblocks+0x223/0x440\\n   ext4_fc_replay_inode+0x29e/0x3b0\\n   ext4_fc_replay+0x278/0x550\\n   do_one_pass+0x646/0xc10\\n   jbd2_journal_recover+0x14a/0x270\\n   jbd2_journal_load+0xc4/0x150\\n   ext4_load_journal+0x1f3/0x490\\n   ext4_fill_super+0x22d4/0x2c00\\n\\nWith this patch, generic/526 still fails, but system is no longer\\nlocking up in a tight loop.  It\u0027s likely the root casue is that\\nfast_commit replay is corrupting file systems with inline_data, and we\\nprobably need to add better error handling in the fast commit replay\\ncode path beyond what is done here, which essentially just breaks the\\ninfinite loop without reporting the to the higher levels of the code.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ext4: agregue verificaci\u00f3n de errores a ext4_ext_replay_set_iblocks(). Si la llamada a ext4_map_blocks() falla debido a un sistema de archivos da\u00f1ado, ext4_ext_replay_set_iblocks() puede quedarse atascado en un bucle infinito. Esto podr\u00eda reproducirse ejecutando generic/526 con un sistema de archivos que tenga inline_data y fast_commit habilitados. El sistema iniciar\u00e1 sesi\u00f3n repetidamente en la consola: Advertencia EXT4-fs (dispositivo dm-3): ext4_block_to_path:105: bloque 1074800922 \u0026gt; max en el inodo 131076 y la pila en la que se atasca es: ext4_block_to_path+0xe3/0x130 ext4_ind_map_blocks+0x93/ 0x690 ext4_map_blocks+0x100/0x660 skip_hole+0x47/0x70 ext4_ext_replay_set_iblocks+0x223/0x440 ext4_fc_replay_inode+0x29e/0x3b0 ext4_fc_replay+0x278/0x550 do_one_pass+0x646/ 0xc10 jbd2_journal_recover+0x14a/0x270 jbd2_journal_load+0xc4/0x150 ext4_load_journal+0x1f3/0x490 ext4_fill_super+0x22d4/ 0x2c00 Con este parche, generic/526 todav\u00eda falla, pero el sistema ya no se bloquea en un bucle cerrado. Es probable que la causa ra\u00edz sea que la reproducci\u00f3n fast_commit est\u00e9 corrompiendo los sistemas de archivos con inline_data, y probablemente necesitemos agregar un mejor manejo de errores en la ruta del c\u00f3digo de reproducci\u00f3n de confirmaci\u00f3n r\u00e1pida m\u00e1s all\u00e1 de lo que se hace aqu\u00ed, lo que esencialmente simplemente rompe el bucle infinito sin informar al niveles superiores del c\u00f3digo.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"NONE\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"HIGH\",\"baseScore\":5.5,\"baseSeverity\":\"MEDIUM\"},\"exploitabilityScore\":1.8,\"impactScore\":3.6}]},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/1fd95c05d8f742abfe906620780aee4dbe1a2db0\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/27e10c5d31ff1d222c7f797f1ee96d422859ba67\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/a63474dbf692dd09b50fed592bc41f6de5f102fc\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.