xfs: remove xfs_attr_leaf_hasname
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 07120f1abdff80f3d1351f733661abe28d609535 · < 3a65ea768b8094e4699e72f9ab420eb9e0f3f568| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
xfs: remove xfs_attr_leaf_hasname
The calling convention of xfs_attr_leaf_hasname() is problematic, because it returns a NULL buffer when xfs_attr3_leaf_read fails, a valid buffer when xfs_attr3_leaf_lookup_int returns -ENOATTR or -EEXIST, and a non-NULL buffer pointer for an already released buffer when xfs_attr3_leaf_lookup_int fails with other error values.
Fix this by simply open coding xfs_attr_leaf_hasname in the callers, so that the buffer release code is done by each caller of xfs_attr3_leaf_read.
From the CVE record · Linux
The Linux kernel's XFS attribute lookup can leave a pointer to an already released buffer when a lookup fails with certain errors. This creates a use-after-free condition; the input does not specify what an attacker could achieve or whether network access, authentication, or user interaction is required.
Anyone running a Linux kernel with XFS should check their kernel version; affected versions were not provided.