Kernel memory exhaustion via unreleased firmware
Published Dec 9, 2025 · Updated May 11, 2026
Memory leak in the Linux kernel bcm3510 DVB frontend allows local users to exhaust kernel memory through repeated failed firmware writes. bcm3510_download_firmware() returns after bcm3510_write_ram() fails without releasing the firmware object allocated by request_firmware(). Reachability requires administrative access, a configured BCM3510 tuner, and repeated firmware-load failures; the bounded consequence is service interruption from memory exhaustion.
Summary
What happened
Memory leak in the Linux kernel bcm3510 DVB frontend allows local users to exhaust kernel memory through repeated failed firmware writes. bcm3510_download_firmware() returns after bcm3510_write_ram() fails without releasing the firmware object allocated by request_firmware(). Reachability requires administrative access, a configured BCM3510 tuner, and repeated firmware-load failures; the bounded consequence is service interruption from memory exhaustion.
The record
- CVE
- CVE-2022-50664
- Published
- Dec 9, 2025
- Updated
- May 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Dec 9, 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=2.6.13
- Affected versionversion=55f51efdb696ff6e9d2056377d05268a97f3d4e4 <25cab05aa2df904ee1fea37d8dfa0d92c951bb4e
- Affected versionversion=55f51efdb696ff6e9d2056377d05268a97f3d4e4 <438a4a8dece2abac099777a00db91784c0996cdc
- Affected versionversion=55f51efdb696ff6e9d2056377d05268a97f3d4e4 <438cd29fec3ea09769639f6032687e0c1434dbe0
- Affected versionversion=55f51efdb696ff6e9d2056377d05268a97f3d4e4 <669fb90507dbaf419aa3871bf73160e93d50487f
- Affected versionversion=55f51efdb696ff6e9d2056377d05268a97f3d4e4 <a15fe8d9f1bf460a804bcf18a890bfd2cf0d5caa
- Affected versionversion=55f51efdb696ff6e9d2056377d05268a97f3d4e4 <a44828482bd5b11d728d7dac09b0d723aab9ff7b
- Affected versionversion=55f51efdb696ff6e9d2056377d05268a97f3d4e4 <afccb6ac63fc4328bc61ba086a3cad30054d87c1
- Affected versionversion=55f51efdb696ff6e9d2056377d05268a97f3d4e4 <b42580c8d8aac11a66046897979cc13cfd04c541
- Affected versionversion=55f51efdb696ff6e9d2056377d05268a97f3d4e4 <b4d8fd008de1774d99a5b50acc03d92a1919c3a7
What conditions does exploitation require?
What is affected?
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