CVE-2022-49708

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2025-10-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

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

ext4: fix bug_on ext4_mb_use_inode_pa

Hulk Robot reported a BUG_ON: ================================================================== kernel BUG at fs/ext4/mballoc.c:3211! [...] RIP: 0010:ext4_mb_mark_diskspace_used.cold+0x85/0x136f [...] Call Trace: ext4_mb_new_blocks+0x9df/0x5d30 ext4_ext_map_blocks+0x1803/0x4d80 ext4_map_blocks+0x3a4/0x1a10 ext4_writepages+0x126d/0x2c30 do_writepages+0x7f/0x1b0 __filemap_fdatawrite_range+0x285/0x3b0 file_write_and_wait_range+0xb1/0x140 ext4_sync_file+0x1aa/0xca0 vfs_fsync_range+0xfb/0x260 do_fsync+0x48/0xa0 [...] ==================================================================

Above issue may happen as follows: ------------------------------------- do_fsync vfs_fsync_range ext4_sync_file file_write_and_wait_range __filemap_fdatawrite_range do_writepages ext4_writepages mpage_map_and_submit_extent mpage_map_one_extent ext4_map_blocks ext4_mb_new_blocks ext4_mb_normalize_request >>> start + size <= ac->ac_o_ex.fe_logical ext4_mb_regular_allocator ext4_mb_simple_scan_group ext4_mb_use_best_found ext4_mb_new_preallocation ext4_mb_new_inode_pa ext4_mb_use_inode_pa >>> set ac->ac_b_ex.fe_len <= 0 ext4_mb_mark_diskspace_used >>> BUG_ON(ac->ac_b_ex.fe_len <= 0);

we can easily reproduce this problem with the following commands: fallocate -l100M disk mkfs.ext4 -b 1024 -g 256 disk mount disk /mnt fsstress -d /mnt -l 0 -n 1000 -p 1

The size must be smaller than or equal to EXT4_BLOCKS_PER_GROUP. Therefore, "start + size <= ac->ac_o_ex.fe_logical" may occur when the size is truncated. So start should be the start position of the group where ac_o_ex.fe_logical is located after alignment. In addition, when the value of fe_logical or EXT4_BLOCKS_PER_GROUP is very large, the value calculated by start_off is more accurate.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
19.8%
KEV
Not listed

Published

February 26, 2025

Last Modified

October 24, 2025

References (8)

Vendor Advisories for CVE-2022-49708(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-162.6.1.el9_12022-11-15redhat
redhatkernel-0:4.18.0-425.3.1.el82022-11-08redhat

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

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

Frequently asked(5)

What is CVE-2022-49708?
CVE-2022-49708 is a medium vulnerability published on February 26, 2025. In the Linux kernel, the following vulnerability has been resolved: ext4: fix bugon ext4mbuseinode_pa Hulk Robot reported a BUG_ON: ================================================================== kernel BUG at fs/ext4/mballoc.c:3211! [...] RIP: 0010:ext4mbmarkdiskspaceused.cold+0x85/0x136f [...]…
When was CVE-2022-49708 disclosed?
CVE-2022-49708 was first published in the National Vulnerability Database on February 26, 2025, with the most recent update on October 24, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-49708 actively exploited?
CVE-2022-49708 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-49708?
CVE-2022-49708 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49708?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-49708, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-49708

Explore →

Is Your Infrastructure Affected by CVE-2022-49708?

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

Start Free Scan →Browse All CVEs