fbdev: omap2: fix use-after-free in omapfb_mmap
Affects the Linux kernel omapfb (OMAP2 framebuffer) driver from 2.6.36 onward. Fixed releases are 6.6.160, 6.12.114, 6.18.57 and 7.1.3, depending on branch.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 6.6.160, 6.12.114, 6.18.57, 7.1.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In the Linux kernel, the following vulnerability has been resolved: fbdev: omap2: fix use-after-free in omapfb_mmap omapfb_mmap() has a race condition with OMAPFB_SETUP_PLANE ioctl that can lead to use-after-free: The fb_mmap() entry point holds mm_lock but not lock (fb_info->lock), while ioctl handlers like OMAPFB_SETUP_PLANE hold lock but not mm_lock. This allows concurrent execution. In omapfb_mmap(): 1. rg = omapfb_get_mem_region(ofbi->region); // Get old region ref 2. start = omapfb_get_region_paddr(ofbi); // Read from NEW region 3. len = fix->smem_len; // Read from NEW region 4. vm_iomap_memory(vma, start, len); // Map NEW region memory 5. atomic_inc(&rg->map_count); // Increment OLD region! Concurrently, OMAPFB_SETUP_PLANE can: • Reassign ofbi->region = new_rg • Update fix->smem_len • OMAPFB_SETUP_MEM then checks NEW region's map_count (0!) and frees it This leaves userspace with a mapping to freed physical memory. The fix is to read all required values (start, len) from the same region reference (rg) that will have its map_count incremented, preventing the region from being freed while still mapped.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
2.6.36
- KernelLinux
From 2.6.36 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.57; From 6.19.0 · fixed in 7.1.3
References 6
git.kernel.org
Questions about CVE-2026-53401
What does this mean?
A concurrent OMAPFB_SETUP_PLANE ioctl can change the memory region while omapfb_mmap() is running. This leaves userspace holding a mapping to freed physical memory, which is a use-after-free condition.Source: git.kernel.org
Am I affected, and how do I check?
The affected kernel ranges are 2.6.36 up to 6.6.160, 6.7.0 up to 6.12.114, 6.13.0 up to 6.18.57, and 6.19.0 up to 7.1.3. A reader can check the running kernel with uname -r and compare it against these ranges, noting that the issue involves the OMAP framebuffer driver.Source: git.kernel.org
What should I do about it?
Move to the fixed release for the kernel branch in use: 6.6.160, 6.12.114, 6.18.57, or 7.1.3.Source: git.kernel.org
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data