ASoC: meson: Keep link pointers valid on realloc failure
Noroxi assessment
Priority: Monitor (action score 29/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.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 0b30fbe6bf7cf6499b19dd886f466e7c9e820089, 1c1485343b7c1c39dab7ecb9cd16ba49fd0ce642, 2aaa41cf974f83a6fb105422bac4e2f107150774.
Low priority for now. Upgrade to Linux Linux 0b30fbe6bf7cf6499b19dd886f466e7c9e820089, 1c1485343b7c1c39dab7ecb9cd16ba49fd0ce642, 2aaa41cf974f83a6fb105422bac4e2f107150774 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: meson: Keep link pointers valid on realloc failure meson_card_reallocate_links() grows the DAI link and private data arrays with two consecutive krealloc() calls and updates the owner pointers only after both calls have succeeded. A successful krealloc() may move the data: it frees the old block and returns a new one. When that happens for the link array and the second krealloc() then fails, card->dai_link still points to the block that krealloc() already freed, and the error path frees the new block too. The probe error path then calls meson_card_clean_references(), which dereferences card->dai_link and kfree()s it again, resulting in a use-after-free and a double free. Commit card->dai_link and card->num_links right after the first krealloc() succeeds, so the pointer always refers to a valid allocation that meson_card_clean_references() can walk and free. krealloc() with __GFP_ZERO zero-initializes the added entries, so walking them on the error path is safe. With both failure paths reduced to a plain return, drop the goto labels and the error message.
- Published
- Sep 17, 2026
- Updated
- Sep 18, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
29
Monitor
Low priority for now.
- CVSS
- 29 / 40 · 7.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.4
- 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
- 4.19affected
- 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b and later · before de33afc57f24538186bccf4c4f6c65dd38634fd8affected · git
- 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b and later · before 1c1485343b7c1c39dab7ecb9cd16ba49fd0ce642affected · git
- 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b and later · before 8db0a0fc84e80aa9924e0833aef6cc95df94e5a7affected · git
- 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b and later · before 41e92e0caa1fe3df2efaca346bfcaeb7fb9826abaffected · git
- 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b and later · before 0b30fbe6bf7cf6499b19dd886f466e7c9e820089affected · git
- 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b and later · before 8fec16898f184e5f8f8fdd09ff1ced2bd7ffc13daffected · git
- 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b and later · before 5ed1b048527bebe4529eb6e01c34dcc5d97ba5feaffected · git
- 7864a79f37b55769b817d5e6c5ae0ca4bfdba93b and later · before 2aaa41cf974f83a6fb105422bac4e2f107150774affected · git
- before 4.19not 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.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-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-93037Sep 17, 2026 · RDMA/hfi1: Propagate sdma_txinit_ahg() errors31Monitor
- ← EarlierCVE-2026-93038Sep 17, 2026 · iio: dac: ad5686: missing NULL check on match data0Monitor
- Later →CVE-2026-93040Sep 17, 2026 · dmaengine: dw-edma: Serialize channel state checks0Monitor
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 | 0b30fbe6bf7cf6499b19dd886f466e7c9e820089 | Vendor (CNA) |
| Linux Linux | 1c1485343b7c1c39dab7ecb9cd16ba49fd0ce642 | Vendor (CNA) |
| Linux Linux | 2aaa41cf974f83a6fb105422bac4e2f107150774 | Vendor (CNA) |
| Linux Linux | 41e92e0caa1fe3df2efaca346bfcaeb7fb9826ab | Vendor (CNA) |
| Linux Linux | 5ed1b048527bebe4529eb6e01c34dcc5d97ba5fe | Vendor (CNA) |
| Linux Linux | 8db0a0fc84e80aa9924e0833aef6cc95df94e5a7 | Vendor (CNA) |
| Linux Linux | 8fec16898f184e5f8f8fdd09ff1ced2bd7ffc13d | Vendor (CNA) |
| Linux Linux | de33afc57f24538186bccf4c4f6c65dd38634fd8 | Vendor (CNA) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · 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.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
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
- High
- Privileges required
- None
- 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:H/PR:N/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/1c1485343b7c1c39dab7ecb9cd16ba49fd0ce642
- git.kernel.org/stable/c/2aaa41cf974f83a6fb105422bac4e2f107150774
- git.kernel.org/stable/c/41e92e0caa1fe3df2efaca346bfcaeb7fb9826ab
- git.kernel.org/stable/c/5ed1b048527bebe4529eb6e01c34dcc5d97ba5fe
- git.kernel.org/stable/c/8db0a0fc84e80aa9924e0833aef6cc95df94e5a7
- git.kernel.org/stable/c/8fec16898f184e5f8f8fdd09ff1ced2bd7ffc13d
- git.kernel.org/stable/c/de33afc57f24538186bccf4c4f6c65dd38634fd8
Vendor advisories and official records. Exploit/PoC links are deliberately left out.