CVE-2025-21821

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory (severity: MODERATE) published 2025-02-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-5985 (ENISA EUVD) · GHSA-2jj4-33hw-m7m9 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-20). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

February 27, 2025

Last Modified

November 3, 2025

Vendor Advisories for CVE-2025-21821(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(10)

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.128-1~deb11u1 (6 versions)
  • every version up to 6.1.129-1~deb11u1: fixed in 6.1.129-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (35 versions)
  • every version up to 6.1.129-1: fixed in 6.1.129-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.16-1: fixed in 6.12.16-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.16-1: fixed in 6.12.16-1
—

Additional Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 8× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 219 rows on record for this CVE, as 97 entries (3 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 119 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-11-20 22:49 UTCEchelonGraph re-scored
  3. 2026-11-20 22:49 UTCVendor advisory
  4. 2026-11-20 22:49 UTCGHSA enrichmentGHSA-2jj4-33hw-m7m9 · GitHub severity MODERATE · GitHub CVSS 5.5
  5. 2026-11-20 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-11-19 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  7. 2026-11-18 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  8. 2026-11-17 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-11-16 16:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  10. 2026-11-15 16:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-11-14 16:37 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  13. 2026-11-11 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  14. 2026-11-10 16:40 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-11-09 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-11-08 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  17. 2026-11-07 20:29 UTCGHSA enrichmentGHSA-2jj4-33hw-m7m9 · GitHub severity MODERATE · GitHub CVSS 5.5
  18. 2026-11-07 20:29 UTCEchelonGraph re-scored
  19. 2026-11-07 16:36 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-11-06 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  21. 2026-11-05 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-11-04 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-11-03 16:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-11-02 16:42 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-11-01 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 72 more
  1. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  3. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  4. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  6. 2026-10-25 16:43 UTCEchelonGraph re-scored
  7. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  8. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-24 01:14 UTCEchelonGraph re-scored
  10. 2026-10-24 01:14 UTCVendor advisory
  11. 2026-10-24 01:14 UTCGHSA enrichmentGHSA-2jj4-33hw-m7m9 · GitHub CVSS 5.5
  12. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  13. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-19 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-18 05:46 UTCEchelonGraph re-scored
  18. 2026-10-17 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-10-12 17:19 UTCEchelonGraph re-scored
  24. 2026-10-12 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-11 20:51 UTCEchelonGraph re-scored
  26. 2026-10-11 19:01 UTCEchelonGraph re-scored
  27. 2026-10-11 15:41 UTCEchelonGraph re-scored
  28. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  29. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  30. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  31. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  32. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  34. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  35. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  36. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  37. 2026-10-02 21:40 UTCOSV refresh
  38. 2026-10-02 16:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  40. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  42. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  43. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  44. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  45. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  46. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  47. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  48. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  49. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  50. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  51. 2026-09-15 03:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  52. 2026-09-13 19:09 UTCOSV refresh
  53. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  54. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  55. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  56. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  57. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  58. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  59. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  60. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  61. 2026-09-05 15:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  62. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  63. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  64. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  65. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  66. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  67. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  68. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  69. 2026-08-25 20:39 UTCOSV refresh
  70. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  71. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  72. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 8th percentile

Frequently asked(5)

What is CVE-2025-21821?
CVE-2025-21821 is a medium-severity vulnerability; its CVE record was published on February 27, 2025. 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…
When was the CVE record for CVE-2025-21821 published?
The CVE record for CVE-2025-21821 was published on February 27, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 3, 2025; the record at its source may have been updated since.
Is CVE-2025-21821 actively exploited?
CVE-2025-21821 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-21821?
CVE-2025-21821 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-21821?
A fix for CVE-2025-21821 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-21821 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-21821

Explore →

Is Your Infrastructure Affected by CVE-2025-21821?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.