CVE Intelligence
Unknown

CVE-2025-68820 — ext4: xattr: fix null pointer deref in ext4_raw_inode()

In the Linux kernel, the following vulnerability has been resolved: ext4: xattr: fix null pointer deref in ext4_raw_inode() If ext4_get_inode_loc() fails (e.g. if it returns -EFSCORRUPTED), iloc.bh will remain set to NULL. Since ext4_xattr_inode_dec_ref_all() lacks error checking, this will lead to a null pointer dereference in ext4_raw_inode(), called right after ext4_get_inode_loc(). Found by Linux Verification Center (linuxtesting.org) with SVACE.

Published Jan 13, 2026 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: Linux

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.2% (30-day exploitation probability)+2

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.21%
ahead of 11% of scored CVEs · Oct 14, 2026
Affects
Linux
Linux
CVSS base
—
Score not published yet.

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Linux Linux version 836e625b03a666cf93ff5be328c8cb30336db872version 6.15≥ 6.14.3 and < 6.15≥ 6.13.12 and < 6.14≥ 5.4.293 and < 5.5≥ 6.12.24 and < 6.12.64≥ 6.6.88 and < 6.6.120≥ 6.1.135 and < 6.1.160
and 11 more ≥ 5.15.181 and < 5.15.198≥ 5.10.237 and < 5.10.248≥ 76c365fa7e2a8bb85f0190cdb4b8cdc99b2fdce3 and < b72a3476f0c97d02f63a6e9fff127348d55436f6version 3bc6317033f365ce578eb6039445fb66162722fdversion 6aff941cb0f7d0c897c3698ad2e30672709135e3≥ c8e008b60492cf6fd31ef127aea6d02fd3d314cd and < b97cb7d6a051aa6ebd57906df0e26e9e36c26d14≥ c8e008b60492cf6fd31ef127aea6d02fd3d314cd and < ce5f54c065a4a7cbb92787f4f140917112350142≥ eb59cc31b6ea076021d14b04e7faab1636b87d0e and < 5b154e901fda2e98570b8f426a481f5740097dc2≥ 362a90cecd36e8a5c415966d0b75b04a0270e4dd and < b5d942922182e82724b7152cb998f540132885ec≥ cf9291a3449b04688b81e32621e88de8f4314b54 and < 190ad0f22ba49f1101182b80e3af50ca2ddfe72f≥ f737418b6de31c962c7192777ee4018906975383 and < 3d8d22e75f7edfa0b30ff27330fd6a1285d594c3
Vulnerable CVE Program (cve.org) e CISA ADP

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.21%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Not enough vector or weakness data: use the affected application’s logs as a starting point.
application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 13, 2026
  • Affected products added · linux/linux
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Deferred
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Jan 13, 2026 · Linux

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

11 on the record

Elsewhere on this site

Linux
every CVE for this vendor

Related CVEs (same products)

  • CVE-2026-99999 ipv4: validate checksum_start before completing checksum 10h
  • CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 10h
  • CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
  • CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
  • CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
  • CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No CVSS score published by NVD, the CNA, CISA or GitHub so far.
  • No fixed version, patch or mitigation documented.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-68820 is "ext4: xattr: fix null pointer deref in ext4_raw_inode()", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.21% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.