CVE-2026-53380

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.8EG
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.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

media: rzv2h-ivc: Fix concurrent buffer list access

The list of buffers (rzv2h_ivc::buffers.queue) is protected by a spinlock (rzv2h_ivc::buffers.lock). However, in rzv2h_ivc_transfer_buffer(), which runs in a separate workqueue, the list_del() call is executed without holding the spinlock, which makes it possible for the list to be concurrently modified

Fix that by removing a buffer from the list in the lock protected section.

[assign ivc->buffers.curr in critical section as reported by Barnabas]

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 5, 2026

Advisory Details (2)

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

media: rzv2h-ivc: Fix concurrent buffer list access - kernel/git/stable/linux.git - Linux kernel stable tree

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

media: rzv2h-ivc: Fix concurrent buffer list access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/72773ff1cdfaebc593f53b1719b2c1773ecf8c43

Vendor Advisories for CVE-2026-53380(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)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (135 versions)7.0.9-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53380?
CVE-2026-53380 is a high vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: media: rzv2h-ivc: Fix concurrent buffer list access The list of buffers (rzv2h_ivc::buffers.queue) is protected by a spinlock (rzv2h_ivc::buffers.lock). However, in rzv2hivctransfer_buffer(), which runs in a separate workqueue, the…
When was CVE-2026-53380 disclosed?
CVE-2026-53380 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-53380 actively exploited?
CVE-2026-53380 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 97.6% of all scored CVEs.
What is the CVSS score of CVE-2026-53380?
CVE-2026-53380 has a CVSS v4.0 base score of 7.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53380?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53380, 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-53380

Explore →

Is Your Infrastructure Affected by CVE-2026-53380?

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

Start Free Scan →Browse All CVEs