CVE-2023-53584 (GCVE-0-2023-53584)
Vulnerability from cvelistv5
Published
2025-10-04 15:43
Modified
2025-10-04 15:43
Severity ?
Summary
In the Linux kernel, the following vulnerability has been resolved: ubifs: ubifs_releasepage: Remove ubifs_assert(0) to valid this process There are two states for ubifs writing pages: 1. Dirty, Private 2. Not Dirty, Not Private The normal process cannot go to ubifs_releasepage() which means there exists pages being private but not dirty. Reproducer[1] shows that it could occur (which maybe related to [2]) with following process: PA PB PC lock(page)[PA] ubifs_write_end attach_page_private // set Private __set_page_dirty_nobuffers // set Dirty unlock(page) write_cache_pages[PA] lock(page) clear_page_dirty_for_io(page) // clear Dirty ubifs_writepage do_truncation[PB] truncate_setsize i_size_write(inode, newsize) // newsize = 0 i_size = i_size_read(inode) // i_size = 0 end_index = i_size >> PAGE_SHIFT if (page->index > end_index) goto out // jump out: unlock(page) // Private, Not Dirty generic_fadvise[PC] lock(page) invalidate_inode_page try_to_release_page ubifs_releasepage ubifs_assert(c, 0) // bad assertion! unlock(page) truncate_pagecache[PB] Then we may get following assertion failed: UBIFS error (ubi0:0 pid 1683): ubifs_assert_failed [ubifs]: UBIFS assert failed: 0, in fs/ubifs/file.c:1513 UBIFS warning (ubi0:0 pid 1683): ubifs_ro_mode [ubifs]: switched to read-only mode, error -22 CPU: 2 PID: 1683 Comm: aa Not tainted 5.16.0-rc5-00184-g0bca5994cacc-dirty #308 Call Trace: dump_stack+0x13/0x1b ubifs_ro_mode+0x54/0x60 [ubifs] ubifs_assert_failed+0x4b/0x80 [ubifs] ubifs_releasepage+0x67/0x1d0 [ubifs] try_to_release_page+0x57/0xe0 invalidate_inode_page+0xfb/0x130 __invalidate_mapping_pages+0xb9/0x280 invalidate_mapping_pagevec+0x12/0x20 generic_fadvise+0x303/0x3c0 ksys_fadvise64_64+0x4c/0xb0 [1] https://bugzilla.kernel.org/show_bug.cgi?id=215373 [2] https://linux-mtd.infradead.narkive.com/NQoBeT1u/patch-rfc-ubifs-fix-assert-failed-in-ubifs-set-page-dirty
References
Impacted products
Vendor Product Version
Linux Linux Version: 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d
Version: 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d
Version: 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d
 Create a notification for this product.
Show details on NVD website

