Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-72261: ASoC: SOF: ipc3-control: Validate size in snd_sof_update_control

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.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 1dc25a3e06364f48c4ef06016852f8b82425151a, 2a591bf6fd41fd14bdae689aafac4a9ee702c23c, 390aa4c9339bb0ec0bc8d554e830faf93ca9d49e.

Low priority for now. Upgrade to Linux Linux 1dc25a3e06364f48c4ef06016852f8b82425151a, 2a591bf6fd41fd14bdae689aafac4a9ee702c23c, 390aa4c9339bb0ec0bc8d554e830faf93ca9d49e 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: Validate size in snd_sof_update_control In snd_sof_update_control(), firmware-provided cdata->num_elems is checked against local_cdata->data->size but never against the actual allocation size. If local_cdata->data->size was previously set to an inconsistent value, the memcpy could write past the allocated buffer. Add a bounds check to ensure num_elems fits within the available space in the ipc_control_data allocation before copying.

Published
Aug 15, 2026
Updated
Oct 16, 2026
EPSS
0.1% · 6th 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-72261

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
    • 10f461d79c2d1afb22344986cc1b4631169cf25e and later · before 1dc25a3e06364f48c4ef06016852f8b82425151aaffected · git
    • 10f461d79c2d1afb22344986cc1b4631169cf25e and later · before ee781058cd4d71e4449f41cbe6a3b8c59daa2c51affected · git
    • 10f461d79c2d1afb22344986cc1b4631169cf25e and later · before ecf67f1302f2080b4d241b973364aacda70ad740affected · git
    • 10f461d79c2d1afb22344986cc1b4631169cf25e and later · before d3abaedf6a58469610136d2dace1a85cddf7afcfaffected · git
    • 10f461d79c2d1afb22344986cc1b4631169cf25e and later · before 2a591bf6fd41fd14bdae689aafac4a9ee702c23caffected · git
    • 10f461d79c2d1afb22344986cc1b4631169cf25e and later · before 390aa4c9339bb0ec0bc8d554e830faf93ca9d49eaffected · 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.

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.167.1.el8_104.18.0-553.167.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.167.1.rt7.508.el8_104.18.0-553.167.1.rt7.508.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.167.1.rt7.508.el8_104.18.0-553.167.1.rt7.508.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.167.1.rt7.508.el8_104.18.0-553.167.1.rt7.508.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.167.1.rt7.508.el8_104.18.0-553.167.1.rt7.508.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.167.1.rt7.508.el8_104.18.0-553.167.1.rt7.508.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.167.1.rt7.508.el8_104.18.0-553.167.1.rt7.508.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.167.1.rt7.508.el8_104.18.0-553.167.1.rt7.508.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.167.1.rt7.508.el8_104.18.0-553.167.1.rt7.508.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.167.1.rt7.508.el8_104.18.0-553.167.1.rt7.508.el8_10

+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-72255Aug 15, 2026 · netfilter: nf_queue: pin bridge device while NFQUEUE holds fake dst
    31Monitor
  • ← EarlierCVE-2026-72256Aug 15, 2026 · netfilter: xt_cluster: reject template conntracks in hash match
    0Monitor
  • Later →CVE-2026-72262Aug 15, 2026 · ASoC: SOF: ipc3-control: Fix heap overflow in bytes_ext put/get
    31Monitor

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 Linux1dc25a3e06364f48c4ef06016852f8b82425151aVendor (CNA)
Linux Linux2a591bf6fd41fd14bdae689aafac4a9ee702c23cVendor (CNA)
Linux Linux390aa4c9339bb0ec0bc8d554e830faf93ca9d49eVendor (CNA)
Linux Linuxd3abaedf6a58469610136d2dace1a85cddf7afcfVendor (CNA)
Linux Linuxecf67f1302f2080b4d241b973364aacda70ad740Vendor (CNA)
Linux Linuxee781058cd4d71e4449f41cbe6a3b8c59daa2c51Vendor (CNA)
almalinux:bpftool4.18.0-553.167.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.167.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-core4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-core4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-devel4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-debug-modules-extra4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-devel4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-rt-modules-extra4.18.0-553.167.1.rt7.508.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.180-1 · Debian:12Package registry (OSV)
red hat:kernel-rt0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-core0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-core0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-debuginfo0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-devel0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-kvm0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debug-modules-extra0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo0:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)
red hat:kernel-rt-debuginfo-common-x86_640:4.18.0-553.167.1.rt7.508.el8_10 · Red Hat:enterprise_linux:8::nfvPackage registry (OSV)

+2

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