CVE-2023-53829

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-09. The CNA's CVSS baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week

Also known asEUVD-2023-60167 (ENISA EUVD) · GHSA-38rj-5vp6-wr6c (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:

f2fs: flush inode if atomic file is aborted

Let's flush the inode being aborted atomic operation to avoid stale dirty inode during eviction in this call stack:

f2fs_mark_inode_dirty_sync+0x22/0x40 [f2fs] f2fs_abort_atomic_write+0xc4/0xf0 [f2fs] f2fs_evict_inode+0x3f/0x690 [f2fs] ? sugov_start+0x140/0x140 evict+0xc3/0x1c0 evict_inodes+0x17b/0x210 generic_shutdown_super+0x32/0x120 kill_block_super+0x21/0x50 deactivate_locked_super+0x31/0x90 cleanup_mnt+0x100/0x160 task_work_run+0x59/0x90 do_exit+0x33b/0xa50 do_group_exit+0x2d/0x80 __x64_sys_exit_group+0x14/0x20 do_syscall_64+0x3b/0x90 entry_SYSCALL_64_after_hwframe+0x63/0xcd

This triggers f2fs_bug_on() in f2fs_evict_inode: f2fs_bug_on(sbi, is_inode_flag_set(inode, FI_DIRTY_INODE));

This fixes the syzbot report:

loop0: detected capacity change from 0 to 131072 F2FS-fs (loop0): invalid crc value F2FS-fs (loop0): Found nat_bits in checkpoint F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4 ------------[ cut here ]------------ kernel BUG at fs/f2fs/inode.c:869! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 0 PID: 5014 Comm: syz-executor220 Not tainted 6.4.0-syzkaller-11479-g6cd06ab12d1a #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 RIP: 0010:f2fs_evict_inode+0x172d/0x1e00 fs/f2fs/inode.c:869 Code: ff df 48 c1 ea 03 80 3c 02 00 0f 85 6a 06 00 00 8b 75 40 ba 01 00 00 00 4c 89 e7 e8 6d ce 06 00 e9 aa fc ff ff e8 63 22 e2 fd <0f> 0b e8 5c 22 e2 fd 48 c7 c0 a8 3a 18 8d 48 ba 00 00 00 00 00 fc RSP: 0018:ffffc90003a6fa00 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000000000001 RCX: 0000000000000000 RDX: ffff8880273b8000 RSI: ffffffff83a2bd0d RDI: 0000000000000007 RBP: ffff888077db91b0 R08: 0000000000000007 R09: 0000000000000000 R10: 0000000000000001 R11: 0000000000000001 R12: ffff888029a3c000 R13: ffff888077db9660 R14: ffff888029a3c0b8 R15: ffff888077db9c50 FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f1909bb9000 CR3: 00000000276a9000 CR4: 0000000000350ef0 Call Trace: evict+0x2ed/0x6b0 fs/inode.c:665 dispose_list+0x117/0x1e0 fs/inode.c:698 evict_inodes+0x345/0x440 fs/inode.c:748 generic_shutdown_super+0xaf/0x480 fs/super.c:478 kill_block_super+0x64/0xb0 fs/super.c:1417 kill_f2fs_super+0x2af/0x3c0 fs/f2fs/super.c:4704 deactivate_locked_super+0x98/0x160 fs/super.c:330 deactivate_super+0xb1/0xd0 fs/super.c:361 cleanup_mnt+0x2ae/0x3d0 fs/namespace.c:1254 task_work_run+0x16f/0x270 kernel/task_work.c:179 exit_task_work include/linux/task_work.h:38 [inline] do_exit+0xa9a/0x29a0 kernel/exit.c:874 do_group_exit+0xd4/0x2a0 kernel/exit.c:1024 __do_sys_exit_group kernel/exit.c:1035 [inline] __se_sys_exit_group kernel/exit.c:1033 [inline] __x64_sys_exit_group+0x3e/0x50 kernel/exit.c:1033 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x7f309be71a09 Code: Unable to access opcode bytes at 0x7f309be719df. RSP: 002b:00007fff171df518 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7 RAX: ffffffffffffffda RBX: 00007f309bef7330 RCX: 00007f309be71a09 RDX: 000000000000003c RSI: 00000000000000e7 RDI: 0000000000000001 RBP: 0000000000000001 R08: ffffffffffffffc0 R09: 00007f309bef1e40 R10: 0000000000010600 R11: 0000000000000246 R12: 00007f309bef7330 R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000001 Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010:f2fs_evict_inode+0x172d/0x1e00 fs/f2fs/inode.c:869 Code: ff df 48 c1 ea 03 80 3c 02 00 0f 85 6a 06 00 00 8b 75 40 ba 01 00 00 00 4c 89 e7 e8 6d ce 06 00 e9 aa fc ff ff e8 63 22 e2 fd <0f> 0b e8 5c 22 e2 fd 48 c7 c0 a8 3a 18 8d 48 ba 00 00 00 00 00 fc RSP: 0018:ffffc90003a6fa00 EFLAGS: 00010293 RAX: 0000000000000000 RBX: 0000000000 ---truncated---

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.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
8th
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-11-02). 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

December 9, 2025

Last Modified

August 5, 2026

Advisory Details (3)

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

f2fs: flush inode if atomic file is aborted - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: flush inode if atomic file is aborted - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: flush inode if atomic file is aborted - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1c64dbe8fa3552a340bca6d7fa09468c16ed2a85

Vendor Advisories for CVE-2023-53829(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.1.54 (fixes >=3.8.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 ... 7.2~rc5-1~exp1 (498 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.55-1~bpo11+1 (10 versions)
  • every version up to 6.1.55-1: fixed in 6.1.55-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.5.6-1: fixed in 6.5.6-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.5.6-1: fixed in 6.5.6-1
—

Data Freshness Timeline

(refreshed 9× in last 7d / 39× 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 235 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 141 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2023-53829?
CVE-2023-53829 is a high-severity vulnerability; its CVE record was published on December 9, 2025. In the Linux kernel, the following vulnerability has been resolved: f2fs: flush inode if atomic file is aborted Let's flush the inode being aborted atomic operation to avoid stale dirty inode during eviction in this call stack: f2fs_mark_inode_dirty_sync+0x22/0x40 [f2fs]…
When was the CVE record for CVE-2023-53829 published?
The CVE record for CVE-2023-53829 was published on December 9, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2023-53829 actively exploited?
CVE-2023-53829 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53829?
CVE-2023-53829 has a CVSS base score of 7.8 (the CNA's own assessment, by linux; NVD's own analysis pending).
How do I remediate CVE-2023-53829?
A fix for CVE-2023-53829 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53829 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-53829

Explore →

Is Your Infrastructure Affected by CVE-2023-53829?

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

Book a Demo →Browse All CVEs