CVE-2022-49419: video: fbdev: vesafb: Fix a use-after-free due early fb_info cleanup
In the Linux kernel, the following vulnerability has been resolved:
video: fbdev: vesafb: Fix a use-after-free due early fb_info cleanup
Commit b3c9a924aab6 ("fbdev: vesafb: Cleanup fb_info in .fb_destroy rather
than .remove") fixed a use-after-free error due the vesafb driver freeing
the fb_info in the .remove handler instead of doing it in .fb_destroy.
This can happen if the .fb_destroy callback is executed after the .remove
callback, since the former tries to access a pointer freed by the latter.
But that change didn't take into account that another possible scenario is
that .fb_destroy is called before the .remove callback. For example, if no
process has the fbdev chardev opened by the time the driver is removed.
If that's the case, fb_info will be freed when unregister_framebuffer() is
called, making the fb_info pointer accessed in vesafb_remove() after that
to no longer be valid.
To prevent that, move the expression containing the info->par to happen
before the unregister_framebuffer() function call.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49419 is a Linux kernel use-after-free bug in the vesafb framebuffer driver. A local authenticated user could potentially trigger kernel memory corruption with high impact to confidentiality, integrity, and availability. It is not listed as CISA KEV, and the provided sources do not show active exploitation.
Executive priority
Treat as a high-priority Linux kernel maintenance item, especially where local users, containers, or workloads are not fully trusted. It is not an internet-facing remote bug based on the provided CVSS vector, but successful exploitation could compromise the host.
Technical view
The vesafb driver could access fb_info after it was freed when .fb_destroy and .remove callbacks occurred in different orders. The fix moves access to info->par before unregister_framebuffer() can free fb_info. The CVE is classified as CWE-416 with CVSS 3.1 score 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with the vesafb/fbdev path present or enabled. The source bundle lists affected Linux kernel versions and stable commit references, but it does not provide distribution-specific package status.
Exploitation context
Attack requires local privileges and no user interaction. The impact is kernel-level memory corruption, which can support privilege escalation or system crash scenarios. No provided source confirms public exploitation or inclusion in CISA KEV.
Researcher notes
The vulnerability centers on object lifetime ordering between unregister_framebuffer(), .fb_destroy, and vesafb_remove(). Validate by code review or vendor backport mapping rather than assuming version strings alone. The provided evidence names stable commits but not distro package identifiers.
Mitigation direction
Review Linux vendor advisories for CVE-2022-49419 and apply the recommended kernel update.
Confirm the running kernel includes one of the referenced stable fixes or equivalent backport.
Prioritize shared, multi-user, workstation, and server systems allowing local shell access.
If updates are delayed, reduce local untrusted user access where operationally possible.
Validation and detection
Inventory Linux kernel versions across managed assets.
Check whether vendor kernel packages include the referenced vesafb fix.
Identify systems using or enabling vesafb/fbdev functionality.
Document exceptions where kernels are custom-built or vendor backport status is unclear.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · low confidence lookup
CWE-416: 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.
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.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-416 · source CWE mapping
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.