cve-2024-26972
Vulnerability from cvelistv5
Published
2024-05-01 05:20
Modified
2024-08-02 00:21
Severity
Summary
ubifs: ubifs_symlink: Fix memleak of inode->i_link in error path
References
SourceURLTags
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/62b5ae00c2b835639002ce898ccb5d82c51073ae
416baaa9-dc9f-4396-8d5f-8c081fb06d67https://git.kernel.org/stable/c/6379b44cdcd67f5f5d986b73953e99700591edfa
Impacted products
VendorProduct
LinuxLinux
LinuxLinux
Show details on NVD website

To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-26972",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-06-14T20:05:43.085010Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-06-14T20:05:50.540Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      },
      {
        "providerMetadata": {
          "dateUpdated": "2024-08-02T00:21:05.922Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/62b5ae00c2b835639002ce898ccb5d82c51073ae"
          },
          {
            "tags": [
              "x_transferred"
            ],
            "url": "https://git.kernel.org/stable/c/6379b44cdcd67f5f5d986b73953e99700591edfa"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ubifs/dir.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "62b5ae00c2b8",
              "status": "affected",
              "version": "2c58d548f570",
              "versionType": "git"
            },
            {
              "lessThan": "6379b44cdcd6",
              "status": "affected",
              "version": "2c58d548f570",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ubifs/dir.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.2"
            },
            {
              "lessThan": "5.2",
              "status": "unaffected",
              "version": "0",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "6.8.*",
              "status": "unaffected",
              "version": "6.8.3",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.9",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nubifs: ubifs_symlink: Fix memleak of inode-\u003ei_link in error path\n\nFor error handling path in ubifs_symlink(), inode will be marked as\nbad first, then iput() is invoked. If inode-\u003ei_link is initialized by\nfscrypt_encrypt_symlink() in encryption scenario, inode-\u003ei_link won\u0027t\nbe freed by callchain ubifs_free_inode -\u003e fscrypt_free_inode in error\nhandling path, because make_bad_inode() has changed \u0027inode-\u003ei_mode\u0027 as\n\u0027S_IFREG\u0027.\nFollowing kmemleak is easy to be reproduced by injecting error in\nubifs_jnl_update() when doing symlink in encryption scenario:\n unreferenced object 0xffff888103da3d98 (size 8):\n  comm \"ln\", pid 1692, jiffies 4294914701 (age 12.045s)\n  backtrace:\n   kmemdup+0x32/0x70\n   __fscrypt_encrypt_symlink+0xed/0x1c0\n   ubifs_symlink+0x210/0x300 [ubifs]\n   vfs_symlink+0x216/0x360\n   do_symlinkat+0x11a/0x190\n   do_syscall_64+0x3b/0xe0\nThere are two ways fixing it:\n 1. Remove make_bad_inode() in error handling path. We can do that\n    because ubifs_evict_inode() will do same processes for good\n    symlink inode and bad symlink inode, for inode-\u003ei_nlink checking\n    is before is_bad_inode().\n 2. Free inode-\u003ei_link before marking inode bad.\nMethod 2 is picked, it has less influence, personally, I think."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-05-29T05:26:10.481Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/62b5ae00c2b835639002ce898ccb5d82c51073ae"
        },
        {
          "url": "https://git.kernel.org/stable/c/6379b44cdcd67f5f5d986b73953e99700591edfa"
        }
      ],
      "title": "ubifs: ubifs_symlink: Fix memleak of inode-\u003ei_link in error path",
      "x_generator": {
        "engine": "bippy-a5840b7849dd"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-26972",
    "datePublished": "2024-05-01T05:20:04.669Z",
    "dateReserved": "2024-02-19T14:20:24.202Z",
    "dateUpdated": "2024-08-02T00:21:05.922Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-26972\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-05-01T06:15:13.597\",\"lastModified\":\"2024-05-01T13:02:20.750\",\"vulnStatus\":\"Awaiting Analysis\",\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nubifs: ubifs_symlink: Fix memleak of inode-\u003ei_link in error path\\n\\nFor error handling path in ubifs_symlink(), inode will be marked as\\nbad first, then iput() is invoked. If inode-\u003ei_link is initialized by\\nfscrypt_encrypt_symlink() in encryption scenario, inode-\u003ei_link won\u0027t\\nbe freed by callchain ubifs_free_inode -\u003e fscrypt_free_inode in error\\nhandling path, because make_bad_inode() has changed \u0027inode-\u003ei_mode\u0027 as\\n\u0027S_IFREG\u0027.\\nFollowing kmemleak is easy to be reproduced by injecting error in\\nubifs_jnl_update() when doing symlink in encryption scenario:\\n unreferenced object 0xffff888103da3d98 (size 8):\\n  comm \\\"ln\\\", pid 1692, jiffies 4294914701 (age 12.045s)\\n  backtrace:\\n   kmemdup+0x32/0x70\\n   __fscrypt_encrypt_symlink+0xed/0x1c0\\n   ubifs_symlink+0x210/0x300 [ubifs]\\n   vfs_symlink+0x216/0x360\\n   do_symlinkat+0x11a/0x190\\n   do_syscall_64+0x3b/0xe0\\nThere are two ways fixing it:\\n 1. Remove make_bad_inode() in error handling path. We can do that\\n    because ubifs_evict_inode() will do same processes for good\\n    symlink inode and bad symlink inode, for inode-\u003ei_nlink checking\\n    is before is_bad_inode().\\n 2. Free inode-\u003ei_link before marking inode bad.\\nMethod 2 is picked, it has less influence, personally, I think.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ubifs: ubifs_symlink: corrige la fuga de memleak de inodo-\u0026gt;i_link en la ruta de error Para el manejo de errores en la ruta en ubifs_symlink(), el inodo se marcar\u00e1 como incorrecto primero y luego se invocar\u00e1 iput(). Si inode-\u0026gt;i_link se inicializa mediante fscrypt_encrypt_symlink() en el escenario de cifrado, inode-\u0026gt;i_link no ser\u00e1 liberado por la cadena de llamadas ubifs_free_inode -\u0026gt; fscrypt_free_inode en la ruta de manejo de errores, porque make_bad_inode() ha cambiado \u0027inode-\u0026gt;i_mode\u0027 como \u0027S_IFREG \u0027. El siguiente kmemleak es f\u00e1cil de reproducir inyectando un error en ubifs_jnl_update() al realizar un enlace simb\u00f3lico en un escenario de cifrado: objeto sin referencia 0xffff888103da3d98 (tama\u00f1o 8): comm \\\"ln\\\", pid 1692, jiffies 4294914701 (edad 12.045 s) backtrace: kmemdup+0x32/ 0x70 __fscrypt_encrypt_symlink+0xed/0x1c0 ubifs_symlink+0x210/0x300 [ubifs] vfs_symlink+0x216/0x360 do_symlinkat+0x11a/0x190 do_syscall_64+0x3b/0xe0 Hay dos formas de solucionarlo: 1. Eliminar make_bad _inode() en la ruta de manejo de errores. Podemos hacer eso porque ubifs_evict_inode() realizar\u00e1 los mismos procesos para el inodo de enlace simb\u00f3lico bueno y el inodo de enlace simb\u00f3lico incorrecto, para inodo-\u0026gt;i_nlink la verificaci\u00f3n es antes de is_bad_inode(). 2. Libere inodo-\u0026gt;i_link antes de marcar el inodo como incorrecto. Se elige el m\u00e9todo 2, creo que tiene menos influencia, personalmente.\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/62b5ae00c2b835639002ce898ccb5d82c51073ae\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/6379b44cdcd67f5f5d986b73953e99700591edfa\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.