fbdev: pxafb: Fix possible use after free in pxafb_task()
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 4.19.323, 5.10.227, 5.15.168, 5.4.285, 6.1.113, 6.10.14, 6.11.3, 6.6.55
- CVEs
- CVE-2024-49924
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 16:58 UTC · Revision 1
Source evidence
fbdev: pxafb: Fix possible use after free in pxafb_task()
core-osv · Original sourcePublished 21 Oct 2024, 18:01 UTC
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.
osv:CVE-2024-49924
Kernel
Fixed versions: 4.19.323, 5.4.285, 5.10.227, 5.15.168, 6.1.113, 6.6.55, 6.10.14, 6.11.3
Complete source record
{
"id": "b4df95643d1408741b5fe9dd8dad677ddd9ad02ab0220b343568c98a48b190ee",
"url": "https://osv.dev/vulnerability/CVE-2024-49924",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "fbdev: pxafb: Fix possible use after free in pxafb_task()",
"summary": "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.",
"evidence": "osv:CVE-2024-49924",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "4.19.323",
"evidence": "/affected/1/ranges"
},
{
"value": "5.4.285",
"evidence": "/affected/1/ranges"
},
{
"value": "5.10.227",
"evidence": "/affected/1/ranges"
},
{
"value": "5.15.168",
"evidence": "/affected/1/ranges"
},
{
"value": "6.1.113",
"evidence": "/affected/1/ranges"
},
{
"value": "6.6.55",
"evidence": "/affected/1/ranges"
},
{
"value": "6.10.14",
"evidence": "/affected/1/ranges"
},
{
"value": "6.11.3",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "CVE-2024-49924",
"aliases": [
"CVE-2024-49924"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "9f17f2874834f4cdbe48cc05676d8f7558793204"
},
{
"fixed": "e657fa2df4429f3805a9b3e47fb1a4a1b02a72bd"
},
{
"fixed": "6d0a07f68b66269e167def6c0b90a219cd3e7473"
},
{
"fixed": "e6897e299f57b103e999e62010b88e363b3eebae"
},
{
"fixed": "4cda484e584be34d55ee17436ebf7ad11922b97a"
},
{
"fixed": "3c0d416eb4bef705f699213cee94bf54b6acdacd"
},
{
"fixed": "fdda354f60a576d52dcf90351254714681df4370"
},
{
"fixed": "aaadc0cb05c999ccd8898a03298b7e5c31509b08"
},
{
"fixed": "a3a855764dbacbdb1cc51e15dc588f2d21c93e0e"
},
{
"fixed": "4a6921095eb04a900e0000da83d9475eb958e61e"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-49924.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "2.6.27"
},
{
"fixed": "4.19.323"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "4.20.0"
},
{
"fixed": "5.4.285"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.5.0"
},
{
"fixed": "5.10.227"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.11.0"
},
{
"fixed": "5.15.168"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "5.16.0"
},
{
"fixed": "6.1.113"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.2.0"
},
{
"fixed": "6.6.55"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.7.0"
},
{
"fixed": "6.10.14"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.11.0"
},
{
"fixed": "6.11.3"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-49924.json"
}
}
],
"modified": "2026-10-28T02:30:38.149223941Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/3c0d416eb4bef705f699213cee94bf54b6acdacd",
"https://git.kernel.org/stable/c/4a6921095eb04a900e0000da83d9475eb958e61e",
"https://git.kernel.org/stable/c/4cda484e584be34d55ee17436ebf7ad11922b97a",
"https://git.kernel.org/stable/c/6d0a07f68b66269e167def6c0b90a219cd3e7473",
"https://git.kernel.org/stable/c/a3a855764dbacbdb1cc51e15dc588f2d21c93e0e",
"https://git.kernel.org/stable/c/aaadc0cb05c999ccd8898a03298b7e5c31509b08",
"https://git.kernel.org/stable/c/e657fa2df4429f3805a9b3e47fb1a4a1b02a72bd",
"https://git.kernel.org/stable/c/e6897e299f57b103e999e62010b88e363b3eebae",
"https://git.kernel.org/stable/c/fdda354f60a576d52dcf90351254714681df4370",
"https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/49xxx/CVE-2024-49924.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-49924",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/49xxx/CVE-2024-49924.json"
}
},
"related_cves": [
{
"value": "CVE-2024-49924",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 505023,
"published_at": "2024-10-21T18:01:49.076+00:00"
}