CVE-2023-53427

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-18. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
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:

cifs: Fix warning and UAF when destroy the MR list

If the MR allocate failed, the MR recovery work not initialized and list not cleared. Then will be warning and UAF when release the MR:

WARNING: CPU: 4 PID: 824 at kernel/workqueue.c:3066 __flush_work.isra.0+0xf7/0x110 CPU: 4 PID: 824 Comm: mount.cifs Not tainted 6.1.0-rc5+ #82 RIP: 0010:__flush_work.isra.0+0xf7/0x110 Call Trace: __cancel_work_timer+0x2ba/0x2e0 smbd_destroy+0x4e1/0x990 _smbd_get_connection+0x1cbd/0x2110 smbd_get_connection+0x21/0x40 cifs_get_tcp_session+0x8ef/0xda0 mount_get_conns+0x60/0x750 cifs_mount+0x103/0xd00 cifs_smb3_do_mount+0x1dd/0xcb0 smb3_get_tree+0x1d5/0x300 vfs_get_tree+0x41/0xf0 path_mount+0x9b3/0xdd0 __x64_sys_mount+0x190/0x1d0 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0

BUG: KASAN: use-after-free in smbd_destroy+0x4fc/0x990 Read of size 8 at addr ffff88810b156a08 by task mount.cifs/824 CPU: 4 PID: 824 Comm: mount.cifs Tainted: G W 6.1.0-rc5+ #82 Call Trace: dump_stack_lvl+0x34/0x44 print_report+0x171/0x472 kasan_report+0xad/0x130 smbd_destroy+0x4fc/0x990 _smbd_get_connection+0x1cbd/0x2110 smbd_get_connection+0x21/0x40 cifs_get_tcp_session+0x8ef/0xda0 mount_get_conns+0x60/0x750 cifs_mount+0x103/0xd00 cifs_smb3_do_mount+0x1dd/0xcb0 smb3_get_tree+0x1d5/0x300 vfs_get_tree+0x41/0xf0 path_mount+0x9b3/0xdd0 __x64_sys_mount+0x190/0x1d0 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0

Allocated by task 824: kasan_save_stack+0x1e/0x40 kasan_set_track+0x21/0x30 __kasan_kmalloc+0x7a/0x90 _smbd_get_connection+0x1b6f/0x2110 smbd_get_connection+0x21/0x40 cifs_get_tcp_session+0x8ef/0xda0 mount_get_conns+0x60/0x750 cifs_mount+0x103/0xd00 cifs_smb3_do_mount+0x1dd/0xcb0 smb3_get_tree+0x1d5/0x300 vfs_get_tree+0x41/0xf0 path_mount+0x9b3/0xdd0 __x64_sys_mount+0x190/0x1d0 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0

Freed by task 824: kasan_save_stack+0x1e/0x40 kasan_set_track+0x21/0x30 kasan_save_free_info+0x2a/0x40 ____kasan_slab_free+0x143/0x1b0 __kmem_cache_free+0xc8/0x330 _smbd_get_connection+0x1c6a/0x2110 smbd_get_connection+0x21/0x40 cifs_get_tcp_session+0x8ef/0xda0 mount_get_conns+0x60/0x750 cifs_mount+0x103/0xd00 cifs_smb3_do_mount+0x1dd/0xcb0 smb3_get_tree+0x1d5/0x300 vfs_get_tree+0x41/0xf0 path_mount+0x9b3/0xdd0 __x64_sys_mount+0x190/0x1d0 do_syscall_64+0x35/0x80 entry_SYSCALL_64_after_hwframe+0x46/0xb0

Let's initialize the MR recovery work before MR allocate to prevent the warning, remove the MRs from the list to prevent the UAF.

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 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 (value × EchelonGraph’s weight)
Severity78% × 45%
The EG Score, 7.8 of 10.
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
3rd
KEV
Not listed

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.

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

September 18, 2025

Last Modified

January 14, 2026

References (7)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 4.19.276 (fixes >=4.16.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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (25 versions)
  • every version up to 5.10.178-1: fixed in 5.10.178-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.1.20-1: fixed in 6.1.20-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 26× 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 86 of 160 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. 14 repeat rows among the latest 100 are merged into the row they repeat. The 74 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2023-53427?
CVE-2023-53427 is a high-severity vulnerability; its CVE record was published on September 18, 2025. In the Linux kernel, the following vulnerability has been resolved: cifs: Fix warning and UAF when destroy the MR list If the MR allocate failed, the MR recovery work not initialized and list not cleared. Then will be warning and UAF when release the MR: WARNING: CPU: 4 PID: 824 at…
When was the CVE record for CVE-2023-53427 published?
The CVE record for CVE-2023-53427 was published on September 18, 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 14, 2026; the record at its source may have been updated since.
Is CVE-2023-53427 actively exploited?
CVE-2023-53427 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53427?
CVE-2023-53427 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-53427?
A fix for CVE-2023-53427 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-53427

Explore →

Is Your Infrastructure Affected by CVE-2023-53427?

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

Book a Demo →Browse All CVEs