CVE-2026-63883

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-19. the CNA's CVSS baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ

When uart_flush_buffer() runs before the DMA completion IRQ is delivered, the following race can occur (all steps serialized by uart_port_lock):

  • DMA starts: tx_remaining = N, kfifo contains N bytes
  • DMA completes in hardware; IRQ is pending but not yet delivered
  • uart_flush_buffer() acquires the port lock and calls kfifo_reset(),
making kfifo_len() = 0 while tx_remaining remains N
  • uart_flush_buffer() releases the port lock
  • DMA IRQ fires; handle_tx_dma() acquires the port lock and calls
uart_xmit_advance(uport, tx_remaining) on an empty kfifo

uart_xmit_advance() increments kfifo->out by tx_remaining. Since kfifo_reset() already set both in and out to 0, out wraps past in, causing kfifo_len() to return UART_XMIT_SIZE - tx_remaining. The next start_tx_dma() call then submits a DMA transfer of stale buffer data.

Fix this by snapshotting kfifo_len() at the start of handle_tx_dma() and skipping uart_xmit_advance() when fifo_len < tx_remaining, which indicates the kfifo was reset by a preceding flush.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity73% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Jul 21, 2026
No patch confirmed yet.
generic

serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c91ea13375f70f6271a0183445e34e83b8f4d8f7
generic

serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b1159dce10b38eb795e4c96cdc4d34b83cec81c5
generic

serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/654f45a8569f3cd6ff20bd724a18e0cce65893ba
generic

serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/452d6fa37ae9b021f4f6d397dbae077f7296f6f4
generic

serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0d2c41a8b00934ddf8a7c1b4cf72dffa1e629c46

Vendor Advisories for CVE-2026-63883(1)

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

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 30× in last 7d / 158× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 203 total refreshes for this CVE.

  1. 2026-08-30 02:59 UTCEG score recompute
  2. 2026-08-30 02:59 UTCVendor advisory
  3. 2026-08-30 02:59 UTCGHSA enrichment
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-28 01:55 UTCEG score recompute
  7. 2026-08-28 01:55 UTCVendor advisory
  8. 2026-08-28 01:55 UTCGHSA enrichment
  9. 2026-08-27 14:25 UTCEPSS rescore
  10. 2026-08-27 13:14 UTCVendor advisory
  11. 2026-08-27 13:14 UTCGHSA enrichment
  12. 2026-08-27 00:30 UTCEG score recompute
  13. 2026-08-27 00:30 UTCVendor advisory
  14. 2026-08-27 00:30 UTCGHSA enrichment
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-26 11:43 UTCVendor advisory
  17. 2026-08-26 11:43 UTCGHSA enrichment
  18. 2026-08-25 20:57 UTCEG score recompute
  19. 2026-08-25 20:57 UTCVendor advisory
  20. 2026-08-25 20:56 UTCGHSA enrichment
  21. 2026-08-25 13:49 UTCEPSS rescore
  22. 2026-08-25 07:51 UTCVendor advisory
  23. 2026-08-25 07:51 UTCGHSA enrichment
  24. 2026-08-24 19:10 UTCEG score recompute
  25. 2026-08-24 19:10 UTCVendor advisory
