CVE-2026-72302: ASoC: SOF: ipc3-control: Use overflow checks in control_update size calc
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.17% (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 312c7d2ebe696da3f885eee77d52297664e57c53, 6856b3c23b0995eefad5a6142b4365ef70e1fe4a, 711d912b18763af62a63aa8f2419a774eb63bba4.
Low priority for now. Upgrade to Linux Linux 312c7d2ebe696da3f885eee77d52297664e57c53, 6856b3c23b0995eefad5a6142b4365ef70e1fe4a, 711d912b18763af62a63aa8f2419a774eb63bba4 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-control: Use overflow checks in control_update size calc In sof_ipc3_control_update(), the expected_size calculation uses firmware-provided cdata->num_elems in arithmetic that could overflow on 32-bit platforms, wrapping to a small value. This would allow the cdata->rhdr.hdr.size comparison to pass with mismatched sizes, potentially leading to out-of-bounds access in snd_sof_update_control. Use check_mul_overflow() and check_add_overflow() to detect and reject overflowed size calculations.
- Published
- Aug 15, 2026
- Updated
- Oct 16, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
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.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
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.
—
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
- 10f461d79c2d1afb22344986cc1b4631169cf25e and later · before 6856b3c23b0995eefad5a6142b4365ef70e1fe4aaffected · git
- 10f461d79c2d1afb22344986cc1b4631169cf25e and later · before 89a2309a9eec80d4c19e3aed62c4f923594d1911affected · git
- 10f461d79c2d1afb22344986cc1b4631169cf25e and later · before ffd79e77f2fbacd7a5d40ad1d4c7f3f089a8f2f3affected · git
- 10f461d79c2d1afb22344986cc1b4631169cf25e and later · before 711d912b18763af62a63aa8f2419a774eb63bba4affected · git
- 10f461d79c2d1afb22344986cc1b4631169cf25e and later · before 312c7d2ebe696da3f885eee77d52297664e57c53affected · git
- 10f461d79c2d1afb22344986cc1b4631169cf25e and later · before 8791977d7289f6e9d2b014f60a5455f053a7bc04affected · git
- before 5.18not affected · semver
- 6.1.178 and later · up to and including 6.1.*not affected · semver
- 6.6.145 and later · up to and including 6.6.*not affected · semver
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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.100-1 | 6.12.100-1 |
| Debian:14 | linux | before 7.1.5-1 | 7.1.5-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-2026-72299Aug 15, 2026 · tipc: restrict socket queue dumps in enqueue tracepoints39Monitor
- ← EarlierCVE-2026-72301Aug 15, 2026 · ASoC: SOF: ipc3-control: Fix TOCTOU in bytes_put and bytes_get31Monitor
- Later →CVE-2026-72303Aug 15, 2026 · ASoC: SOF: ipc4-control: Validate notification payload size31Monitor
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 | 312c7d2ebe696da3f885eee77d52297664e57c53 | Vendor (CNA) |
| Linux Linux | 6856b3c23b0995eefad5a6142b4365ef70e1fe4a | Vendor (CNA) |
| Linux Linux | 711d912b18763af62a63aa8f2419a774eb63bba4 | Vendor (CNA) |
| Linux Linux | 8791977d7289f6e9d2b014f60a5455f053a7bc04 | Vendor (CNA) |
| Linux Linux | 89a2309a9eec80d4c19e3aed62c4f923594d1911 | Vendor (CNA) |
| Linux Linux | ffd79e77f2fbacd7a5d40ad1d4c7f3f089a8f2f3 | Vendor (CNA) |
| debian:linux | 6.1.180-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.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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
- 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)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
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
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/6856b3c23b0995eefad5a6142b4365ef70e1fe4a
- git.kernel.org/stable/c/711d912b18763af62a63aa8f2419a774eb63bba4
- git.kernel.org/stable/c/8791977d7289f6e9d2b014f60a5455f053a7bc04
- git.kernel.org/stable/c/89a2309a9eec80d4c19e3aed62c4f923594d1911
- git.kernel.org/stable/c/ffd79e77f2fbacd7a5d40ad1d4c7f3f089a8f2f3
Vendor advisories and official records. Exploit/PoC links are deliberately left out.