CVE-2022-50721: dmaengine: qcom-adm: fix wrong calling convention for prep_slave_sg
Noroxi assessment
Priority: Monitor (action score 0/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.23% (FIRST EPSS).
- Fixed version: Linux Linux 5653bd0200944e5803fa8e32dc36aa49931312f9, 9a041174c58a226e713f6cebd41eccec7a5cfa72, b9d2140c3badf4107973ad77c5a0ec3075705c85.
Low priority for now. Upgrade to Linux Linux 5653bd0200944e5803fa8e32dc36aa49931312f9, 9a041174c58a226e713f6cebd41eccec7a5cfa72, b9d2140c3badf4107973ad77c5a0ec3075705c85 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: dmaengine: qcom-adm: fix wrong calling convention for prep_slave_sg The calling convention for pre_slave_sg is to return NULL on error and provide an error log to the system. Qcom-adm instead provide error pointer when an error occur. This indirectly cause kernel panic for example for the nandc driver that checks only if the pointer returned by device_prep_slave_sg is not NULL. Returning an error pointer makes nandc think the device_prep_slave_sg function correctly completed and makes the kernel panics later in the code. While nandc is the one that makes the kernel crash, it was pointed out that the real problem is qcom-adm not following calling convention for that function. To fix this, drop returning error pointer and return NULL with an error log.
- Published
- Dec 24, 2025
- Updated
- Nov 10, 2026
- EPSS
- 0.2% · 14th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
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.
Is your version affected? Check itNoroxi 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.
—
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
- 5.11affected
- 5c9f8c2dbdbe53818bcde6aa6695e1331e5f841f and later · before 5653bd0200944e5803fa8e32dc36aa49931312f9affected · git
- 5c9f8c2dbdbe53818bcde6aa6695e1331e5f841f and later · before 9a041174c58a226e713f6cebd41eccec7a5cfa72affected · git
- 5c9f8c2dbdbe53818bcde6aa6695e1331e5f841f and later · before b9d2140c3badf4107973ad77c5a0ec3075705c85affected · git
- before 5.11not affected · semver
- 5.19.17 and later · up to and including 5.19.*not affected · semver
- 6.0.3 and later · up to and including 6.0.*not affected · semver
- 6.1 and laternot affected · original_commit_for_fix
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.0.3-1 | 6.0.3-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2022-50719Dec 24, 2025 · ALSA: line6: fix stack overflow in line6_midi_transmit31Monitor
- ← EarlierCVE-2022-50720Dec 24, 2025 · x86/apic: Don't disable x2APIC if locked0Monitor
- Later →CVE-2022-50722Dec 24, 2025 · media: ipu3-imgu: Fix NULL pointer dereference in active selection access0Monitor
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 | 5653bd0200944e5803fa8e32dc36aa49931312f9 | Vendor (CNA) |
| Linux Linux | 9a041174c58a226e713f6cebd41eccec7a5cfa72 | Vendor (CNA) |
| Linux Linux | b9d2140c3badf4107973ad77c5a0ec3075705c85 | Vendor (CNA) |
| debian:linux | 6.0.3-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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.