Answer in brief
CVE-2024-49924 records a Unknown severity vulnerability in fbdev: pxafb: Fix possible use after free in pxafb_task(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2024-49924 records a Unknown severity vulnerability in fbdev: pxafb: Fix possible use after free in pxafb_task(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9f17f2874834f4cdbe48cc05676d8f7558793204 <e657fa2df4429f3805a9b3e47fb1a4a1b02a72bd || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <6d0a07f68b66269e167def6c0b90a219cd3e7473 || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <e6897e299f57b103e999e62010b88e363b3eebae || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <4cda484e584be34d55ee17436ebf7ad11922b97a || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <3c0d416eb4bef705f699213cee94bf54b6acdacd || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <fdda354f60a576d52dcf90351254714681df4370 || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <aaadc0cb05c999ccd8898a03298b7e5c31509b08 || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <a3a855764dbacbdb1cc51e15dc588f2d21c93e0e || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <4a6921095eb04a900e0000da83d9475eb958e61e | e657fa2df4429f3805a9b3e47fb1a4a1b02a72bd, 6d0a07f68b66269e167def6c0b90a219cd3e7473, e6897e299f57b103e999e62010b88e363b3eebae, 4cda484e584be34d55ee17436ebf7ad11922b97a, 3c0d416eb4bef705f699213cee94bf54b6acdacd, fdda354f60a576d52dcf90351254714681df4370, aaadc0cb05c999ccd8898a03298b7e5c31509b08, a3a855764dbacbdb1cc51e15dc588f2d21c93e0e, 4a6921095eb04a900e0000da83d9475eb958e61e |
| Linux/Linuxgeneric | 2.6.27 | Not reported |
Published upstream
Oct 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9f17f2874834f4cdbe48cc05676d8f7558793204 <e657fa2df4429f3805a9b3e47fb1a4a1b02a72bd || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <6d0a07f68b66269e167def6c0b90a219cd3e7473 || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <e6897e299f57b103e999e62010b88e363b3eebae || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <4cda484e584be34d55ee17436ebf7ad11922b97a || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <3c0d416eb4bef705f699213cee94bf54b6acdacd || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <fdda354f60a576d52dcf90351254714681df4370 || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <aaadc0cb05c999ccd8898a03298b7e5c31509b08 || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <a3a855764dbacbdb1cc51e15dc588f2d21c93e0e || >=9f17f2874834f4cdbe48cc05676d8f7558793204 <4a6921095eb04a900e0000da83d9475eb958e61e | e657fa2df4429f3805a9b3e47fb1a4a1b02a72bd, 6d0a07f68b66269e167def6c0b90a219cd3e7473, e6897e299f57b103e999e62010b88e363b3eebae, 4cda484e584be34d55ee17436ebf7ad11922b97a, 3c0d416eb4bef705f699213cee94bf54b6acdacd, fdda354f60a576d52dcf90351254714681df4370, aaadc0cb05c999ccd8898a03298b7e5c31509b08, a3a855764dbacbdb1cc51e15dc588f2d21c93e0e, 4a6921095eb04a900e0000da83d9475eb958e61e |
| Linux/Linuxgeneric | 2.6.27 | Not reported |
Published upstream
Oct 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.