Local service interruption via UBI retry loop
Published Oct 1, 2025 · Updated Oct 1, 2025
An infinite loop in the Linux UBI wear-leveling path allows local users to hang a UBIFS background thread after a flash read fault. During concurrent unmapping, wear_leveling_worker deletes a lookup entry and clears move pointers; ubi_wl_put_peb() then treats two NULL pointers as equal and retries forever. Reachability requires a UBI-backed UBIFS volume and a wear-leveling read failure, while the observed consequence is one background thread consuming 100% CPU.
Summary
What happened
An infinite loop in the Linux UBI wear-leveling path allows local users to hang a UBIFS background thread after a flash read fault. During concurrent unmapping, wear_leveling_worker deletes a lookup entry and clears move pointers; ubi_wl_put_peb() then treats two NULL pointers as equal and retries forever. Reachability requires a UBI-backed UBIFS volume and a wear-leveling read failure, while the observed consequence is one background thread consuming 100% CPU.
The record
- CVE
- CVE-2023-53481
- Published
- Oct 1, 2025
- Updated
- Oct 1, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-835, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 1, 2025CVE publishedPublication date reported by the CVE source.
- Oct 1, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.25
- Affected versionversion=43f9b25a9cdd7b177f77f026b1461abd1abbd174 <3afaaf6f5867dc4ad383808d4053f428ec7b867d
- Affected versionversion=43f9b25a9cdd7b177f77f026b1461abd1abbd174 <4d57a7333e26040f2b583983e1970d9d460e56b0
- Affected versionversion=43f9b25a9cdd7b177f77f026b1461abd1abbd174 <5af1c643184a5d09ff5b3f334077a4d0a163c677
- Affected versionversion=43f9b25a9cdd7b177f77f026b1461abd1abbd174 <8a18856e074479bd050b01e688c58defadce7ab0
- Affected versionversion=43f9b25a9cdd7b177f77f026b1461abd1abbd174 <b40d2fbf47af58377e898b5062077a47bb28a132
- Affected versionversion=43f9b25a9cdd7b177f77f026b1461abd1abbd174 <b5be23f6ae610bdb262160a1f294afee6d0e6a69
- Affected versionversion=43f9b25a9cdd7b177f77f026b1461abd1abbd174 <cc4bc532acda66189bddc03b3fe1ad689d9a48a2
- Affected versionversion=43f9b25a9cdd7b177f77f026b1461abd1abbd174 <f006f596fe851c3b6aae60b79f89f89f0e515d2f
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Kernel Bugzilla 216111 reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo