Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72262: ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get

HighCVSS 7.8 · v3.1—No exploit Fix available

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.18% (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 121577383b5cf221e86581e0f2bcca4c66f17469, 1adde1941bba7b0d7104b86ed819d48d81cb0ad9, af4b437a463ac0482ba705434a44da06783778e6.

Low priority for now. Upgrade to Linux Linux 121577383b5cf221e86581e0f2bcca4c66f17469, 1adde1941bba7b0d7104b86ed819d48d81cb0ad9, af4b437a463ac0482ba705434a44da06783778e6 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: Fix heap overflow in bytes_ext put/get The ipc_control_data buffer is allocated as kzalloc(max_size), where max_size covers the entire struct sof_ipc_ctrl_data including its flexible array payload. However, the bounds checks in bytes_ext_put and _bytes_ext_get compared user data lengths against max_size directly, ignoring that cdata->data sits at an offset of sizeof(struct sof_ipc_ctrl_data) bytes into the allocation. This allowed writing up to sizeof(struct sof_ipc_ctrl_data) bytes past the end of the heap buffer from unprivileged userspace via the ALSA TLV kcontrol interface, and similarly allowed over-reading adjacent heap data on the get path. Fix all bounds checks to subtract sizeof(*cdata) from max_size so they reflect the actual space available at the cdata->data offset. Also fix the error-path restore in bytes_ext_put which wrote to cdata->data instead of cdata, causing the same overflow.

Published
Aug 15, 2026
Updated
Oct 16, 2026
EPSS
0.1% · 7th percentile
CWE
—

Report tools

JSON

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.

Follow CVE-2026-72262

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

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 help

Affected 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
    • 67ec2a091630c28ea8d05db2bd7178a05b04b7e6 and later · before af4b437a463ac0482ba705434a44da06783778e6affected · git
    • 67ec2a091630c28ea8d05db2bd7178a05b04b7e6 and later · before 1adde1941bba7b0d7104b86ed819d48d81cb0ad9affected · git
    • 67ec2a091630c28ea8d05db2bd7178a05b04b7e6 and later · before eaa67e139c9217099e2a7b717aeeb46c65de3494affected · git
    • 67ec2a091630c28ea8d05db2bd7178a05b04b7e6 and later · before 121577383b5cf221e86581e0f2bcca4c66f17469affected · git
    • 67ec2a091630c28ea8d05db2bd7178a05b04b7e6 and later · before f4933e1d11b97b6a0951648b7c3e53850e1b33a9affected · git
    • 67ec2a091630c28ea8d05db2bd7178a05b04b7e6 and later · before fd46668d538993218eea19c6925c868ac0f2630caffected · git
    • before 5.18not affected · semver
    • 6.1.184 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.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.66.1.el10_26.12.0-211.66.1.el10_2

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-72256Aug 15, 2026 · netfilter: xt_cluster: reject template conntracks in hash match
    0Monitor
  • ← EarlierCVE-2026-72261Aug 15, 2026 · ASoC: SOF: ipc3-control: Validate size in snd_sof_update_control
    31Monitor
  • Later →CVE-2026-72265Aug 15, 2026 · fbdev: nvidia: fix potential memory leak in nvidiafb_probe()
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux121577383b5cf221e86581e0f2bcca4c66f17469Vendor (CNA)
Linux Linux1adde1941bba7b0d7104b86ed819d48d81cb0ad9Vendor (CNA)
Linux Linuxaf4b437a463ac0482ba705434a44da06783778e6Vendor (CNA)
Linux Linuxeaa67e139c9217099e2a7b717aeeb46c65de3494Vendor (CNA)
Linux Linuxf4933e1d11b97b6a0951648b7c3e53850e1b33a9Vendor (CNA)
Linux Linuxfd46668d538993218eea19c6925c868ac0f2630cVendor (CNA)
almalinux:bpftool4.18.0-553.174.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.174.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-687.58.1.el9_8 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.174.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.174.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.174.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.174.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.174.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.174.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.174.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.174.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.174.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.174.1.el8_10 · AlmaLinux:8Package registry (OSV)

+36

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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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.

References

Show all references (5 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records