CVE-2025-40323
fbcon: Set fb_display[i]->mode to NULL when the mode is released
Reported by linux · Published December 8, 2025
In the Linux kernel, the following vulnerability has been resolved: fbcon: Set fb_display[i]->mode to NULL when the mode is released Recently, we discovered the following issue through syzkaller: BUG: KASAN: slab-use-after-free in fb_mode_is_equal+0x285/0x2f0 Read of size 4 at addr ff11000001b3c69c by task syz.xxx ... Call Trace: <TASK> dump_stack_lvl+0xab/0xe0 print_address_description.constprop.0+0x2c/0x390 print_report+0xb9/0x280 kasan_report+0xb8/0xf0 fb_mode_is_equal+0x285/0x2f0 fbcon_mode_deleted+0x129/0x180 fb_set_var+0xe7f/0x11d0 do_fb_ioctl+0x6a0/0x750 fb_ioctl+0xe0/0x140 __x64_sys_ioctl+0x193/0x210 do_syscall_64+0x5f/0x9c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e Based on experimentation and analysis, during framebuffer unregistration, only the memory of fb_info->modelist is freed, without setting the corresponding fb_display[i]->mode to NULL for the freed modes. This leads to UAF issues during subsequent accesses. Here's an example of reproduction steps: 1. With /dev/fb0 already registered in the system, load a kernel module to register a new device /dev/fb1; 2. Set fb1's mode to the global fb_display[] array (via FBIOPUT_CON2FBMAP); 3. Switch console from fb to VGA (to allow normal rmmod of the ko); 4. Unload the kernel module, at this point fb1's modelist is freed, leaving a wild pointer in fb_display[]; 5. Trigger the bug via system calls through fb0 attempting to delete a mode from fb0. Add a check in do_unregister_framebuffer(): if the mode to be freed exists in fb_display[], set the corresponding mode pointer to NULL.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| kernel-debug-modules-extra | errata.rockylinux.org | 6.12.0-211.60.1.el10, 4.18.0-553.169.1.el8 |
| kernel-debug-core | errata.rockylinux.org | 6.12.0-211.60.1.el10, 5.14.0-687.52.1.el9, 4.18.0-553.169.1.el8 |
| kernel-rt-modules-extra | errata.rockylinux.org | 5.14.0-687.52.1.el9 |
| python3-perf-debuginfo | errata.rockylinux.org | 6.12.0-211.60.1.el10, 5.14.0-687.52.1.el9 |
| libperf-debuginfo | errata.rockylinux.org | 5.14.0-687.52.1.el9 |
| kernel-devel | errata.rockylinux.org | 6.12.0-211.60.1.el10, 5.14.0-687.52.1.el9 |
| python3-perf | errata.rockylinux.org | 6.12.0-211.60.1.el10, 5.14.0-687.52.1.el9, 4.18.0-553.169.1.el8 |
| kernel-core | errata.rockylinux.org | 6.12.0-211.60.1.el10, 5.14.0-687.52.1.el9 |
| kernel | errata.rockylinux.org | 6.12.0-211.60.1.el10, 5.14.0-687.52.1.el9 |
| libperf | errata.rockylinux.org | 5.14.0-687.52.1.el9 |
| kernel-debug | errata.rockylinux.org | 6.12.0-211.60.1.el10, 5.14.0-687.52.1.el9 |
| kernel-64k-debug-modules-extra | errata.rockylinux.org | 5.14.0-687.52.1.el9 |
48 more packages have a fixed version. See every fix in Lookup.
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2, 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 |
| Linux | Linux | 2.6.12, 0, 5.15.203 |
| amazon:2023 | bpftool | 0 |
| amazon:2023 | kernel6.12-libbpf-static | 0 |
| amazon:2023 | perf | 0 |
| amazon:2023 | kernel6.12-modules-extra | 0 |
| amazon:2023 | kernel6.12-tools | 0 |
| amazon:2023 | kernel6.12-headers | 0 |
| amazon:2023 | kernel6.12-modules-extra-common | 0 |
| amazon:2023 | kernel6.12-tools-devel | 0 |
| amazon:2023 | kernel-tools | 0 |
| amazon:2023 | kernel-tools-devel | 0 |
| amazon:2023 | kernel-libbpf-devel | 0 |
| amazon:2023 | kernel-livepatch-6.12.58-82.121 | 0 |
| amazon:2023 | kernel6.12 | 0 |
| amazon:2023 | python3-perf | 0 |
| amazon:2023 | kernel-modules-extra-common | 0 |
| amazon:2023 | kernel | 0 |
| amazon:2023 | kernel-livepatch-6.1.159-181.297 | 0 |
| amazon:2023 | kernel6.12-devel | 0 |
…and 12 more
Timeline
- Dec 7, 2025 CVE Published
- Dec 8, 2025 EPSS Score (30 in total, the first dated here)
- Mar 29, 2026 Distribution Patch (170 in total, the first dated here)
- Mar 29, 2026 Security Advisory (204 in total, the first dated here)
- Jun 8, 2026 Coalition ESS Score
- Jul 30, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2025-40323
vulnetix vdb fixes CVE-2025-40323
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-40323/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart