CVE-2026-99479
fbdev: atmel_lcdfb: Prevent FIFO work after removal
What happened?
In the Linux kernel, the following vulnerability has been resolved:
fbdev: atmel_lcdfb: Prevent FIFO work after removal
The LCD controller IRQ schedules sinfo->task to recover from a FIFO underflow. Probe currently requests the IRQ before initializing the work, so an early interrupt can schedule an uninitialized work item.
The probe error path and remove path cancel the work before freeing the IRQ. A FIFO-underflow interrupt can schedule the work again after that cancellation. framebuffer_release() may then free sinfo while the work is still pending.
KASAN reported a use-after-free in atmel_lcdfb_task() when an underflow interrupt occurred during removal. With the IRQ freed before the work was cancelled, the same test completed without a kernel diagnostic.
Initialize the work before requesting the IRQ. In both cleanup paths, free the IRQ before cancelling the work so that it cannot be scheduled again after cancellation.
Affected software and versions
| Software | Version information | Fixed version |
|---|---|---|
| LinuxLinux | affected: d22579b837358cbef12ccca5adaf7e93ae09ab7a to < 0c782a29f66eab8f2f9ce2b4325cfb5b9f01f8ff; affected: d22579b837358cbef12ccca5adaf7e93ae09ab7a to < 3b0be34d9d1e7add0c9b99b0b4b969ca56d81066; affected: d22579b837358cbef12ccca5adaf7e93ae09ab7a to < f099d5adad31609a6de64aea12a8609734570b00; affected: d22579b837358cbef12ccca5adaf7e93ae09ab7a to < 20b3b97cf89cb381bf07516090d99399cc9b91fd | See vendor advisory |
| LinuxLinux | affected: 2.6.27; unaffected: 0 to < 2.6.27; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.61 to ≤ 6.18.*; unaffected: 7.3.2 to ≤ 7.3.*; unaffected: 7.4-rc1 to ≤ * | See vendor advisory |
Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.
Is it being exploited?
This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.
How to respond
- Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
- Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
- Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.
Sources and remediation references
- https://www.cve.org/CVERecord?id=CVE-2026-99479
- https://git.kernel.org/stable/c/0c782a29f66eab8f2f9ce2b4325cfb5b9f01f8ff
- https://git.kernel.org/stable/c/3b0be34d9d1e7add0c9b99b0b4b969ca56d81066
- https://git.kernel.org/stable/c/f099d5adad31609a6de64aea12a8609734570b00
- https://git.kernel.org/stable/c/20b3b97cf89cb381bf07516090d99399cc9b91fd