CVE-2022-50400: staging: greybus: audio_helper: remove unused and wrong debugfs usage
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.14% (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 4dab0d27a4211a27135a6899d6c737e6e0759a11, 5699afbff1fa2972722e863906c0320d55dd4d58, d0febad83e29d85bb66e4f5cac0115b022403338.
Low priority for now. Upgrade to Linux Linux 4dab0d27a4211a27135a6899d6c737e6e0759a11, 5699afbff1fa2972722e863906c0320d55dd4d58, d0febad83e29d85bb66e4f5cac0115b022403338 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: staging: greybus: audio_helper: remove unused and wrong debugfs usage In the greybus audio_helper code, the debugfs file for the dapm has the potential to be removed and memory will be leaked. There is also the very real potential for this code to remove ALL debugfs entries from the system, and it seems like this is what will really happen if this code ever runs. This all is very wrong as the greybus audio driver did not create this debugfs file, the sound core did and controls the lifespan of it. So remove all of the debugfs logic from the audio_helper code as there's no way it could be correct. If this really is needed, it can come back with a fixup for the incorrect usage of the debugfs_lookup() call which is what caused this to be noticed at all.
- Published
- Sep 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th 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%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
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 kernelbefore 5.10.150
- linux linux kernel5.11 and later · before 5.15.75
- linux linux kernel5.16 and later · before 5.19.17
- linux linux kernel6.0 and later · before 6.0.3
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.9affected
- 510e340efe0cbd379cf1ff3490d088c3299749b1 and later · before d0febad83e29d85bb66e4f5cac0115b022403338affected · git
- 510e340efe0cbd379cf1ff3490d088c3299749b1 and later · before 4dab0d27a4211a27135a6899d6c737e6e0759a11affected · git
- 510e340efe0cbd379cf1ff3490d088c3299749b1 and later · before 5699afbff1fa2972722e863906c0320d55dd4d58affected · git
- 510e340efe0cbd379cf1ff3490d088c3299749b1 and later · before d835fa49d9589a780ff0d001bb7e6323238a4afbaffected · git
- 510e340efe0cbd379cf1ff3490d088c3299749b1 and later · before d517cdeb904ddc0cbebcc959d43596426cac40b0affected · git
- before 5.9not affected · semver
- 5.10.150 and later · up to and including 5.10.*not affected · semver
- 5.15.75 and later · up to and including 5.15.*not affected · semver
- 5.19.17 and later · up to and including 5.19.*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.0.3-1 | 6.0.3-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-50398Sep 18, 2025 · drm/msm/dp: add atomic_check to bridge ops22Monitor
- ← EarlierCVE-2022-50399Sep 18, 2025 · media: atomisp: prevent integer overflow in sh_css_set_black_frame()22Monitor
- Later →CVE-2023-53369Sep 18, 2025 · net: dcb: choose correct policy to parse DCB_ATTR_BCN22Monitor
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 | 4dab0d27a4211a27135a6899d6c737e6e0759a11 | Vendor (CNA) |
| Linux Linux | 5699afbff1fa2972722e863906c0320d55dd4d58 | Vendor (CNA) |
| Linux Linux | d0febad83e29d85bb66e4f5cac0115b022403338 | Vendor (CNA) |
| Linux Linux | d517cdeb904ddc0cbebcc959d43596426cac40b0 | Vendor (CNA) |
| Linux Linux | d835fa49d9589a780ff0d001bb7e6323238a4afb | Vendor (CNA) |
| debian:linux | 6.0.3-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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.