CVE-2023-53497

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 published 2025-10-01. 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-32771 (ENISA EUVD) · GHSA-9pg5-vgmp-j2j8 (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:

media: vsp1: Replace vb2_is_streaming() with vb2_start_streaming_called()

The vsp1 driver uses the vb2_is_streaming() function in its .buf_queue() handler to check if the .start_streaming() operation has been called, and decide whether to just add the buffer to an internal queue, or also trigger a hardware run. vb2_is_streaming() relies on the vb2_queue structure's streaming field, which used to be set only after calling the .start_streaming() operation.

Commit a10b21532574 ("media: vb2: add (un)prepare_streaming queue ops") changed this, setting the .streaming field in vb2_core_streamon() before enqueuing buffers to the driver and calling .start_streaming(). This broke the vsp1 driver which now believes that .start_streaming() has been called when it hasn't, leading to a crash:

[ 881.058705] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000020 [ 881.067495] Mem abort info: [ 881.070290] ESR = 0x0000000096000006 [ 881.074042] EC = 0x25: DABT (current EL), IL = 32 bits [ 881.079358] SET = 0, FnV = 0 [ 881.082414] EA = 0, S1PTW = 0 [ 881.085558] FSC = 0x06: level 2 translation fault [ 881.090439] Data abort info: [ 881.093320] ISV = 0, ISS = 0x00000006 [ 881.097157] CM = 0, WnR = 0 [ 881.100126] user pgtable: 4k pages, 48-bit VAs, pgdp=000000004fa51000 [ 881.106573] [0000000000000020] pgd=080000004f36e003, p4d=080000004f36e003, pud=080000004f7ec003, pmd=0000000000000000 [ 881.117217] Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP [ 881.123494] Modules linked in: rcar_fdp1 v4l2_mem2mem [ 881.128572] CPU: 0 PID: 1271 Comm: yavta Tainted: G B 6.2.0-rc1-00023-g6c94e2e99343 #556 [ 881.138061] Hardware name: Renesas Salvator-X 2nd version board based on r8a77965 (DT) [ 881.145981] pstate: 400000c5 (nZcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 881.152951] pc : vsp1_dl_list_add_body+0xa8/0xe0 [ 881.157580] lr : vsp1_dl_list_add_body+0x34/0xe0 [ 881.162206] sp : ffff80000c267710 [ 881.165522] x29: ffff80000c267710 x28: ffff000010938ae8 x27: ffff000013a8dd98 [ 881.172683] x26: ffff000010938098 x25: ffff000013a8dc00 x24: ffff000010ed6ba8 [ 881.179841] x23: ffff00000faa4000 x22: 0000000000000000 x21: 0000000000000020 [ 881.186998] x20: ffff00000faa4000 x19: 0000000000000000 x18: 0000000000000000 [ 881.194154] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000000 [ 881.201309] x14: 0000000000000000 x13: 746e696174206c65 x12: ffff70000157043d [ 881.208465] x11: 1ffff0000157043c x10: ffff70000157043c x9 : dfff800000000000 [ 881.215622] x8 : ffff80000ab821e7 x7 : 00008ffffea8fbc4 x6 : 0000000000000001 [ 881.222779] x5 : ffff80000ab821e0 x4 : ffff70000157043d x3 : 0000000000000020 [ 881.229936] x2 : 0000000000000020 x1 : ffff00000e4f6400 x0 : 0000000000000000 [ 881.237092] Call trace: [ 881.239542] vsp1_dl_list_add_body+0xa8/0xe0 [ 881.243822] vsp1_video_pipeline_run+0x270/0x2a0 [ 881.248449] vsp1_video_buffer_queue+0x1c0/0x1d0 [ 881.253076] __enqueue_in_driver+0xbc/0x260 [ 881.257269] vb2_start_streaming+0x48/0x200 [ 881.261461] vb2_core_streamon+0x13c/0x280 [ 881.265565] vb2_streamon+0x3c/0x90 [ 881.269064] vsp1_video_streamon+0x2fc/0x3e0 [ 881.273344] v4l_streamon+0x50/0x70 [ 881.276844] __video_do_ioctl+0x2bc/0x5d0 [ 881.280861] video_usercopy+0x2a8/0xc80 [ 881.284704] video_ioctl2+0x20/0x40 [ 881.288201] v4l2_ioctl+0xa4/0xc0 [ 881.291525] __arm64_sys_ioctl+0xe8/0x110 [ 881.295543] invoke_syscall+0x68/0x190 [ 881.299303] el0_svc_common.constprop.0+0x88/0x170 [ 881.304105] do_el0_svc+0x4c/0xf0 [ 881.307430] el0_svc+0x4c/0xa0 [ 881.310494] el0t_64_sync_handler+0xbc/0x140 [ 881.314773] el0t_64_sync+0x190/0x194 [ 881.318450] Code: d50323bf d65f03c0 91008263 f9800071 (885f7c60) [ 881.324551] ---[ end trace 0000000000000000 ]--- [ 881.329173] note: yavta[1271] exited with preempt_count 1

A different r ---truncated---

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
5th
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-10-25). 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

October 1, 2025

Last Modified

January 16, 2026

References (3)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.2.15 (fixes >=6.2.0)—osv

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 rangeFix by version rangeDependents
linux—
  • every version up to 6.3.7-1: fixed in 6.3.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.3.7-1: fixed in 6.3.7-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 34× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 92 of 183 refreshes on record for this CVE.

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. 8 repeat rows among the latest 100 are merged into the row they repeat. The 91 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-53497?
CVE-2023-53497 is a medium-severity vulnerability; its CVE record was published on October 1, 2025. In the Linux kernel, the following vulnerability has been resolved: media: vsp1: Replace vb2_is_streaming() with vb2_start_streaming_called() The vsp1 driver uses the vb2_is_streaming() function in its .buf_queue() handler to check if the .start_streaming() operation has been called, and decide…
When was the CVE record for CVE-2023-53497 published?
The CVE record for CVE-2023-53497 was published on October 1, 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 January 16, 2026; the record at its source may have been updated since.
Is CVE-2023-53497 actively exploited?
CVE-2023-53497 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53497?
CVE-2023-53497 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53497?
A fix for CVE-2023-53497 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-53497

Explore →

Is Your Infrastructure Affected by CVE-2023-53497?

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

Book a Demo →Browse All CVEs