CVE-2024-53171

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 2024-12-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-51843 (ENISA EUVD) · GHSA-2gwr-frhx-j93x (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.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit

After an insertion in TNC, the tree might split and cause a node to change its znode->parent. A further deletion of other nodes in the tree (which also could free the nodes), the aforementioned node's znode->cparent could still point to a freed node. This znode->cparent may not be updated when getting nodes to commit in ubifs_tnc_start_commit(). This could then trigger a use-after-free when accessing the znode->cparent in write_index() in ubifs_tnc_end_commit().

This can be triggered by running

rm -f /etc/test-file.bin dd if=/dev/urandom of=/etc/test-file.bin bs=1M count=60 conv=fsync

in a loop, and with CONFIG_UBIFS_FS_AUTHENTICATION. KASAN then reports:

BUG: KASAN: use-after-free in ubifs_tnc_end_commit+0xa5c/0x1950 Write of size 32 at addr ffffff800a3af86c by task ubifs_bgt0_20/153

Call trace: dump_backtrace+0x0/0x340 show_stack+0x18/0x24 dump_stack_lvl+0x9c/0xbc print_address_description.constprop.0+0x74/0x2b0 kasan_report+0x1d8/0x1f0 kasan_check_range+0xf8/0x1a0 memcpy+0x84/0xf4 ubifs_tnc_end_commit+0xa5c/0x1950 do_commit+0x4e0/0x1340 ubifs_bg_thread+0x234/0x2e0 kthread+0x36c/0x410 ret_from_fork+0x10/0x20

Allocated by task 401: kasan_save_stack+0x38/0x70 __kasan_kmalloc+0x8c/0xd0 __kmalloc+0x34c/0x5bc tnc_insert+0x140/0x16a4 ubifs_tnc_add+0x370/0x52c ubifs_jnl_write_data+0x5d8/0x870 do_writepage+0x36c/0x510 ubifs_writepage+0x190/0x4dc __writepage+0x58/0x154 write_cache_pages+0x394/0x830 do_writepages+0x1f0/0x5b0 filemap_fdatawrite_wbc+0x170/0x25c file_write_and_wait_range+0x140/0x190 ubifs_fsync+0xe8/0x290 vfs_fsync_range+0xc0/0x1e4 do_fsync+0x40/0x90 __arm64_sys_fsync+0x34/0x50 invoke_syscall.constprop.0+0xa8/0x260 do_el0_svc+0xc8/0x1f0 el0_svc+0x34/0x70 el0t_64_sync_handler+0x108/0x114 el0t_64_sync+0x1a4/0x1a8

Freed by task 403: kasan_save_stack+0x38/0x70 kasan_set_track+0x28/0x40 kasan_set_free_info+0x28/0x4c __kasan_slab_free+0xd4/0x13c kfree+0xc4/0x3a0 tnc_delete+0x3f4/0xe40 ubifs_tnc_remove_range+0x368/0x73c ubifs_tnc_remove_ino+0x29c/0x2e0 ubifs_jnl_delete_inode+0x150/0x260 ubifs_evict_inode+0x1d4/0x2e4 evict+0x1c8/0x450 iput+0x2a0/0x3c4 do_unlinkat+0x2cc/0x490 __arm64_sys_unlinkat+0x90/0x100 invoke_syscall.constprop.0+0xa8/0x260 do_el0_svc+0xc8/0x1f0 el0_svc+0x34/0x70 el0t_64_sync_handler+0x108/0x114 el0t_64_sync+0x1a4/0x1a8

The offending memcpy() in ubifs_copy_hash() has a use-after-free when a node becomes root in TNC but still has a cparent to an already freed node. More specifically, consider the following TNC:

zroot / / zp1 / / zn

Inserting a new node zn_new with a key smaller then zn will trigger a split in tnc_insert() if zp1 is full:

zroot / \ / \ zp1 zp2 / \ / \ zn_new zn

zn->parent has now been moved to zp2, *but* zn->cparent still points to zp1.

Now, consider a removal of all the nodes _except_ zn. Just when tnc_delete() is about to delete zroot and zp2:

zroot \ \ zp2 \ \ zn

zroot and zp2 get freed and the tree collapses:

zn

zn now becomes the new zroot.

get_znodes_to_commit() will now only find zn, the new zroot, and write_index() will check its znode->cparent that wrongly points to the already freed zp1. ubifs_copy_hash() thus gets wrongly called with znode->cparent->zbranch[znode->iip].hash that triggers the use-after-free!

Fix this by explicitly setting znode->cparent to NULL in get_znodes_to_commit() for the root node. The search for the dirty nodes ---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.3% × 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.3%
EPSS %ILE
25th
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.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 27, 2024

Last Modified

August 5, 2026

Advisory Details (8)

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

ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4617fb8fc15effe8eda4dd898d4e33eb537a7140
Web page

ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2497479aecebe869d23a0064e0fd1a03e34f0e2a
Web page

ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/398a91599d263e41c5f95a2fd4ebdb6280b5c6c3
Web page

ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01d3a2293d7e4edfff96618c15727db7e51f11b6
Web page

ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74981f7577d183acad1cd58f74c10d263711a215
Web page

ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4d9807048b851d7a58d5bd089c16254af896e4df
Web page

ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d8b3f5f4cbfbf6cb0ea4a4d5dc296872b4151eb
Web page

ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/daac4aa1825de0dbc1a6eede2fa7f9fc53f14223

Vendor Advisories for CVE-2024-53171(1)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-aws-lts-20.04 (5.4.0.1142.139) @ focal2026-10-27ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-10-27ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1027.29~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04 (6.8.1-1020.21) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1028.30~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1010.12) @ noble2026-10-27ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-10-27ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1077.83~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-kvm (5.15.0.1076.72) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt (5.15.0.1033.33) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1044.48) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-fips (5.15.0.1079.69) @ jammy2026-10-27ubuntu
ubuntulinux-tools-realtime (5.15.0.1080.83) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1060 (5.4.0-1060.64) @ focal2026-10-27ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.211.206) @ focal2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1024.25~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-ibm-edge (5.15.0.1074.77~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1086.95~20.04.1.61) @ focal2026-10-27ubuntu
ubuntulinux-tools-ibm-edge (5.4.0.1090.95~18.04.1) @ bionic2026-10-27ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.136.147~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-aws-fips (5.4.0.1142.89) @ focal2026-10-27ubuntu
ubuntulinux-tools-gcp-fips (5.4.0.1145.87) @ focal2026-10-27ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1077.83~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-10-27ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-58.60~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1081.90~20.04.1) @ focal2026-10-27ubuntu
linuxKernel @ 5.4.287 (fixes >=4.20.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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)
  • every version up to 5.10.234-1: fixed in 5.10.234-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1, 6.1.119-1~deb11u1
  • every version up to 6.1.128-1~deb11u1: fixed in 6.1.128-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (32 versions)
  • every version up to 6.1.123-1: fixed in 6.1.123-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.3-1: fixed in 6.12.3-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-53171?
CVE-2024-53171 is a high-severity vulnerability; its CVE record was published on December 27, 2024. In the Linux kernel, the following vulnerability has been resolved: ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit After an insertion in TNC, the tree might split and cause a node to change its znode->parent. A further deletion of other nodes in the tree (which also could free…
When was the CVE record for CVE-2024-53171 published?
The CVE record for CVE-2024-53171 was published on December 27, 2024. 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-2024-53171 actively exploited?
CVE-2024-53171 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-53171?
CVE-2024-53171 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-53171?
A fix for CVE-2024-53171 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-53171 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-2024-53171

Explore →

Is Your Infrastructure Affected by CVE-2024-53171?

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

Book a Demo →Browse All CVEs