CVE-2023-54308

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-12-30. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2023-60496 (ENISA EUVD) · GHSA-3j26-wpvv-9xc2 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ALSA: ymfpci: Create card with device-managed snd_devm_card_new()

snd_card_ymfpci_remove() was removed in commit c6e6bb5eab74 ("ALSA: ymfpci: Allocate resources with device-managed APIs"), but the call to snd_card_new() was not replaced with snd_devm_card_new().

Since there was no longer a call to snd_card_free, unloading the module would eventually result in Oops:

[697561.532887] BUG: unable to handle page fault for address: ffffffffc0924480 [697561.532893] #PF: supervisor read access in kernel mode [697561.532896] #PF: error_code(0x0000) - not-present page [697561.532899] PGD ae1e15067 P4D ae1e15067 PUD ae1e17067 PMD 11a8f5067 PTE 0 [697561.532905] Oops: 0000 [#1] PREEMPT SMP NOPTI [697561.532909] CPU: 21 PID: 5080 Comm: wireplumber Tainted: G W OE 6.2.7 #1 [697561.532914] Hardware name: System manufacturer System Product Name/TUF GAMING X570-PLUS, BIOS 4408 10/28/2022 [697561.532916] RIP: 0010:try_module_get.part.0+0x1a/0xe0 [697561.532924] Code: 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 49 89 fc bf 01 00 00 00 e8 56 3c f8 ff <41> 83 3c 24 02 0f 84 96 00 00 00 41 8b 84 24 30 03 00 00 85 c0 0f [697561.532927] RSP: 0018:ffffbe9b858c3bd8 EFLAGS: 00010246 [697561.532930] RAX: ffff9815d14f1900 RBX: ffff9815c14e6000 RCX: 0000000000000000 [697561.532933] RDX: 0000000000000000 RSI: ffffffffc055092c RDI: ffffffffb3778c1a [697561.532935] RBP: ffffbe9b858c3be8 R08: 0000000000000040 R09: ffff981a1a741380 [697561.532937] R10: ffffbe9b858c3c80 R11: 00000009d56533a6 R12: ffffffffc0924480 [697561.532939] R13: ffff9823439d8500 R14: 0000000000000025 R15: ffff9815cd109f80 [697561.532942] FS: 00007f13084f1f80(0000) GS:ffff9824aef40000(0000) knlGS:0000000000000000 [697561.532945] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [697561.532947] CR2: ffffffffc0924480 CR3: 0000000145344000 CR4: 0000000000350ee0 [697561.532949] Call Trace: [697561.532951] [697561.532955] try_module_get+0x13/0x30 [697561.532960] snd_ctl_open+0x61/0x1c0 [snd] [697561.532976] snd_open+0xb4/0x1e0 [snd] [697561.532989] chrdev_open+0xc7/0x240 [697561.532995] ? fsnotify_perm.part.0+0x6e/0x160 [697561.533000] ? __pfx_chrdev_open+0x10/0x10 [697561.533005] do_dentry_open+0x169/0x440 [697561.533009] vfs_open+0x2d/0x40 [697561.533012] path_openat+0xa9d/0x10d0 [697561.533017] ? debug_smp_processor_id+0x17/0x20 [697561.533022] ? trigger_load_balance+0x65/0x370 [697561.533026] do_filp_open+0xb2/0x160 [697561.533032] ? _raw_spin_unlock+0x19/0x40 [697561.533036] ? alloc_fd+0xa9/0x190 [697561.533040] do_sys_openat2+0x9f/0x160 [697561.533044] __x64_sys_openat+0x55/0x90 [697561.533048] do_syscall_64+0x3b/0x90 [697561.533052] entry_SYSCALL_64_after_hwframe+0x72/0xdc [697561.533056] RIP: 0033:0x7f1308a40db4 [697561.533059] Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 46 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 78 68 f8 ff 8b 44 [697561.533062] RSP: 002b:00007ffcce664450 EFLAGS: 00000293 ORIG_RAX: 0000000000000101 [697561.533066] RAX: ffffffffffffffda RBX: 0000000000000003 RCX: 00007f1308a40db4 [697561.533068] RDX: 0000000000080000 RSI: 00007ffcce664690 RDI: 00000000ffffff9c [697561.533070] RBP: 00007ffcce664690 R08: 0000000000000000 R09: 0000000000000012 [697561.533072] R10: 0000000000000000 R11: 0000000000000293 R12: 0000000000080000 [697561.533074] R13: 00007f13054b069b R14: 0000565209f83200 R15: 0000000000000000 [697561.533078]

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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
4th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-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-29). 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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 Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

December 30, 2025

Last Modified

October 15, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
Patch available.
Web page

ALSA: ymfpci: Create card with device-managed snd_devm_card_new() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f33fc1576757741479452255132d6e3aaf558ffe
Web page

ALSA: ymfpci: Create card with device-managed snd_devm_card_new() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/db7d7782677ff998c06997903d5400a0ba91cebb
Web page

ALSA: ymfpci: Create card with device-managed snd_devm_card_new() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95642872c466030240199ba796a40771c493ed0c
Web page

ALSA: ymfpci: Create card with device-managed snd_devm_card_new() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/255a81a89501df77379b51a81c7a2e8e7c359bc6

Vendor Advisories for CVE-2023-54308(3)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:4.18.0-513.5.1.el8_92023-11-14redhat
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 5.15.106 (fixes >=5.15.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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.25-1: fixed in 6.1.25-1
—

Data Freshness Timeline

(refreshed 10× in last 7d / 46× 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 94 of 246 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. 6 repeat rows among the latest 100 are merged into the row they repeat. The 152 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2023-54308?
CVE-2023-54308 is a high-severity vulnerability; its CVE record was published on December 30, 2025. In the Linux kernel, the following vulnerability has been resolved: ALSA: ymfpci: Create card with device-managed snd_devm_card_new() snd_card_ymfpci_remove() was removed in commit c6e6bb5eab74 ("ALSA: ymfpci: Allocate resources with device-managed APIs"), but the call to snd_card_new() was not…
When was the CVE record for CVE-2023-54308 published?
The CVE record for CVE-2023-54308 was published on December 30, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2023-54308 actively exploited?
CVE-2023-54308 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-54308?
CVE-2023-54308 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2023-54308?
A fix for CVE-2023-54308 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-54308 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-2023-54308

Explore →

Is Your Infrastructure Affected by CVE-2023-54308?

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

Book a Demo →Browse All CVEs