Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2023-53800ubi: Fix use-after-free when volume resizing failed

Description

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: <TASK> 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 </TASK> 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.

Timeline

  1. ID reserved

    By Linux

  2. · 1 day later

    Published

  3. · 10 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2023-53800, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (16 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < bf9875aa7f7d624a8c084425b14bf7e5907ebc30
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < bf795ebbb9995e2fe7945de71177f01c2f1215dc
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < 9c8be1f165baee53b5a36ea0b3c9281d403a1d0b
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < 35f8d4064e54c18424db2997059d4c0b1d13d093
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < 53818746e549e61841428892a8d94344494be797
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < b0c951742348d216f094d16ed4f70ae73db881c0
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < 3d6378f7056ac7350338f941001162a8f660853c
    • affected 801c135ce73d5df1caf3eca35b66a10824ae0707 – < 9af31d6ec1a4be4caab2550096c6bd2ba8fba472
  • Linux · Linux

    • affected 2.6.22
    • unaffected < 2.6.22
    • unaffected 4.14.308 – ≤ 4.14.*
    • unaffected 4.19.276 – ≤ 4.19.*
    • unaffected 5.4.235 – ≤ 5.4.*
    • unaffected 5.10.173 – ≤ 5.10.*
    • unaffected 5.15.100 – ≤ 5.15.*
    • unaffected 6.1.18 – ≤ 6.1.*
    • unaffected 6.2.5 – ≤ 6.2.*
    • unaffected 6.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53800 badge
[![CVE-2023-53800](https://cveledger.app/badge/CVE-2023-53800.svg)](https://cveledger.app/cve/CVE-2023-53800)

Record last updated .