Show 75 more
  1. 2026-08-24 19:10 UTCGHSA enrichment
  2. 2026-08-24 05:33 UTCVendor advisory
  3. 2026-08-24 05:33 UTCGHSA enrichment
  4. 2026-08-23 16:52 UTCVendor advisory
  5. 2026-08-23 16:52 UTCGHSA enrichment
  6. 2026-08-23 04:12 UTCEG score recompute
  7. 2026-08-23 04:12 UTCVendor advisory
  8. 2026-08-23 04:12 UTCGHSA enrichment
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 15:31 UTCVendor advisory
  11. 2026-08-22 15:31 UTCGHSA enrichment
  12. 2026-08-22 02:50 UTCEG score recompute
  13. 2026-08-22 02:50 UTCVendor advisory
  14. 2026-08-22 02:50 UTCGHSA enrichment
  15. 2026-08-21 23:49 UTCEPSS rescore
  16. 2026-08-21 14:01 UTCVendor advisory
  17. 2026-08-21 14:01 UTCGHSA enrichment
  18. 2026-08-21 00:56 UTCEG score recompute
  19. 2026-08-21 00:56 UTCVendor advisory
  20. 2026-08-21 00:55 UTCGHSA enrichment
  21. 2026-08-20 22:55 UTCEPSS rescore
  22. 2026-08-20 12:14 UTCVendor advisory
  23. 2026-08-20 12:14 UTCGHSA enrichment
  24. 2026-08-19 23:11 UTCEG score recompute
  25. 2026-08-19 23:11 UTCVendor advisory
  26. 2026-08-19 23:11 UTCGHSA enrichment
  27. 2026-08-19 17:04 UTCEPSS rescore
  28. 2026-08-19 08:36 UTCVendor advisory
  29. 2026-08-19 08:35 UTCGHSA enrichment
  30. 2026-08-18 19:50 UTCEG score recompute
  31. 2026-08-18 19:50 UTCVendor advisory
  32. 2026-08-18 19:50 UTCGHSA enrichment
  33. 2026-08-18 13:48 UTCEPSS rescore
  34. 2026-08-18 05:54 UTCVendor advisory
  35. 2026-08-18 05:54 UTCGHSA enrichment
  36. 2026-08-17 17:09 UTCEG score recompute
  37. 2026-08-17 17:09 UTCVendor advisory
  38. 2026-08-17 17:09 UTCGHSA enrichment
  39. 2026-08-17 13:47 UTCEPSS rescore
  40. 2026-08-17 04:28 UTCVendor advisory
  41. 2026-08-17 04:28 UTCGHSA enrichment
  42. 2026-08-16 15:47 UTCEG score recompute
  43. 2026-08-16 15:47 UTCVendor advisory
  44. 2026-08-16 15:47 UTCGHSA enrichment
  45. 2026-08-16 14:56 UTCEPSS rescore
  46. 2026-08-16 03:06 UTCEG score recompute
  47. 2026-08-16 03:06 UTCVendor advisory
  48. 2026-08-16 03:06 UTCGHSA enrichment
  49. 2026-08-15 14:26 UTCVendor advisory
  50. 2026-08-15 14:26 UTCGHSA enrichment
  51. 2026-08-15 01:45 UTCEG score recompute
  52. 2026-08-15 01:45 UTCVendor advisory
  53. 2026-08-15 01:45 UTCGHSA enrichment
  54. 2026-08-15 01:30 UTCEPSS rescore
  55. 2026-08-14 13:05 UTCVendor advisory
  56. 2026-08-14 13:05 UTCGHSA enrichment
  57. 2026-08-14 00:24 UTCEG score recompute
  58. 2026-08-14 00:24 UTCVendor advisory
  59. 2026-08-14 00:24 UTCGHSA enrichment
  60. 2026-08-13 22:00 UTCEPSS rescore
  61. 2026-08-13 11:43 UTCGHSA enrichment
  62. 2026-08-12 23:01 UTCEG score recompute
  63. 2026-08-12 23:01 UTCVendor advisory
  64. 2026-08-12 23:01 UTCGHSA enrichment
  65. 2026-08-12 13:51 UTCEPSS rescore
  66. 2026-08-12 10:21 UTCVendor advisory
  67. 2026-08-12 10:21 UTCGHSA enrichment
  68. 2026-08-11 21:38 UTCEG score recompute
  69. 2026-08-11 21:38 UTCVendor advisory
  70. 2026-08-11 21:38 UTCGHSA enrichment
  71. 2026-08-11 08:57 UTCEG score recompute
  72. 2026-08-11 08:57 UTCVendor advisory
  73. 2026-08-11 08:57 UTCGHSA enrichment
  74. 2026-08-11 00:00 UTCEPSS rescore
  75. 2026-08-10 20:17 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-63883?
CVE-2026-63883 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: serial: qcom_geni: fix kfifo underflow when flush precedes DMA completion IRQ When uartflushbuffer() runs before the DMA completion IRQ is delivered, the following race can occur (all steps serialized by uartportlock): 1. DMA…
When was CVE-2026-63883 disclosed?
CVE-2026-63883 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63883 actively exploited?
CVE-2026-63883 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.9% of all scored CVEs.
What is the CVSS score of CVE-2026-63883?
CVE-2026-63883 has a CVSS v4.0 base score of 7.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-63883?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63883, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-63883

Explore →

Is Your Infrastructure Affected by CVE-2026-63883?

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