Security readout for executives and security teams
Plain-English summary
This is a Linux kernel floppy-driver memory leak. A local user who can trigger the vulnerable path could cause kernel memory exhaustion, affecting availability rather than data theft or tampering. The source does not show active exploitation.
Executive priority
Treat as a routine but real availability issue. Patch through normal kernel maintenance, faster on shared systems, development hosts, or environments with untrusted local users.
Technical view
The flaw is CWE-401 in do_floppy_init(). If floppy_alloc_disk() fails after blk_mq_alloc_tag_set() allocated tag data, error handling can skip freeing the latest tag set. CVSS is 5.5, local, low complexity, low privileges, no user interaction, availability impact high.
Likely exposure
Exposure is most relevant on Linux systems with the floppy driver present and loadable. The source lists Linux kernel versions and stable commits, but distribution backport status must be verified against vendor advisories.
Exploitation context
The CVSS vector indicates local, low-privilege exploitation with no user interaction. CISA KEV is false in the source bundle, and no cited source claims public exploitation or exploit availability.
Researcher notes
The evidence supports a memory leak during floppy module initialization failure, not confidentiality or integrity compromise. The affected-version data is limited in the bundle, so rely on kernel stable commits and distro advisories for exact exposure.
Mitigation direction
- Update to a vendor kernel containing the linked stable fixes.
- Check distribution advisories for backported fixes to your exact kernel package.
- Avoid loading the floppy driver where it is unnecessary, following vendor guidance.
- Prioritize systems where untrusted local users can load or trigger kernel modules.
Validation and detection
- Inventory Linux kernel versions and package build revisions across hosts.
- Check whether the floppy driver is present, built-in, or loadable.
- Map installed kernels to vendor advisories or the linked stable commits.
- Review kernel logs for floppy module load attempts and memory pressure events.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-401: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-50342 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H1.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/f36d8c8651506aea5f09899f5356ece5d1384f50CVE reference
- https://git.kernel.org/stable/c/75d8c8851a4da0190c2480e84315b5fd3d0356c5CVE reference
- https://git.kernel.org/stable/c/55b3c66a0d441cd37154ae95e44d0b82ccfd580eCVE reference
- https://git.kernel.org/stable/c/f8ace2e304c5dd8a7328db9cd2b8a4b1b98d83ecCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Release of Memory after Effective Lifetime
Missing Release of Memory after Effective Lifetime represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
