Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-74308: ext4: fix kernel BUG in ext4_write_inline_data_end

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.17% (FIRST EPSS).
  • Fixed version: Linux Linux 0ae42b51607240990614e0843f0d3529aaff62cc, 13db1ccae4d38f6d9296ee74aa1d39b429959ddb, 260830a9a706f5d335398236fc788ce32f220de1.

Low priority for now. Upgrade to Linux Linux 0ae42b51607240990614e0843f0d3529aaff62cc, 13db1ccae4d38f6d9296ee74aa1d39b429959ddb, 260830a9a706f5d335398236fc788ce32f220de1 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: fix kernel BUG in ext4_write_inline_data_end When the data=journal mount option is used, the ext4_journalled_write_end() function incorrectly calls ext4_write_inline_data_end() without checking if the EXT4_STATE_MAY_INLINE_DATA flag is still set on the inode. If a previous attempt to convert the inline data to an extent failed (e.g. due to ENOSPC), the EXT4_STATE_MAY_INLINE_DATA flag is cleared, but the EXT4_INODE_INLINE_DATA flag remains set. In this scenario, the next call to ext4_write_begin() will not prepare the inline data xattr for writing, but ext4_journalled_write_end() will incorrectly attempt to write to it, triggering a BUG_ON(pos + len > EXT4_I(inode)->i_inline_size) in ext4_write_inline_data() since i_inline_size was not expanded. Fix this by ensuring that ext4_journalled_write_end() only calls ext4_write_inline_data_end() if the EXT4_STATE_MAY_INLINE_DATA flag is set, mirroring the behavior of ext4_write_end() and ext4_da_write_end().

—No exploit Fix available
Published
Aug 15, 2026
Updated
Oct 30, 2026
EPSS
0.1% · 6th 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.1%

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-2026-74308

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
    • 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb and later · before 13db1ccae4d38f6d9296ee74aa1d39b429959ddbaffected · git
    • 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb and later · before 260830a9a706f5d335398236fc788ce32f220de1affected · git
    • 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb and later · before 9808ae9fae996afa942bd963a39c9b1cdeebd0bdaffected · git
    • 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb and later · before f00f5c0dd55319bc33b76f72c853bda0e0a32edaaffected · git
    • 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb and later · before 0ae42b51607240990614e0843f0d3529aaff62ccaffected · git
    • 3fdcfb668fd78ec92d9bc2daddf1d41e2a8a30bb and later · before ad09aa45965d3fafaf9963bc78109b73c0f9ac8daffected · git
    • before 3.8not affected · semver
    • 6.1.191 and later · up to and including 6.1.*not affected · semver
    • 6.6.145 and later · up to and including 6.6.*not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxfrom 0—
Debian:13linuxbefore 6.12.100-16.12.100-1
Debian:14linuxbefore 7.1.5-17.1.5-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-2026-74305Aug 15, 2026 · bpf: Tighten cgroup storage cookie checks for prog arrays
    31Monitor
  • ← EarlierCVE-2026-74307Aug 15, 2026 · ext4: validate donor file superblock early in EXT4_IOC_MOVE_EXT
    0Monitor
  • Later →CVE-2026-74310Aug 15, 2026 · vhost/net: complete zerocopy ubufs only once
    37Monitor

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 Linux0ae42b51607240990614e0843f0d3529aaff62ccVendor (CNA)
Linux Linux13db1ccae4d38f6d9296ee74aa1d39b429959ddbVendor (CNA)
Linux Linux260830a9a706f5d335398236fc788ce32f220de1Vendor (CNA)
Linux Linux9808ae9fae996afa942bd963a39c9b1cdeebd0bdVendor (CNA)
Linux Linuxad09aa45965d3fafaf9963bc78109b73c0f9ac8dVendor (CNA)
Linux Linuxf00f5c0dd55319bc33b76f72c853bda0e0a32edaVendor (CNA)
debian:linux6.12.100-1 · Debian:13Package 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

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

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

All records