Service interruption via probe error-path memory leak
Published Oct 7, 2025 · Updated Oct 7, 2025
Memory leak in Linux's Raspberry Pi firmware driver allows local users to interrupt service through kernel-memory exhaustion. rpi_firmware_probe() allocates fw, but its mbox_request_channel() error path returns without calling rpi_firmware_delete() or kfree(), leaving the allocation unreleased. Reachability requires the Raspberry Pi firmware driver and a mailbox-channel request failure; the published impact is limited to availability, with no reported data exposure or modification.
Summary
What happened
Memory leak in Linux's Raspberry Pi firmware driver allows local users to interrupt service through kernel-memory exhaustion. rpi_firmware_probe() allocates fw, but its mbox_request_channel() error path returns without calling rpi_firmware_delete() or kfree(), leaving the allocation unreleased. Reachability requires the Raspberry Pi firmware driver and a mailbox-channel request failure; the published impact is limited to availability, with no reported data exposure or modification.
The record
- CVE
- CVE-2022-50537
- Published
- Oct 7, 2025
- Updated
- Oct 7, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-401, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 7, 2025CVE publishedPublication date reported by the CVE source.
- Oct 7, 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=1e7c57355a3bc617fc220234889e49fe722a6305 <6757dd2193fe18c5c5fe3050e7f2ff9dcbd1ff34
- Affected versionversion=1e7c57355a3bc617fc220234889e49fe722a6305 <71d2abab374f707ab8ac8dcef191fd2b3b67b8bd
- Affected versionversion=1e7c57355a3bc617fc220234889e49fe722a6305 <7b51161696e803fd5f9ad55b20a64c2df313f95c
- Affected versionversion=1e7c57355a3bc617fc220234889e49fe722a6305 <b308fdedef095aac14569f810d46edf773ea7d1e
- Affected versionversion=5.13
- Affected versionversion=60831f5ae6c713afceb6d29f40899ed112f36059 <d34742245e4366579f9a80f8cfe4a63248e838e0
- Affected versionversion=d537afa08e156a0a72562e625506825c2776fcfa <62ac943eb2a9d655e431b9bc98ff6d7bd51a0e49
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