CVE-2024-49924
Ubuntu Linux framebuffer Use After Free (UAF) Vulnerability
Description
In the Linux kernel, the following vulnerability has been resolved: fbdev: pxafb: Fix possible use after free in pxafb_task() In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which &fbi->task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the &pxafb_ops struct is capable of scheduling work. If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi->fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | pxafb_task pxafb_remove | unregister_framebuffer(info) | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info) | // free fbi->fb | set_ctrlr_state(fbi, state) | __pxafb_lcd_power(fbi, 0) | fbi->lcd_power(on, &fbi->fb.var) | //use fbi->fb Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove. Note that only root user can remove the driver at runtime.
INFO
Published Date :
Oct. 21, 2024, 6:15 p.m.
Last Modified :
Nov. 8, 2024, 4:15 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
5.9
Exploitability Score :
1.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-49924.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-49924 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-49924 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Nov. 08, 2024
Action Type Old Value New Value Added Reference kernel.org https://git.kernel.org/stable/c/e657fa2df4429f3805a9b3e47fb1a4a1b02a72bd [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/6d0a07f68b66269e167def6c0b90a219cd3e7473 [No types assigned] -
Initial Analysis by [email protected]
Oct. 25, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://git.kernel.org/stable/c/3c0d416eb4bef705f699213cee94bf54b6acdacd No Types Assigned https://git.kernel.org/stable/c/3c0d416eb4bef705f699213cee94bf54b6acdacd Patch Changed Reference Type https://git.kernel.org/stable/c/4a6921095eb04a900e0000da83d9475eb958e61e No Types Assigned https://git.kernel.org/stable/c/4a6921095eb04a900e0000da83d9475eb958e61e Patch Changed Reference Type https://git.kernel.org/stable/c/4cda484e584be34d55ee17436ebf7ad11922b97a No Types Assigned https://git.kernel.org/stable/c/4cda484e584be34d55ee17436ebf7ad11922b97a Patch Changed Reference Type https://git.kernel.org/stable/c/a3a855764dbacbdb1cc51e15dc588f2d21c93e0e No Types Assigned https://git.kernel.org/stable/c/a3a855764dbacbdb1cc51e15dc588f2d21c93e0e Patch Changed Reference Type https://git.kernel.org/stable/c/aaadc0cb05c999ccd8898a03298b7e5c31509b08 No Types Assigned https://git.kernel.org/stable/c/aaadc0cb05c999ccd8898a03298b7e5c31509b08 Patch Changed Reference Type https://git.kernel.org/stable/c/e6897e299f57b103e999e62010b88e363b3eebae No Types Assigned https://git.kernel.org/stable/c/e6897e299f57b103e999e62010b88e363b3eebae Patch Changed Reference Type https://git.kernel.org/stable/c/fdda354f60a576d52dcf90351254714681df4370 No Types Assigned https://git.kernel.org/stable/c/fdda354f60a576d52dcf90351254714681df4370 Patch Added CWE NIST CWE-416 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions up to (excluding) 5.10.227 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.11 up to (excluding) 5.15.168 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.16 up to (excluding) 6.1.113 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.2 up to (excluding) 6.6.55 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.10.14 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.11 up to (excluding) 6.11.3 -
CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Oct. 21, 2024
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: fbdev: pxafb: Fix possible use after free in pxafb_task() In the pxafb_probe function, it calls the pxafb_init_fbinfo function, after which &fbi->task is associated with pxafb_task. Moreover, within this pxafb_init_fbinfo function, the pxafb_blank function within the &pxafb_ops struct is capable of scheduling work. If we remove the module which will call pxafb_remove to make cleanup, it will call unregister_framebuffer function which can call do_unregister_framebuffer to free fbi->fb through put_fb_info(fb_info), while the work mentioned above will be used. The sequence of operations that may lead to a UAF bug is as follows: CPU0 CPU1 | pxafb_task pxafb_remove | unregister_framebuffer(info) | do_unregister_framebuffer(fb_info) | put_fb_info(fb_info) | // free fbi->fb | set_ctrlr_state(fbi, state) | __pxafb_lcd_power(fbi, 0) | fbi->lcd_power(on, &fbi->fb.var) | //use fbi->fb Fix it by ensuring that the work is canceled before proceeding with the cleanup in pxafb_remove. Note that only root user can remove the driver at runtime. Added Reference kernel.org https://git.kernel.org/stable/c/e6897e299f57b103e999e62010b88e363b3eebae [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/4cda484e584be34d55ee17436ebf7ad11922b97a [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/3c0d416eb4bef705f699213cee94bf54b6acdacd [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/fdda354f60a576d52dcf90351254714681df4370 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/aaadc0cb05c999ccd8898a03298b7e5c31509b08 [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/a3a855764dbacbdb1cc51e15dc588f2d21c93e0e [No types assigned] Added Reference kernel.org https://git.kernel.org/stable/c/4a6921095eb04a900e0000da83d9475eb958e61e [No types assigned]
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-49924 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-49924
weaknesses.