CVE-2024-49958

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

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

ocfs2: reserve space for inline xattr before attaching reflink tree

One of our customers reported a crash and a corrupted ocfs2 filesystem. The crash was due to the detection of corruption. Upon troubleshooting, the fsck -fn output showed the below corruption

[EXTENT_LIST_FREE] Extent list in owner 33080590 claims 230 as the next free chain record, but fsck believes the largest valid value is 227. Clamp the next record value? n

The stat output from the debugfs.ocfs2 showed the following corruption where the "Next Free Rec:" had overshot the "Count:" in the root metadata block.

Inode: 33080590 Mode: 0640 Generation: 2619713622 (0x9c25a856) FS Generation: 904309833 (0x35e6ac49) CRC32: 00000000 ECC: 0000 Type: Regular Attr: 0x0 Flags: Valid Dynamic Features: (0x16) HasXattr InlineXattr Refcounted Extended Attributes Block: 0 Extended Attributes Inline Size: 256 User: 0 (root) Group: 0 (root) Size: 281320357888 Links: 1 Clusters: 141738 ctime: 0x66911b56 0x316edcb8 -- Fri Jul 12 06:02:30.829349048 2024 atime: 0x66911d6b 0x7f7a28d -- Fri Jul 12 06:11:23.133669517 2024 mtime: 0x66911b56 0x12ed75d7 -- Fri Jul 12 06:02:30.317552087 2024 dtime: 0x0 -- Wed Dec 31 17:00:00 1969 Refcount Block: 2777346 Last Extblk: 2886943 Orphan Slot: 0 Sub Alloc Slot: 0 Sub Alloc Bit: 14 Tree Depth: 1 Count: 227 Next Free Rec: 230 ## Offset Clusters Block# 0 0 2310 2776351 1 2310 2139 2777375 2 4449 1221 2778399 3 5670 731 2779423 4 6401 566 2780447 ....... .... ....... ....... .... .......

The issue was in the reflink workfow while reserving space for inline xattr. The problematic function is ocfs2_reflink_xattr_inline(). By the time this function is called the reflink tree is already recreated at the destination inode from the source inode. At this point, this function reserves space for inline xattrs at the destination inode without even checking if there is space at the root metadata block. It simply reduces the l_count from 243 to 227 thereby making space of 256 bytes for inline xattr whereas the inode already has extents beyond this index (in this case up to 230), thereby causing corruption.

The fix for this is to reserve space for inline metadata at the destination inode before the reflink tree gets recreated. The customer has verified the fix.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

October 21, 2024

Last Modified

August 5, 2026

References (9)

Patch Availability(31)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.127.126) @ jammy2026-05-23ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1073.73) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.127.137~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1071.77~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1071.71) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1078.87~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1039.43) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.11.0-18.18) @ oracular2026-05-23ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.11.0-1005.5) @ oracular2026-05-23ubuntu
ubuntulinux-tools-gcp-lts-20.04 (5.4.0.1143.145) @ focal2026-05-23ubuntu
ubuntulinux-virtual (6.8.0-54.56) @ noble2026-05-23ubuntu
ubuntulinux-tools-fips (4.4.0.1115.116) @ xenial2026-05-23ubuntu
ubuntulinux-virtual-hwe-18.04-edge (5.4.0.208.228~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1058 (5.4.0-1058.62) @ focal2026-05-23ubuntu
ubuntulinux-virtual-lts-xenial (4.4.0.270.276) @ xenial2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-57.59~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure-nvidia (6.8.0-1014.15) @ noble2026-05-23ubuntu
ubuntulinux-tools-fips (5.4.0.1116.113) @ focal2026-05-23ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1025.30~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1129.142~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-tools-iot (5.4.0.1048.46) @ focal2026-05-23ubuntu
ubuntulinux-tools-aws-edge (5.4.0.1142.152~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-tools-raspi2-hwe-18.04-edge (5.4.0.1129.160) @ focal2026-05-23ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1006.8) @ noble2026-05-23ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1023.25) @ noble2026-05-23ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1138.131) @ focal2026-05-23ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1022.25.2) @ noble2026-05-23ubuntu
ubuntulinux-tools-ibm-lts-20.04 (5.4.0.1086.115) @ focal2026-05-23ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1020.21) @ noble2026-05-23ubuntu
ubuntulinux-tools-oem-24.04b (6.11.0-1015.15) @ noble2026-05-23ubuntu
linuxKernel @ 4.19.323—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 rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (44 versions)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~deb11u16.1.119-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (30 versions)6.1.115-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—6.11.4-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—6.11.4-1—

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 31× 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.

Showing the most recent 100 of 166 total refreshes for this CVE.

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

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2024-49958?
CVE-2024-49958 is a medium vulnerability published on October 21, 2024. In the Linux kernel, the following vulnerability has been resolved: ocfs2: reserve space for inline xattr before attaching reflink tree One of our customers reported a crash and a corrupted ocfs2 filesystem. The crash was due to the detection of corruption. Upon troubleshooting, the fsck -fn output…
When was CVE-2024-49958 disclosed?
CVE-2024-49958 was first published in the National Vulnerability Database on October 21, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-49958 actively exploited?
CVE-2024-49958 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.1% of all scored CVEs.
What is the CVSS score of CVE-2024-49958?
CVE-2024-49958 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-49958?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-49958, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-49958

Explore →

Is Your Infrastructure Affected by CVE-2024-49958?

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

Start Free Scan →Browse All CVEs