ext4: guard against EA inode refcount underflow in xattr update
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 6b879c4c6bbaab03c0ad2a983953bd1410bb165e| No fix yet |
| Linux Linux | — |
|
In the Linux kernel, the following vulnerability has been resolved:
ext4: guard against EA inode refcount underflow in xattr update
syzkaller found a path where ext4_xattr_inode_update_ref() reads an EA inode refcount that is already <= 0 and then applies ref_change (often -1). That lets the refcount underflow and we proceed with a bogus value, triggering errors like:
EXT4-fs error: EA inode <n> ref underflow: ref_count=-1 ref_change=-1 EXT4-fs warning: ea_inode dec ref err=-117
Make the invariant explicit: if the current refcount is non-positive, treat this as on-disk corruption, emit ext4_error_inode(), and fail the operation with -EFSCORRUPTED instead of updating the refcount. Delete the WARN_ONCE() as negative refcounts are now impossible; keep error reporting in ext4_error_inode().
This prevents the underflow and the follow-on orphan/cleanup churn.
From the CVE record · Linux
The Linux kernel’s ext4 xattr update path can underflow an EA inode refcount when the on-disk refcount is already non-positive. This can trigger filesystem errors and follow-on orphan or cleanup activity. The input does not specify an attacker access path, authentication requirement, or user interaction.
Engineers running Linux kernels with ext4 should check their versions against the vendor advisory; affected versions are not specified.