GHSA-7JJF-HG6R-X4HG

Vulnerability from github – Published: 2025-12-09 03:31 – Updated: 2025-12-09 03:31
VLAI?
Details

In the Linux kernel, the following vulnerability has been resolved:

ubi: Fix use-after-free when volume resizing failed

There is an use-after-free problem reported by KASAN: ================================================================== BUG: KASAN: use-after-free in ubi_eba_copy_table+0x11f/0x1c0 [ubi] Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735

CPU: 2 PID: 4735 Comm: ubirsvol Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty #14 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: dump_stack_lvl+0x34/0x44 print_report+0x171/0x472 kasan_report+0xad/0x130 ubi_eba_copy_table+0x11f/0x1c0 [ubi] ubi_resize_volume+0x4f9/0xbc0 [ubi] ubi_cdev_ioctl+0x701/0x1850 [ubi] __x64_sys_ioctl+0x11d/0x170 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0

When ubi_change_vtbl_record() returns an error in ubi_resize_volume(), "new_eba_tbl" will be freed on error handing path, but it is holded by "vol->eba_tbl" in ubi_eba_replace_table(). It means that the liftcycle of "vol->eba_tbl" and "vol" are different, so when resizing volume in next time, it causing an use-after-free fault.

Fix it by not freeing "new_eba_tbl" after it replaced in ubi_eba_replace_table(), while will be freed in next volume resizing.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2023-53800"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-09T01:16:51Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nubi: Fix use-after-free when volume resizing failed\n\nThere is an use-after-free problem reported by KASAN:\n  ==================================================================\n  BUG: KASAN: use-after-free in ubi_eba_copy_table+0x11f/0x1c0 [ubi]\n  Read of size 8 at addr ffff888101eec008 by task ubirsvol/4735\n\n  CPU: 2 PID: 4735 Comm: ubirsvol\n  Not tainted 6.1.0-rc1-00003-g84fa3304a7fc-dirty #14\n  Hardware name: QEMU Standard PC (i440FX + PIIX, 1996),\n  BIOS 1.14.0-1.fc33 04/01/2014\n  Call Trace:\n   \u003cTASK\u003e\n   dump_stack_lvl+0x34/0x44\n   print_report+0x171/0x472\n   kasan_report+0xad/0x130\n   ubi_eba_copy_table+0x11f/0x1c0 [ubi]\n   ubi_resize_volume+0x4f9/0xbc0 [ubi]\n   ubi_cdev_ioctl+0x701/0x1850 [ubi]\n   __x64_sys_ioctl+0x11d/0x170\n   do_syscall_64+0x35/0x80\n   entry_SYSCALL_64_after_hwframe+0x46/0xb0\n   \u003c/TASK\u003e\n\nWhen ubi_change_vtbl_record() returns an error in ubi_resize_volume(),\n\"new_eba_tbl\" will be freed on error handing path, but it is holded\nby \"vol-\u003eeba_tbl\" in ubi_eba_replace_table(). It means that the liftcycle\nof \"vol-\u003eeba_tbl\" and \"vol\" are different, so when resizing volume in\nnext time, it causing an use-after-free fault.\n\nFix it by not freeing \"new_eba_tbl\" after it replaced in\nubi_eba_replace_table(), while will be freed in next volume resizing.",
  "id": "GHSA-7jjf-hg6r-x4hg",
  "modified": "2025-12-09T03:31:11Z",
  "published": "2025-12-09T03:31:11Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-53800"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/35f8d4064e54c18424db2997059d4c0b1d13d093"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/3d6378f7056ac7350338f941001162a8f660853c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/53818746e549e61841428892a8d94344494be797"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9af31d6ec1a4be4caab2550096c6bd2ba8fba472"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9c8be1f165baee53b5a36ea0b3c9281d403a1d0b"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b0c951742348d216f094d16ed4f70ae73db881c0"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/bf795ebbb9995e2fe7945de71177f01c2f1215dc"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/bf9875aa7f7d624a8c084425b14bf7e5907ebc30"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


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 observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.