Kernel crash via unchecked CODA IRAM allocation
Published Oct 4, 2025 · Updated Oct 4, 2025
NULL pointer dereference in the CODA media driver in Linux allows local users to crash the kernel through video decoding activity. The coda_setup_iram routine continues IRAM buffer setup without immediately rejecting a zero return from coda_iram_alloc. Exploitation requires low-privileged local access, a reachable CODA device path, and an allocation failure; the documented consequence is availability loss only.
Summary
What happened
NULL pointer dereference in the CODA media driver in Linux allows local users to crash the kernel through video decoding activity. The coda_setup_iram routine continues IRAM buffer setup without immediately rejecting a zero return from coda_iram_alloc. Exploitation requires low-privileged local access, a reachable CODA device path, and an allocation failure; the documented consequence is availability loss only.
The record
- CVE
- CVE-2022-50501
- Published
- Oct 4, 2025
- Updated
- Oct 4, 2025
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- CWE-476, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 4, 2025CVE publishedPublication date reported by the CVE source.
- Oct 4, 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=3.17
- Affected versionversion=b313bcc9a46795c0233a765411cef9a15caaa7fb <05f165ded4a7baec31b65aba88e2cd1fb9b91db2
- Affected versionversion=b313bcc9a46795c0233a765411cef9a15caaa7fb <2b436f1410245412ea5e4c356a175a928d73eed3
- Affected versionversion=b313bcc9a46795c0233a765411cef9a15caaa7fb <2c6887d5a29024bada6928d1d0959c9990401384
- Affected versionversion=b313bcc9a46795c0233a765411cef9a15caaa7fb <35ddd00b36589cf948875b825eedaab1aefd5ad5
- Affected versionversion=b313bcc9a46795c0233a765411cef9a15caaa7fb <45f57abaee136a1e39d2b04443a1bd5311ba7d94
- Affected versionversion=b313bcc9a46795c0233a765411cef9a15caaa7fb <532417dc98cb9c1185ada4ea4e7ccf965c06bcb5
- Affected versionversion=b313bcc9a46795c0233a765411cef9a15caaa7fb <5688d33aa293dfa122d66bef9c0258ddf7ef11e7
- Affected versionversion=b313bcc9a46795c0233a765411cef9a15caaa7fb <6b8082238fb8bb20f67e46388123e67a5bbc558d
- Affected versionversion=b313bcc9a46795c0233a765411cef9a15caaa7fb <b99872178e7473f21904fdeea38109275aad8ae8
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