CVE-2022-49349

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-02-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-2022-54879 (ENISA EUVD) · GHSA-qwcq-8262-9j44 (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:

ext4: fix use-after-free in ext4_rename_dir_prepare

We got issue as follows: EXT4-fs (loop0): mounted filesystem without journal. Opts: ,errors=continue ext4_get_first_dir_block: bh->b_data=0xffff88810bee6000 len=34478 ext4_get_first_dir_block: *parent_de=0xffff88810beee6ae bh->b_data=0xffff88810bee6000 ext4_rename_dir_prepare: [1] parent_de=0xffff88810beee6ae ================================================================== BUG: KASAN: use-after-free in ext4_rename_dir_prepare+0x152/0x220 Read of size 4 at addr ffff88810beee6ae by task rep/1895

CPU: 13 PID: 1895 Comm: rep Not tainted 5.10.0+ #241 Call Trace: dump_stack+0xbe/0xf9 print_address_description.constprop.0+0x1e/0x220 kasan_report.cold+0x37/0x7f ext4_rename_dir_prepare+0x152/0x220 ext4_rename+0xf44/0x1ad0 ext4_rename2+0x11c/0x170 vfs_rename+0xa84/0x1440 do_renameat2+0x683/0x8f0 __x64_sys_renameat+0x53/0x60 do_syscall_64+0x33/0x40 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f45a6fc41c9 RSP: 002b:00007ffc5a470218 EFLAGS: 00000246 ORIG_RAX: 0000000000000108 RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f45a6fc41c9 RDX: 0000000000000005 RSI: 0000000020000180 RDI: 0000000000000005 RBP: 00007ffc5a470240 R08: 00007ffc5a470160 R09: 0000000020000080 R10: 00000000200001c0 R11: 0000000000000246 R12: 0000000000400bb0 R13: 00007ffc5a470320 R14: 0000000000000000 R15: 0000000000000000

The buggy address belongs to the page: page:00000000440015ce refcount:0 mapcount:0 mapping:0000000000000000 index:0x1 pfn:0x10beee flags: 0x200000000000000() raw: 0200000000000000 ffffea00043ff4c8 ffffea0004325608 0000000000000000 raw: 0000000000000001 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff88810beee580: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88810beee600: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff >ffff88810beee680: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ^ ffff88810beee700: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ffff88810beee780: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ================================================================== Disabling lock debugging due to kernel taint ext4_rename_dir_prepare: [2] parent_de->inode=3537895424 ext4_rename_dir_prepare: [3] dir=0xffff888124170140 ext4_rename_dir_prepare: [4] ino=2 ext4_rename_dir_prepare: ent->dir->i_ino=2 parent=-757071872

Reason is first directory entry which 'rec_len' is 34478, then will get illegal parent entry. Now, we do not check directory entry after read directory block in 'ext4_get_first_dir_block'. To solve this issue, check directory entry in 'ext4_get_first_dir_block'.

[ Trigger an ext4_error() instead of just warning if the directory is missing a '.' or '..' entry. Also make sure we return an error code if the file system is corrupted. -TYT ]

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
21st
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-28). 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

February 26, 2025

Last Modified

August 5, 2026

Advisory Details (9)

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

ext4: fix use-after-free in ext4_rename_dir_prepare - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: fix use-after-free in ext4_rename_dir_prepare - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: fix use-after-free in ext4_rename_dir_prepare - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/97f802a652a749422dede32071d29a53cf4bd034
Web page

ext4: fix use-after-free in ext4_rename_dir_prepare - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext4: fix use-after-free in ext4_rename_dir_prepare - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/364380c00912bed9b5d99eb485018360b0ecf64f
Web page

ext4: fix use-after-free in ext4_rename_dir_prepare - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1a3a15bf6f9963d755270cbdb282863b84839195
Web page

ext4: fix use-after-free in ext4_rename_dir_prepare - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10801095224de0d0ab06ae60698680c1f883a3ae
Web page

ext4: fix use-after-free in ext4_rename_dir_prepare - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ff38b99fa075ddd246487a28cb9af049f4ceef1
Web page

ext4: fix use-after-free in ext4_rename_dir_prepare - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0be698ecbe4471fcad80e81ec6a05001421041b3

Vendor Advisories for CVE-2022-49349(2)

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:5.14.0-162.6.1.el9_12022-11-15redhat
redhatkernel-0:4.18.0-425.3.1.el82022-11-08redhat
linuxKernel @ 4.9.318 (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 ... 5.10.92-2 (14 versions)
  • every version up to 5.10.127-1: fixed in 5.10.127-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 5.18.5-1: fixed in 5.18.5-1
—

Weakness Classification(1)

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

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 99 of 207 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 108 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-49349?
CVE-2022-49349 is a high-severity vulnerability; its CVE record was published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: ext4: fix use-after-free in ext4_rename_dir_prepare We got issue as follows: EXT4-fs (loop0): mounted filesystem without journal. Opts: ,errors=continue ext4_get_first_dir_block: bh->b_data=0xffff88810bee6000 len=34478…
When was the CVE record for CVE-2022-49349 published?
The CVE record for CVE-2022-49349 was published on February 26, 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-2022-49349 actively exploited?
CVE-2022-49349 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49349?
CVE-2022-49349 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2022-49349?
A fix for CVE-2022-49349 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-49349 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-2022-49349

Explore →

Is Your Infrastructure Affected by CVE-2022-49349?

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

Book a Demo →Browse All CVEs