# xfs: don't irele after failing to iget in xfs_attri_recover_work

CVE record · `CVE-2026-43063`

- **Identifiers:** `CVE-2026-43063`
- **State:** Confirmed
- **Severity:** CVSS 7.8 High
- **Critical:** No
- **CNA:** Linux
- **Weakness (CWE):** [CWE-416](https://cwe.mitre.org/data/definitions/416.html)
- **Tags:** [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 5 May 2026
- **Updated:** 19 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 5 May 2026, 15:23 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `ae673f534a30976ce5e709c4535a59c12b786ef3 to before b5c5a50c2f513d4a13a6763564a07b470e69cc5a` (git)
  - affected: `ae673f534a30976ce5e709c4535a59c12b786ef3 to before a1a5df1038f0b3c560d204270373621a4e622808` (git)
  - affected: `ae673f534a30976ce5e709c4535a59c12b786ef3 to before 40082d08b638485cbaa543dc8087a3d1844d6f08` (git)
  - affected: `ae673f534a30976ce5e709c4535a59c12b786ef3 to before 70685c291ef82269180758130394ecdc4496b52c` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.10`
  - unaffected: `before 6.10` (semver)
  - unaffected: `6.12.80 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.21 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.11 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

- 7.8 High, CVSS 3.1: `CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`, from CNA (Linux)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0013, the 2nd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 5 May 2026, 16:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43063)

## Sources

- [CVE List: CVE-2026-43063](https://www.cve.org/CVERecord?id=CVE-2026-43063)
- [NVD: CVE-2026-43063](https://nvd.nist.gov/vuln/detail/CVE-2026-43063)

### References from the CNA

- <https://git.kernel.org/stable/c/b5c5a50c2f513d4a13a6763564a07b470e69cc5a>
- <https://git.kernel.org/stable/c/a1a5df1038f0b3c560d204270373621a4e622808>
- <https://git.kernel.org/stable/c/40082d08b638485cbaa543dc8087a3d1844d6f08>
- <https://git.kernel.org/stable/c/70685c291ef82269180758130394ecdc4496b52c>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-43063>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-43063/>. Everything for agents: <https://agentprime.io/llms.txt>.
