LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21821: fbdev: omap: use threaded IRQ for LCD DMA

In the Linux kernel, the following vulnerability has been resolved: fbdev: omap: use threaded IRQ for LCD DMA When using touchscreen and framebuffer, Nokia 770 crashes easily with: BUG: scheduling while atomic: irq/144-ads7846/82/0x00010000 Modules linked in: usb_f_ecm g_ether usb_f_rndis u_ether libcomposite configfs omap_udc ohci_omap ohci_hcd CPU: 0 UID: 0 PID: 82 Comm: irq/144-ads7846 Not tainted 6.12.7-770 #2 Hardware name: Nokia 770 Call trace: unwind_backtrace from show_stack+0x10/0x14 show_stack from dump_stack_lvl+0x54/0x5c dump_stack_lvl from __schedule_bug+0x50/0x70 __schedule_bug from __schedule+0x4d4/0x5bc __schedule from schedule+0x34/0xa0 schedule from schedule_preempt_disabled+0xc/0x10 schedule_preempt_disabled from __mutex_lock.constprop.0+0x218/0x3b4 __mutex_lock.constprop.0 from clk_prepare_lock+0x38/0xe4 clk_prepare_lock from clk_set_rate+0x18/0x154 clk_set_rate from sossi_read_data+0x4c/0x168 sossi_read_data from hwa742_read_reg+0x5c/0x8c hwa742_read_reg from send_frame_handler+0xfc/0x300 send_frame_handler from process_pending_requests+0x74/0xd0 process_pending_requests from lcd_dma_irq_handler+0x50/0x74 lcd_dma_irq_handler from __handle_irq_event_percpu+0x44/0x130 __handle_irq_event_percpu from handle_irq_event+0x28/0x68 handle_irq_event from handle_level_irq+0x9c/0x170 handle_level_irq from generic_handle_domain_irq+0x2c/0x3c generic_handle_domain_irq from omap1_handle_irq+0x40/0x8c omap1_handle_irq from generic_handle_arch_irq+0x28/0x3c generic_handle_arch_irq from call_with_stack+0x1c/0x24 call_with_stack from __irq_svc+0x94/0xa8 Exception stack(0xc5255da0 to 0xc5255de8) 5da0: 00000001 c22fc620 00000000 00000000 c08384a8 c106fc00 00000000 c240c248 5dc0: c113a600 c3f6ec30 00000001 00000000 c22fc620 c5255df0 c22fc620 c0279a94 5de0: 60000013 ffffffff __irq_svc from clk_prepare_lock+0x4c/0xe4 clk_prepare_lock from clk_get_rate+0x10/0x74 clk_get_rate from uwire_setup_transfer+0x40/0x180 uwire_setup_transfer from spi_bitbang_transfer_one+0x2c/0x9c spi_bitbang_transfer_one from spi_transfer_one_message+0x2d0/0x664 spi_transfer_one_message from __spi_pump_transfer_message+0x29c/0x498 __spi_pump_transfer_message from __spi_sync+0x1f8/0x2e8 __spi_sync from spi_sync+0x24/0x40 spi_sync from ads7846_halfd_read_state+0x5c/0x1c0 ads7846_halfd_read_state from ads7846_irq+0x58/0x348 ads7846_irq from irq_thread_fn+0x1c/0x78 irq_thread_fn from irq_thread+0x120/0x228 irq_thread from kthread+0xc8/0xe8 kthread from ret_from_fork+0x14/0x28 As a quick fix, switch to a threaded IRQ which provides a stable system.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel stability flaw in the OMAP framebuffer LCD DMA path. On affected hardware, using touchscreen and framebuffer together can crash the system. The public record does not show code execution, data theft, or active exploitation, but reliability impact may matter for embedded or operational devices.

Executive priority

Treat as low general enterprise priority, but moderate for owners of affected embedded Linux hardware where device crashes disrupt service, safety workflows, or field operations.

Technical view

The kernel report shows an interrupt handler reaching clock operations that can sleep, causing a scheduling-while-atomic BUG. The resolved change moves OMAP LCD DMA interrupt handling to a threaded IRQ. Evidence points to the fbdev OMAP path, with the Nokia 770 cited as the observed crashing platform.

Likely exposure

Likely limited to Linux systems using the OMAP framebuffer LCD DMA driver, especially embedded ARM devices with touchscreen plus framebuffer. Typical servers, desktops, and cloud workloads are unlikely to expose this path unless they use the affected OMAP display stack.

Exploitation context

No KEV listing is provided, and the source bundle does not cite active exploitation. The described trigger is local hardware and driver interaction causing a crash. Public evidence supports denial of service or instability, not remote compromise.

Researcher notes

The evidence is narrow and hardware-specific. The bundle has no CVSS, CWE, exploit report, or detailed version mapping beyond Linux affected entries and stable commits. Avoid broad claims about all Linux systems; focus validation on OMAP fbdev LCD DMA deployments.

Mitigation direction

  • Update to a vendor kernel containing the OMAP fbdev LCD DMA threaded IRQ fix.
  • Apply the relevant kernel.org stable commit for the deployed kernel branch.
  • Use Debian LTS kernel updates where applicable to Debian systems.
  • Prioritize embedded devices using OMAP framebuffer, LCD DMA, and touchscreen input.
  • If no package exists, track vendor guidance and plan a kernel maintenance update.

Validation and detection

  • Inventory devices for OMAP fbdev framebuffer and LCD DMA usage.
  • Check deployed kernel versions against vendor advisories and stable branch fixes.
  • Review crash logs for scheduling-while-atomic BUG traces in OMAP LCD DMA paths.
  • Confirm updated kernels include the threaded IRQ change for this driver.
  • Regression-test touchscreen and framebuffer operation on affected hardware after updating.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-21821 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
1ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxc73b9099da4fb5703abaa804a0377850eea66cb5, c73b9099da4fb5703abaa804a0377850eea66cb5, c73b9099da4fb5703abaa804a0377850eea66cb5, c73b9099da4fb5703abaa804a0377850eea66cb5, c73b9099da4fb5703abaa804a0377850eea66cb5unaffected
LinuxLinux5.19, 0, 6.1.129, 6.6.79, 6.12.16, 6.13.4, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.