CVE-2022-50501: media: coda: Add check for dcoda_iram_alloc
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 05f165ded4a7baec31b65aba88e2cd1fb9b91db2, 2b436f1410245412ea5e4c356a175a928d73eed3, 2c6887d5a29024bada6928d1d0959c9990401384.
Low priority for now. Upgrade to Linux Linux 05f165ded4a7baec31b65aba88e2cd1fb9b91db2, 2b436f1410245412ea5e4c356a175a928d73eed3, 2c6887d5a29024bada6928d1d0959c9990401384 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: media: coda: Add check for dcoda_iram_alloc As the coda_iram_alloc may return NULL pointer, it should be better to check the return value in order to avoid NULL poineter dereference, same as the others.
- Published
- Oct 4, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.17 and later · before 4.9.337
- linux linux kernel4.10 and later · before 4.14.303
- linux linux kernel4.15 and later · before 4.19.270
- linux linux kernel4.20 and later · before 5.4.229
- linux linux kernel5.5 and later · before 5.10.163
- linux linux kernel5.11 and later · before 5.15.86
- linux linux kernel5.16 and later · before 6.0.16
- linux linux kernel6.1 and later · before 6.1.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.17affected
- b313bcc9a46795c0233a765411cef9a15caaa7fb and later · before 5688d33aa293dfa122d66bef9c0258ddf7ef11e7affected · git
- b313bcc9a46795c0233a765411cef9a15caaa7fb and later · before 2c6887d5a29024bada6928d1d0959c9990401384affected · git
- b313bcc9a46795c0233a765411cef9a15caaa7fb and later · before 45f57abaee136a1e39d2b04443a1bd5311ba7d94affected · git
- b313bcc9a46795c0233a765411cef9a15caaa7fb and later · before 2b436f1410245412ea5e4c356a175a928d73eed3affected · git
- b313bcc9a46795c0233a765411cef9a15caaa7fb and later · before 35ddd00b36589cf948875b825eedaab1aefd5ad5affected · git
- b313bcc9a46795c0233a765411cef9a15caaa7fb and later · before b99872178e7473f21904fdeea38109275aad8ae8affected · git
- b313bcc9a46795c0233a765411cef9a15caaa7fb and later · before 532417dc98cb9c1185ada4ea4e7ccf965c06bcb5affected · git
- b313bcc9a46795c0233a765411cef9a15caaa7fb and later · before 05f165ded4a7baec31b65aba88e2cd1fb9b91db2affected · git
- b313bcc9a46795c0233a765411cef9a15caaa7fb and later · before 6b8082238fb8bb20f67e46388123e67a5bbc558daffected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.4-1 | 6.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-50496Oct 4, 2025 · dm cache: Fix UAF in destroy()31Monitor
- ← EarlierCVE-2022-50499Oct 4, 2025 · media: dvb-core: Fix double free in dvb_register_device()31Monitor
- Later →CVE-2022-50503Oct 4, 2025 · mtd: lpddr2_nvm: Fix possible null-ptr-deref22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 05f165ded4a7baec31b65aba88e2cd1fb9b91db2 | Vendor (CNA) |
| Linux Linux | 2b436f1410245412ea5e4c356a175a928d73eed3 | Vendor (CNA) |
| Linux Linux | 2c6887d5a29024bada6928d1d0959c9990401384 | Vendor (CNA) |
| Linux Linux | 35ddd00b36589cf948875b825eedaab1aefd5ad5 | Vendor (CNA) |
| Linux Linux | 45f57abaee136a1e39d2b04443a1bd5311ba7d94 | Vendor (CNA) |
| Linux Linux | 532417dc98cb9c1185ada4ea4e7ccf965c06bcb5 | Vendor (CNA) |
| Linux Linux | 5688d33aa293dfa122d66bef9c0258ddf7ef11e7 | Vendor (CNA) |
| Linux Linux | 6b8082238fb8bb20f67e46388123e67a5bbc558d | Vendor (CNA) |
| Linux Linux | b99872178e7473f21904fdeea38109275aad8ae8 | Vendor (CNA) |
| debian:linux | 6.1.4-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/2b436f1410245412ea5e4c356a175a928d73eed3
- git.kernel.org/stable/c/2c6887d5a29024bada6928d1d0959c9990401384
- git.kernel.org/stable/c/35ddd00b36589cf948875b825eedaab1aefd5ad5
- git.kernel.org/stable/c/45f57abaee136a1e39d2b04443a1bd5311ba7d94
- git.kernel.org/stable/c/532417dc98cb9c1185ada4ea4e7ccf965c06bcb5
- git.kernel.org/stable/c/5688d33aa293dfa122d66bef9c0258ddf7ef11e7
- git.kernel.org/stable/c/6b8082238fb8bb20f67e46388123e67a5bbc558d
- git.kernel.org/stable/c/b99872178e7473f21904fdeea38109275aad8ae8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.