Service interruption via CLCD node refcount leak
Published Feb 26, 2025 · Updated May 11, 2026
Reference-count leak in the Linux CLCD framebuffer driver allows local users to exhaust resources and interrupt service. In clcdfb_of_vram_setup(), successful device-tree VRAM setup and the mapping-failure path retain the node reference returned by of_parse_phandle() instead of releasing it with of_node_put(). The public record does not identify how a low-privileged local user can repeatedly reach the setup path; the assessed impact is availability only.
Summary
What happened
Reference-count leak in the Linux CLCD framebuffer driver allows local users to exhaust resources and interrupt service. In clcdfb_of_vram_setup(), successful device-tree VRAM setup and the mapping-failure path retain the node reference returned by of_parse_phandle() instead of releasing it with of_node_put(). The public record does not identify how a low-privileged local user can repeatedly reach the setup path; the assessed impact is availability only.
The record
- CVE
- CVE-2022-49421
- Published
- Feb 26, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2025CVE publishedPublication date reported by the CVE source.
- May 11, 2026Record 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=3.17
- Affected versionversion=d10715be03bd8bad59ddc50236cb140c3bd73c7b <2e2e2c71b2642289438392edbf5d08cdbc0b138b
- Affected versionversion=d10715be03bd8bad59ddc50236cb140c3bd73c7b <38d245cebf545338a6bc1c7762023de3fbecd7b7
- Affected versionversion=d10715be03bd8bad59ddc50236cb140c3bd73c7b <51eb1bb6baeb478538dd4ec6459fd68c44a855b1
- Affected versionversion=d10715be03bd8bad59ddc50236cb140c3bd73c7b <6c92711db7c90f78e0b67ac2a8944d0fe7e12d83
- Affected versionversion=d10715be03bd8bad59ddc50236cb140c3bd73c7b <8db59df7f5826e104db82cfddbf22a33a151193e
- Affected versionversion=d10715be03bd8bad59ddc50236cb140c3bd73c7b <b23789a59fa6f00e98a319291819f91fbba0deb8
- Affected versionversion=d10715be03bd8bad59ddc50236cb140c3bd73c7b <bbb2a24e863b6a10129546a0a4ceea2f07deec39
- Affected versionversion=d10715be03bd8bad59ddc50236cb140c3bd73c7b <c1c4405222b6fc98c16e8c2aa679c14e41d81465
- Affected versionversion=d10715be03bd8bad59ddc50236cb140c3bd73c7b <f2dfb4ab887d67be7d0892ba041d3c8d738d3356
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
No public exploit references are available in this record.
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