Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-68264: ext4: refresh inline data size before write operations

Noroxi assessment

Priority: Monitor (action score 0/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.22% (FIRST EPSS).
  • Fixed version: Linux Linux 1687a055a555347b002f406676a1aaae4668f242, 210ac60a86a3ad2c76ae60e0dc71c34af6e7ea0b, 43bf001f0fe4e59bba47c897505222f959f4a1cc.

Low priority for now. Upgrade to Linux Linux 1687a055a555347b002f406676a1aaae4668f242, 210ac60a86a3ad2c76ae60e0dc71c34af6e7ea0b, 43bf001f0fe4e59bba47c897505222f959f4a1cc 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: ext4: refresh inline data size before write operations The cached ei->i_inline_size can become stale between the initial size check and when ext4_update_inline_data()/ext4_create_inline_data() use it. Although ext4_get_max_inline_size() reads the correct value at the time of the check, concurrent xattr operations can modify i_inline_size before ext4_write_lock_xattr() is acquired. This causes ext4_update_inline_data() and ext4_create_inline_data() to work with stale capacity values, leading to a BUG_ON() crash in ext4_write_inline_data(): kernel BUG at fs/ext4/inline.c:1331! BUG_ON(pos + len > EXT4_I(inode)->i_inline_size); The race window: 1. ext4_get_max_inline_size() reads i_inline_size = 60 (correct) 2. Size check passes for 50-byte write 3. [Another thread adds xattr, i_inline_size changes to 40] 4. ext4_write_lock_xattr() acquires lock 5. ext4_update_inline_data() uses stale i_inline_size = 60 6. Attempts to write 50 bytes but only 40 bytes actually available 7. BUG_ON() triggers Fix this by recalculating i_inline_size via ext4_find_inline_data_nolock() immediately after acquiring xattr_sem. This ensures ext4_update_inline_data() and ext4_create_inline_data() work with current values that are protected from concurrent modifications. This is similar to commit a54c4613dac1 ("ext4: fix race writing to an inline_data file while its xattrs are changing") which fixed i_inline_off staleness. This patch addresses the related i_inline_size staleness issue.

—No exploit Fix available
Published
Dec 16, 2025
Updated
Oct 15, 2026
EPSS
0.2% · 13th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
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.

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-2025-68264

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.

—

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

    • 3.8affected
    • 67cf5b09a46f72e048501b84996f2f77bc42e947 and later · before 54ab81ae5f218452e64470cd8a8139bb5880fe2baffected · git
    • 67cf5b09a46f72e048501b84996f2f77bc42e947 and later · before 43bf001f0fe4e59bba47c897505222f959f4a1ccaffected · git
    • 67cf5b09a46f72e048501b84996f2f77bc42e947 and later · before 89c2c41f0974e530b2d032c3695095aa0559adb1affected · git
    • 67cf5b09a46f72e048501b84996f2f77bc42e947 and later · before 1687a055a555347b002f406676a1aaae4668f242affected · git
    • 67cf5b09a46f72e048501b84996f2f77bc42e947 and later · before 210ac60a86a3ad2c76ae60e0dc71c34af6e7ea0baffected · git
    • 67cf5b09a46f72e048501b84996f2f77bc42e947 and later · before ca43ea29b4c4d2764aec8a26cffcfb677a871e6eaffected · git
    • 67cf5b09a46f72e048501b84996f2f77bc42e947 and later · before 58df743faf21ceb1880f930aa5dd428e2a5e415daffected · git
    • 67cf5b09a46f72e048501b84996f2f77bc42e947 and later · before 892e1cf17555735e9d021ab036c36bc7b58b0e3baffected · git
    • before 3.8not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.162-16.1.162-1
Debian:13linuxbefore 6.12.63-16.12.63-1
Debian:14linuxbefore 6.17.12-16.17.12-1
openSUSE:Tumbleweedkernel-sourcebefore 6.18.2-1.16.18.2-1.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-68262Dec 16, 2025 · crypto: zstd - fix double-free in per-CPU stream cleanup
    0Monitor
  • ← EarlierCVE-2025-68263Dec 16, 2025 · ksmbd: ipc: fix use-after-free in ipc_msg_send_request
    39Monitor
  • Later →CVE-2025-68265Dec 16, 2025 · nvme: fix admin request_queue lifetime
    31Monitor

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 Linux1687a055a555347b002f406676a1aaae4668f242Vendor (CNA)
Linux Linux210ac60a86a3ad2c76ae60e0dc71c34af6e7ea0bVendor (CNA)
Linux Linux43bf001f0fe4e59bba47c897505222f959f4a1ccVendor (CNA)
Linux Linux54ab81ae5f218452e64470cd8a8139bb5880fe2bVendor (CNA)
Linux Linux58df743faf21ceb1880f930aa5dd428e2a5e415dVendor (CNA)
Linux Linux892e1cf17555735e9d021ab036c36bc7b58b0e3bVendor (CNA)
Linux Linux89c2c41f0974e530b2d032c3695095aa0559adb1Vendor (CNA)
Linux Linuxca43ea29b4c4d2764aec8a26cffcfb677a871e6eVendor (CNA)
debian:linux6.1.162-1 · Debian:12Package registry (OSV)
opensuse:kernel-source6.18.2-1.1 · openSUSE:TumbleweedPackage 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.

No history yet (it accumulates with the daily EPSS job).

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

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

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 (9 more)

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

All records