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.
Security readout for executives and security teams
Plain-English summary
A Linux XFS filesystem error can mishandle an internal memory buffer after an attribute lookup fails. A locally authenticated, low-privilege user may be able to trigger serious confidentiality, integrity, or availability impact. The supplied CVSS score is 7.8, but the sources provide no evidence of active exploitation.
Executive priority
Treat as a high-priority kernel maintenance issue, especially on shared Linux servers using XFS. Schedule prompt, tested kernel updates. Emergency incident response is not justified solely by this bundle because active exploitation is not reported and exploitation requires local privileges.
Technical view
xfs_attr_leaf_hasname() could return a pointer to an already released buffer when xfs_attr3_leaf_lookup_int() failed with errors other than -ENOATTR or -EEXIST. Callers could consequently mishandle buffer lifetime. The fix removes the helper and places read, lookup, and release handling directly in each caller.
Likely exposure
Exposure is limited to Linux systems within the source-listed affected versions where XFS and the vulnerable attribute-handling paths are used. Exploitation requires local access with low privileges. The supplied version data is ambiguous, so confirm exposure against distribution kernel advisories and backport records.
Exploitation context
The CVSS vector describes a local, low-complexity attack requiring low privileges and no user interaction, with potentially high confidentiality, integrity, and availability impact. KEV is false, and the supplied sources do not report public or active exploitation. No remote attack path is established.
Researcher notes
The defect concerns inconsistent ownership and release semantics across XFS attribute read and lookup failures. No CWE is supplied, and the bundle does not establish exploitability beyond the CVSS assessment. Exact vulnerable and fixed version boundaries are unclear; use commit-level and distribution backport verification.
Mitigation direction
Install a vendor-supported kernel containing the applicable upstream XFS fix.
Check distribution advisories for backported fixes before relying on kernel version numbers.
Prioritize multi-user systems and hosts processing untrusted XFS filesystems.
Restrict unnecessary local access until affected kernels are updated.
Validation and detection
Inventory kernel versions and identify systems actively using XFS.
Compare vendor kernel packages and changelogs with the four referenced fix commits.
Confirm the updated kernel is running after installation and reboot.
Review kernel logs for XFS errors or unexpected crashes without treating them as proof of exploitation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-43153 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
0ADP providers
5Source links
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.