CVE-2022-50115: ASoC: SOF: ipc3-topology: Prevent double freeing of ipc_control_data via load_bytes
Noroxi assessment
Priority: Monitor (action score 31/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.20% (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 8463986b54295e6b65ddf2b7c65627d01ce7643b, c2eddfcafcffaf1b9245ea0dde9143bbfb47d5d1, d5bd47f3ca124058a8e87eae4508afeda2132611.
Low priority for now. Upgrade to Linux Linux 8463986b54295e6b65ddf2b7c65627d01ce7643b, c2eddfcafcffaf1b9245ea0dde9143bbfb47d5d1, d5bd47f3ca124058a8e87eae4508afeda2132611 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: ASoC: SOF: ipc3-topology: Prevent double freeing of ipc_control_data via load_bytes We have sanity checks for byte controls and if any of the fail the locally allocated scontrol->ipc_control_data is freed up, but not set to NULL. On a rollback path of the error the higher level code will also try to free the scontrol->ipc_control_data which will eventually going to lead to memory corruption as double freeing memory is not a good thing.
- Published
- Jun 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- CWE-415
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- 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.
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 kernel5.18 and later · before 5.18.18
- linux linux kernel5.19 and later · before 5.19.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
- 5.18affected
- b5cee8feb1d482a9d07b677f4f2f9565bacda53e and later · before 8463986b54295e6b65ddf2b7c65627d01ce7643baffected · git
- b5cee8feb1d482a9d07b677f4f2f9565bacda53e and later · before c2eddfcafcffaf1b9245ea0dde9143bbfb47d5d1affected · git
- b5cee8feb1d482a9d07b677f4f2f9565bacda53e and later · before d5bd47f3ca124058a8e87eae4508afeda2132611affected · git
- before 5.18not affected · semver
- 5.18.18 and later · up to and including 5.18.*not affected · semver
- 5.19.2 and later · up to and including 5.19.*not affected · semver
- 6.0 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.2-1 | 6.0.2-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-50113Jun 18, 2025 · ASoc: audio-graph-card2: Fix refcount leak bug in __graph_get_type()22Monitor
- ← EarlierCVE-2022-50114Jun 18, 2025 · net: 9p: fix refcount leak in p9_read_work() error handling22Monitor
- Later →CVE-2022-50116Jun 18, 2025 · tty: n_gsm: fix deadlock and link starvation in outgoing data path22Monitor
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 | 8463986b54295e6b65ddf2b7c65627d01ce7643b | Vendor (CNA) |
| Linux Linux | c2eddfcafcffaf1b9245ea0dde9143bbfb47d5d1 | Vendor (CNA) |
| Linux Linux | d5bd47f3ca124058a8e87eae4508afeda2132611 | Vendor (CNA) |
| debian:linux | 6.0.2-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.
- CVE-2026-31608310 days apartsmb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list()39Monitor
- CVE-2026-31609310 days apartsmb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()39Monitor
- CVE-2026-43011317 days apartnet/x25: Fix potential double free of skb39Monitor
- CVE-2026-43414324 days apartscsi: qla2xxx: Completely fix fcport double free39Monitor
- CVE-2026-52993371 days aparttipc: fix double-free in tipc_buf_append()39Monitor
- CVE-2026-63888396 days apartscsi: target: iscsi: Fix CRC overread and double-free in iscsit_handle_text_cmd()39Monitor
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
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-415 · Double FreeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.