To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "fs/ubifs/file.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "7750be5d3e18500b454714677463b500a0b8b0d8",
              "status": "affected",
              "version": "1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d",
              "versionType": "git"
            },
            {
              "lessThan": "bd188ff1c8a1935c93a1e3cacf3be62667fdf762",
              "status": "affected",
              "version": "1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d",
              "versionType": "git"
            },
            {
              "lessThan": "66f4742e93523ab2f062d9d9828b3e590bc61536",
              "status": "affected",
              "version": "1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "fs/ubifs/file.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "2.6.27"
            },
            {
              "lessThan": "2.6.27",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.18",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.2.*",
              "status": "unaffected",
              "version": "6.2.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.3",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.18",
                  "versionStartIncluding": "2.6.27",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.2.5",
                  "versionStartIncluding": "2.6.27",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.3",
                  "versionStartIncluding": "2.6.27",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nubifs: ubifs_releasepage: Remove ubifs_assert(0) to valid this process\n\nThere are two states for ubifs writing pages:\n1. Dirty, Private\n2. Not Dirty, Not Private\n\nThe normal process cannot go to ubifs_releasepage() which means there\nexists pages being private but not dirty. Reproducer[1] shows that it\ncould occur (which maybe related to [2]) with following process:\n\n     PA                     PB                    PC\nlock(page)[PA]\nubifs_write_end\n  attach_page_private         // set Private\n  __set_page_dirty_nobuffers  // set Dirty\nunlock(page)\n\nwrite_cache_pages[PA]\n  lock(page)\n  clear_page_dirty_for_io(page)\t// clear Dirty\n  ubifs_writepage\n\n                        do_truncation[PB]\n\t\t\t  truncate_setsize\n\t\t\t    i_size_write(inode, newsize) // newsize = 0\n\n    i_size = i_size_read(inode)\t// i_size = 0\n    end_index = i_size \u003e\u003e PAGE_SHIFT\n    if (page-\u003eindex \u003e end_index)\n      goto out // jump\nout:\nunlock(page)   // Private, Not Dirty\n\n\t\t\t\t\t\tgeneric_fadvise[PC]\n\t\t\t\t\t\t  lock(page)\n\t\t\t\t\t\t  invalidate_inode_page\n\t\t\t\t\t\t    try_to_release_page\n\t\t\t\t\t\t      ubifs_releasepage\n\t\t\t\t\t\t        ubifs_assert(c, 0)\n\t\t                                        // bad assertion!\n\t\t\t\t\t\t  unlock(page)\n\t\t\t  truncate_pagecache[PB]\n\nThen we may get following assertion failed:\n  UBIFS error (ubi0:0 pid 1683): ubifs_assert_failed [ubifs]:\n  UBIFS assert failed: 0, in fs/ubifs/file.c:1513\n  UBIFS warning (ubi0:0 pid 1683): ubifs_ro_mode [ubifs]:\n  switched to read-only mode, error -22\n  CPU: 2 PID: 1683 Comm: aa Not tainted 5.16.0-rc5-00184-g0bca5994cacc-dirty #308\n  Call Trace:\n    dump_stack+0x13/0x1b\n    ubifs_ro_mode+0x54/0x60 [ubifs]\n    ubifs_assert_failed+0x4b/0x80 [ubifs]\n    ubifs_releasepage+0x67/0x1d0 [ubifs]\n    try_to_release_page+0x57/0xe0\n    invalidate_inode_page+0xfb/0x130\n    __invalidate_mapping_pages+0xb9/0x280\n    invalidate_mapping_pagevec+0x12/0x20\n    generic_fadvise+0x303/0x3c0\n    ksys_fadvise64_64+0x4c/0xb0\n\n[1] https://bugzilla.kernel.org/show_bug.cgi?id=215373\n[2] https://linux-mtd.infradead.narkive.com/NQoBeT1u/patch-rfc-ubifs-fix-assert-failed-in-ubifs-set-page-dirty"
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2025-10-04T15:43:59.835Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/7750be5d3e18500b454714677463b500a0b8b0d8"
        },
        {
          "url": "https://git.kernel.org/stable/c/bd188ff1c8a1935c93a1e3cacf3be62667fdf762"
        },
        {
          "url": "https://git.kernel.org/stable/c/66f4742e93523ab2f062d9d9828b3e590bc61536"
        }
      ],
      "title": "ubifs: ubifs_releasepage: Remove ubifs_assert(0) to valid this process",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2023-53584",
    "datePublished": "2025-10-04T15:43:59.835Z",
    "dateReserved": "2025-10-04T15:40:38.477Z",
    "dateUpdated": "2025-10-04T15:43:59.835Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "nvd": "{\"cve\":{\"id\":\"CVE-2023-53584\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2025-10-04T16:15:54.217\",\"lastModified\":\"2025-10-06T14:56:21.733\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\nubifs: ubifs_releasepage: Remove ubifs_assert(0) to valid this process\\n\\nThere are two states for ubifs writing pages:\\n1. Dirty, Private\\n2. Not Dirty, Not Private\\n\\nThe normal process cannot go to ubifs_releasepage() which means there\\nexists pages being private but not dirty. Reproducer[1] shows that it\\ncould occur (which maybe related to [2]) with following process:\\n\\n     PA                     PB                    PC\\nlock(page)[PA]\\nubifs_write_end\\n  attach_page_private         // set Private\\n  __set_page_dirty_nobuffers  // set Dirty\\nunlock(page)\\n\\nwrite_cache_pages[PA]\\n  lock(page)\\n  clear_page_dirty_for_io(page)\\t// clear Dirty\\n  ubifs_writepage\\n\\n                        do_truncation[PB]\\n\\t\\t\\t  truncate_setsize\\n\\t\\t\\t    i_size_write(inode, newsize) // newsize = 0\\n\\n    i_size = i_size_read(inode)\\t// i_size = 0\\n    end_index = i_size \u003e\u003e PAGE_SHIFT\\n    if (page-\u003eindex \u003e end_index)\\n      goto out // jump\\nout:\\nunlock(page)   // Private, Not Dirty\\n\\n\\t\\t\\t\\t\\t\\tgeneric_fadvise[PC]\\n\\t\\t\\t\\t\\t\\t  lock(page)\\n\\t\\t\\t\\t\\t\\t  invalidate_inode_page\\n\\t\\t\\t\\t\\t\\t    try_to_release_page\\n\\t\\t\\t\\t\\t\\t      ubifs_releasepage\\n\\t\\t\\t\\t\\t\\t        ubifs_assert(c, 0)\\n\\t\\t                                        // bad assertion!\\n\\t\\t\\t\\t\\t\\t  unlock(page)\\n\\t\\t\\t  truncate_pagecache[PB]\\n\\nThen we may get following assertion failed:\\n  UBIFS error (ubi0:0 pid 1683): ubifs_assert_failed [ubifs]:\\n  UBIFS assert failed: 0, in fs/ubifs/file.c:1513\\n  UBIFS warning (ubi0:0 pid 1683): ubifs_ro_mode [ubifs]:\\n  switched to read-only mode, error -22\\n  CPU: 2 PID: 1683 Comm: aa Not tainted 5.16.0-rc5-00184-g0bca5994cacc-dirty #308\\n  Call Trace:\\n    dump_stack+0x13/0x1b\\n    ubifs_ro_mode+0x54/0x60 [ubifs]\\n    ubifs_assert_failed+0x4b/0x80 [ubifs]\\n    ubifs_releasepage+0x67/0x1d0 [ubifs]\\n    try_to_release_page+0x57/0xe0\\n    invalidate_inode_page+0xfb/0x130\\n    __invalidate_mapping_pages+0xb9/0x280\\n    invalidate_mapping_pagevec+0x12/0x20\\n    generic_fadvise+0x303/0x3c0\\n    ksys_fadvise64_64+0x4c/0xb0\\n\\n[1] https://bugzilla.kernel.org/show_bug.cgi?id=215373\\n[2] https://linux-mtd.infradead.narkive.com/NQoBeT1u/patch-rfc-ubifs-fix-assert-failed-in-ubifs-set-page-dirty\"}],\"metrics\":{},\"references\":[{\"url\":\"https://git.kernel.org/stable/c/66f4742e93523ab2f062d9d9828b3e590bc61536\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/7750be5d3e18500b454714677463b500a0b8b0d8\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"},{\"url\":\"https://git.kernel.org/stable/c/bd188ff1c8a1935c93a1e3cacf3be62667fdf762\",\"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.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • 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.