CVE-2022-50431: ALSA: aoa: i2sbus: fix possible memory leak in i2sbus_add_dev()
Noroxi assessment
Priority: Monitor (action score 22/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 027fee10e3a400cf6f3237374a1248da1082807b, 4a4c8482e370d697738a78dcd7bf2780832cb712, 5bdea674534153110b90d70b02f2fbaf48b2c0eb.
Low priority for now. Upgrade to Linux Linux 027fee10e3a400cf6f3237374a1248da1082807b, 4a4c8482e370d697738a78dcd7bf2780832cb712, 5bdea674534153110b90d70b02f2fbaf48b2c0eb 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: ALSA: aoa: i2sbus: fix possible memory leak in i2sbus_add_dev() dev_set_name() in soundbus_add_one() allocates memory for name, it need be freed when of_device_register() fails, call soundbus_dev_put() to give up the reference that hold in device_initialize(), so that it can be freed in kobject_cleanup() when the refcount hit to 0. And other resources are also freed in i2sbus_release_dev(), so it can return 0 directly.
- Published
- Oct 1, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 5th percentile
- CWE
- CWE-401
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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 kernel2.6.18 and later · before 4.9.332
- linux linux kernel4.10 and later · before 4.14.298
- linux linux kernel4.15 and later · before 4.19.264
- linux linux kernel4.20 and later · before 5.4.223
- linux linux kernel5.5 and later · before 5.10.153
- linux linux kernel5.11 and later · before 5.15.77
- linux linux kernel5.16 and later · before 6.0.7
- linux linux kernel6.1
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
- 2.6.18affected
- f3d9478b2ce468c3115b02ecae7e975990697f15 and later · before fd410d24665e4efb3c1796797181265efe553e9caffected · git
- f3d9478b2ce468c3115b02ecae7e975990697f15 and later · before 802532a50acf501fdafe38a84ca2aa886d68af68affected · git
- f3d9478b2ce468c3115b02ecae7e975990697f15 and later · before 027fee10e3a400cf6f3237374a1248da1082807baffected · git
- f3d9478b2ce468c3115b02ecae7e975990697f15 and later · before 5bdea674534153110b90d70b02f2fbaf48b2c0ebaffected · git
- f3d9478b2ce468c3115b02ecae7e975990697f15 and later · before ce6fd1c382a38b75557db85a2fe99d285540a03daffected · git
- f3d9478b2ce468c3115b02ecae7e975990697f15 and later · before e81d7826b8f40430a1ea1b330e24d9a9eb4512c4affected · git
- f3d9478b2ce468c3115b02ecae7e975990697f15 and later · before c7524279c8ddc7dbf3463bec70e0289097959944affected · git
- f3d9478b2ce468c3115b02ecae7e975990697f15 and later · before 4a4c8482e370d697738a78dcd7bf2780832cb712affected · git
- before 2.6.18not 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.0.7-1 | 6.0.7-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-50430Oct 1, 2025 · mmc: vub300: fix warning - do not call blocking ops when !TASK_RUNNING22Monitor
- ← EarlierCVE-2025-39916Oct 1, 2025 · mm/damon/reclaim: avoid divide-by-zero in damon_reclaim_apply_parameters()22Monitor
- Later →CVE-2025-39917Oct 1, 2025 · bpf: Fix out-of-bounds dynptr write in bpf_crypto_crypt31Monitor
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 | 027fee10e3a400cf6f3237374a1248da1082807b | Vendor (CNA) |
| Linux Linux | 4a4c8482e370d697738a78dcd7bf2780832cb712 | Vendor (CNA) |
| Linux Linux | 5bdea674534153110b90d70b02f2fbaf48b2c0eb | Vendor (CNA) |
| Linux Linux | 802532a50acf501fdafe38a84ca2aa886d68af68 | Vendor (CNA) |
| Linux Linux | c7524279c8ddc7dbf3463bec70e0289097959944 | Vendor (CNA) |
| Linux Linux | ce6fd1c382a38b75557db85a2fe99d285540a03d | Vendor (CNA) |
| Linux Linux | e81d7826b8f40430a1ea1b330e24d9a9eb4512c4 | Vendor (CNA) |
| Linux Linux | fd410d24665e4efb3c1796797181265efe553e9c | Vendor (CNA) |
| debian:linux | 6.0.7-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.
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
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-401 · Missing Release of Memory after Effective LifetimeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 (7 more)Show less
- git.kernel.org/stable/c/4a4c8482e370d697738a78dcd7bf2780832cb712
- git.kernel.org/stable/c/5bdea674534153110b90d70b02f2fbaf48b2c0eb
- git.kernel.org/stable/c/802532a50acf501fdafe38a84ca2aa886d68af68
- git.kernel.org/stable/c/c7524279c8ddc7dbf3463bec70e0289097959944
- git.kernel.org/stable/c/ce6fd1c382a38b75557db85a2fe99d285540a03d
- git.kernel.org/stable/c/e81d7826b8f40430a1ea1b330e24d9a9eb4512c4
- git.kernel.org/stable/c/fd410d24665e4efb3c1796797181265efe553e9c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.