erofs: fix metabuf leak in inode xattr initialization
Summary
| CVE | CVE-2026-64146 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-07-19 16:17:56 UTC |
| Updated | 2026-07-19 16:17:56 UTC |
| Description | In the Linux kernel, the following vulnerability has been resolved:
erofs: fix metabuf leak in inode xattr initialization
commit bb88e8da0025 ("erofs: use meta buffers for xattr operations")
converted xattr operations to use on-stack erofs_buf instances.
erofs_init_inode_xattrs() uses such a metabuf while reading the inline
xattr header and shared xattr id array.
Some error paths after erofs_read_metabuf() leave through out_unlock
without dropping the metabuf, so the folio reference can leak.
Consolidate the cleanup at out_unlock. erofs_put_metabuf() is a
no-op if no folio has been acquired, and this keeps all paths after
taking EROFS_I_BL_XATTR_BIT covered by a single cleanup site. |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected bb88e8da00253bea0e7f0f4cdfd7910572d7799f 492c73b21fefa36f3869cb2b188ffb7fe37b3a9b git |
Not specified |
| CNA |
Linux |
Linux |
affected bb88e8da00253bea0e7f0f4cdfd7910572d7799f 79b09c54c6563df9846ca3094bcfd72082c3e1d7 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5.17 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 5.17 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0.11 7.0.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.1 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/79b09c54c6563df9846ca3094bcfd72082c3e1d7 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/492c73b21fefa36f3869cb2b188ffb7fe37b3a9b |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.