Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-49958: ocfs2: reserve space for inline xattr before attaching reflink tree

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.27% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 020f5c53c17f66c0a8f2d37dad27ace301b8d8a1, 3.1, 3.10; Azure Linux 3.0 ARM 6.6.57.1-2; Azure Linux 3.0 x64 6.6.57.1-2.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 020f5c53c17f66c0a8f2d37dad27ace301b8d8a1, 3.1, 3.10; Azure Linux 3.0 ARM 6.6.57.1-2; Azure Linux 3.0 x64 6.6.57.1-2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Oct 21, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 19th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-49958

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel3.0.87 and later · before 3.2
  • linux linux kernel3.2.49 and later · before 3.4
  • linux linux kernel3.4.54 and later · before 3.9
  • linux linux kernel3.9.11 and later · before 3.10
  • linux linux kernel3.10.2 and later · before 3.11
  • linux linux kernel3.11 and later · before 5.10.227
  • linux linux kernel5.11 and later · before 5.15.168
  • linux linux kernel5.16 and later · before 6.1.113
  • linux linux kernel6.2 and later · before 6.6.55
  • linux linux kernel6.7 and later · before 6.10.14
  • linux linux kernel6.11 and later · before 6.11.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 3a32958d2ac96070c53d04bd8e013c97b260b5e6, 93f26306db89c9dc37885b76a1082e6d54d23b16, 26a849f49fb3347d126a0ed6611173f903374ef4, 1e7e4c9ae2a78a6791a2ca91a6a400f94855f01e, 1926bf8ae44d80c9f50103f11fc4f17e2e2bf684, 3.11affected
    • ef962df057aaafd714f5c22ba3de1be459571fdf and later · before 5c9807c523b4fca81d3e8e864dabc8c806402121affected · git
    • ef962df057aaafd714f5c22ba3de1be459571fdf and later · before 74364cb578dcc0b6c9109519d19cbe5a56afac9aaffected · git
    • ef962df057aaafd714f5c22ba3de1be459571fdf and later · before aac31d654a0a31cb0d2fa36ae694f4e164a52707affected · git
    • ef962df057aaafd714f5c22ba3de1be459571fdf and later · before 020f5c53c17f66c0a8f2d37dad27ace301b8d8a1affected · git
    • ef962df057aaafd714f5c22ba3de1be459571fdf and later · before 5c2072f02c0d75802ec28ec703b7d43a0dd008b5affected · git
    • ef962df057aaafd714f5c22ba3de1be459571fdf and later · before 637c00e06564a945e9d0edb3d78d362d64935f9faffected · git
    • ef962df057aaafd714f5c22ba3de1be459571fdf and later · before 9f9a8f3ac65b4147f1a7b6c05fad5192c0e3c3d9affected · git
    • ef962df057aaafd714f5c22ba3de1be459571fdf and later · before 96ce4c3537114d1698be635f5e36c62dc49df7a4affected · git
    • ef962df057aaafd714f5c22ba3de1be459571fdf and later · before 5ca60b86f57a4d9648f68418a725b3a7de2816b0affected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.115-16.1.115-1
Debian:13linuxbefore 6.11.4-16.11.4-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-49956Oct 21, 2024 · gfs2: fix double destroy_workqueue error
    22Monitor
  • ← EarlierCVE-2024-49957Oct 21, 2024 · ocfs2: fix null-ptr-deref when journal load failed.
    22Monitor
  • Later →CVE-2024-49959Oct 21, 2024 · jbd2: stop waiting for space when jbd2_cleanup_journal_tail() returns error
    22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux020f5c53c17f66c0a8f2d37dad27ace301b8d8a1Vendor (CNA)
Linux Linux3.1Vendor (CNA)
Linux Linux3.10Vendor (CNA)
Linux Linux3.11Vendor (CNA)
Linux Linux3.3Vendor (CNA)
Linux Linux3.5Vendor (CNA)
Linux Linux5c2072f02c0d75802ec28ec703b7d43a0dd008b5Vendor (CNA)
Linux Linux5c9807c523b4fca81d3e8e864dabc8c806402121Vendor (CNA)
Linux Linux5ca60b86f57a4d9648f68418a725b3a7de2816b0Vendor (CNA)
Linux Linux637c00e06564a945e9d0edb3d78d362d64935f9fVendor (CNA)
Linux Linux74364cb578dcc0b6c9109519d19cbe5a56afac9aVendor (CNA)
Linux Linux96ce4c3537114d1698be635f5e36c62dc49df7a4Vendor (CNA)
Linux Linux9f9a8f3ac65b4147f1a7b6c05fad5192c0e3c3d9Vendor (CNA)
Linux Linuxaac31d654a0a31cb0d2fa36ae694f4e164a52707Vendor (CNA)
Azure Linux 3.0 ARM6.6.57.1-2 · kernelMicrosoft (MSRC)
Azure Linux 3.0 x646.6.57.1-2 · kernelMicrosoft (MSRC)
debian:linux6.1.115-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records