Security readout for executives and security teams
Plain-English summary
CVE-2022-50404 is a Linux kernel memory leak in the framebuffer console font handling path. A local user with low privileges could trigger failed font handling and consume kernel memory, creating an availability risk. The sources do not show data theft, integrity impact, or confirmed active exploitation.
Executive priority
Treat as a normal-cycle kernel availability fix, elevated for shared Linux environments. It is not described as remotely exploitable, actively exploited, or data-exposing in the provided sources, but unpatched local availability bugs can still disrupt critical systems.
Technical view
The issue is CWE-401 in fbdev/fbcon. When fbcon_do_set_font() failed, code introduced by a prior change did not release a buffer that could be newly allocated by fbcon_set_font(). CVSS 3.1 is 5.5: local access, low complexity, low privileges, no user interaction, high availability impact only.
Likely exposure
Exposure is most relevant on Linux systems running affected kernel versions or commits with framebuffer console code present. Practical concern is higher on shared, multi-user, workstation, kiosk, lab, or container-host environments where untrusted local users can obtain shell access.
Exploitation context
The bundle marks CISA KEV as false and provides no cited evidence of exploitation in the wild. The CVSS vector indicates exploitation requires local low-privileged access and affects availability, not confidentiality or integrity.
Researcher notes
The affected data in the bundle mixes commit identifiers and kernel versions, so branch-specific impact should be verified against distribution backports. The fix direction is clear: release the newly allocated buffer when fbcon_do_set_font() fails.
Mitigation direction
- Update to a vendor kernel containing the referenced stable fixes.
- Check distribution advisories for the exact fixed package for your kernel branch.
- Prioritize systems that allow untrusted local users or interactive shells.
- Avoid direct wrangler-style assumptions; follow vendor kernel guidance for production rollout.
Validation and detection
- Inventory running Linux kernel versions across servers, workstations, and appliances.
- Map kernels to vendor advisories or the listed upstream stable commits.
- Confirm vulnerable systems are upgraded and rebooted into the fixed kernel.
- Review local-user exposure on systems that cannot be patched quickly.
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-50404 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/5a341810a22e51c3a7a108f7896b5fd58d44d127CVE reference
- https://git.kernel.org/stable/c/88ec6d11052da527eb9268831e7a9bc5bbad02f6CVE reference
- https://git.kernel.org/stable/c/06926607b9fddf7ce8017493899ce6eb7e79a123CVE reference
- https://git.kernel.org/stable/c/a609bfc1e644a8467cb31945ed1488374ebdc013CVE reference
- https://git.kernel.org/stable/c/3c3bfb8586f848317ceba5d777e11204ba3e5758CVE 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.