CVE-2023-53481 json
ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed
published last yr. modified last mo. also EUVD-2025-32788
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 5%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed
Following process will trigger an infinite loop in ubi_wl_put_peb():
ubifs_bgt ubi_bgt ubifs_leb_unmap ubi_leb_unmap ubi_eba_unmap_leb ubi_wl_put_peb wear_leveling_worker e1 = rb_entry(rb_first(&ubi->used) e2 = get_peb_for_wl(ubi) ubi_io_read_vid_hdr // return err (flash fault) out_error: ubi->move_from = ubi->move_to = NULL wl_entry_destroy(ubi, e1) ubi->lookuptbl[e->pnum] = NULL retry: e = ubi->lookuptbl[pnum]; // return NULL if (e == ubi->move_from) { // NULL == NULL gets true goto retry; // infinite loop !!!
$ top PID USER PR NI VIRT RES SHR S %CPU %MEM COMMAND 7676 root 20 0 0 0 0 R 100.0 0.0 ubifs_bgt0_0
Fix it by: 1) Letting ubi_wl_put_peb() returns directly if wearl leveling entry has been removed from 'ubi->lookuptbl'. 2) Using 'ubi->wl_lock' protecting wl entry deletion to preventing an use-after-free problem for wl entry in ubi_wl_put_peb().
Fetch a reproducer in [Link].
Patch / fix
- Linux Linux 4.14.308, 4.19.276, 5.4.235, 5.10.173, 5.15.100, 6.1.18, 6.2.5, 6.3
- linux Debian 14, Debian 13, Debian 12 6.1.20-1
debian advisories DEBIAN-CVE-2023-53481
- linux Ubuntu 20.04 LTS 5.4.0-152.169
- linux Ubuntu 22.04 LTS 5.15.0-79.86
- linux-aws Ubuntu 20.04 LTS 5.4.0-1104.112
- linux-aws Ubuntu 22.04 LTS 5.15.0-1042.47
- linux-gcp Ubuntu 20.04 LTS 5.4.0-1107.116
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1039.47
- linux-gke Ubuntu 22.04 LTS 5.15.0-1039.44
- linux-ibm Ubuntu 20.04 LTS 5.4.0-1051.56
ubuntu advisories UBUNTU-CVE-2023-53481
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/b40d2fbf47af58377e898b5062077a47bb28a132 commit
- git.kernel.org/stable/c/f006f596fe851c3b6aae60b79f89f89f0e515d2f commit
- git.kernel.org/stable/c/b5be23f6ae610bdb262160a1f294afee6d0e6a69 commit
- git.kernel.org/stable/c/8a18856e074479bd050b01e688c58defadce7ab0 commit
- git.kernel.org/stable/c/3afaaf6f5867dc4ad383808d4053f428ec7b867d commit
- git.kernel.org/stable/c/cc4bc532acda66189bddc03b3fe1ad689d9a48a2 commit
- git.kernel.org/stable/c/5af1c643184a5d09ff5b3f334077a4d0a163c677 commit
- git.kernel.org/stable/c/4d57a7333e26040f2b583983e1970d9d460e56b0 commit
Is CVE-2023-53481 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2023-53481 updated cvss 5.5
kernel: ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 moreaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 10 kernelnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- last mo.
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-16).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-835 Loop with Unreachable Exit Condition
- Technology feeds
References
-
git.kernel.org
/stable/c/b40d2fbf47af58377e898b5062077a47bb28a132
patch
-
git.kernel.org
/stable/c/f006f596fe851c3b6aae60b79f89f89f0e515d2f
patch
-
git.kernel.org
/stable/c/b5be23f6ae610bdb262160a1f294afee6d0e6a69
patch
-
git.kernel.org
/stable/c/8a18856e074479bd050b01e688c58defadce7ab0
patch
-
git.kernel.org
/stable/c/3afaaf6f5867dc4ad383808d4053f428ec7b867d
patch
-
git.kernel.org
/stable/c/cc4bc532acda66189bddc03b3fe1ad689d9a48a2
patch
-
git.kernel.org
/stable/c/5af1c643184a5d09ff5b3f334077a4d0a163c677
patch
-
git.kernel.org
/stable/c/4d57a7333e26040f2b583983e1970d9d460e56b0
patch
Sources
- CVE List CVE-2023-53481
- NVD CVE-2023-53481
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.