CVE-2026-43153

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-06. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 6, 2026

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated May 13, 2026
No patch confirmed yet.
generic

xfs: remove xfs_attr_leaf_hasname - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/530082df991903f3330354e99e0cb7b05debfa86
generic

xfs: remove xfs_attr_leaf_hasname - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/457121c01f609b9934addbb04d5c1ef638c71c61
generic

xfs: remove xfs_attr_leaf_hasname - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3a65ea768b8094e4699e72f9ab420eb9e0f3f568
generic

xfs: remove xfs_attr_leaf_hasname - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2fbc8421d1db102c0e5458607e042a23a03648b1

Vendor Advisories for CVE-2026-43153(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(13)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc5-1~exp1 (335 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (113 versions)6.19.6-1

All Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 4× in last 7d / 72× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 208 total refreshes for this CVE.

  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-08-30 19:17 UTCEPSS rescore
  4. 2026-08-30 01:22 UTCEPSS rescore
  5. 2026-08-28 21:41 UTCEPSS rescore
  6. 2026-08-27 14:25 UTCEPSS rescore
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 13:49 UTCEPSS rescore
  9. 2026-08-23 20:13 UTCEG score recompute
  10. 2026-08-23 20:13 UTCVendor advisory
  11. 2026-08-23 20:13 UTCGHSA enrichment
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-20 22:55 UTCEPSS rescore
  15. 2026-08-19 17:04 UTCEPSS rescore
  16. 2026-08-18 13:48 UTCEPSS rescore
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 12:57 UTCEG score recompute
  19. 2026-08-17 12:57 UTCVendor advisory
  20. 2026-08-17 12:57 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 04:54 UTCEG score recompute
  23. 2026-08-16 04:54 UTCVendor advisory
  24. 2026-08-16 04:54 UTCGHSA enrichment
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 75 more
  1. 2026-08-15 02:06 UTCEG score recompute
  2. 2026-08-15 02:06 UTCVendor advisory
  3. 2026-08-15 02:06 UTCGHSA enrichment
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 14:48 UTCVendor advisory
  6. 2026-08-14 14:48 UTCGHSA enrichment
  7. 2026-08-14 03:29 UTCEG score recompute
  8. 2026-08-14 03:29 UTCVendor advisory
  9. 2026-08-14 03:29 UTCGHSA enrichment
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 04:20 UTCVendor advisory
  12. 2026-08-13 04:20 UTCGHSA enrichment
  13. 2026-08-12 17:01 UTCEG score recompute
  14. 2026-08-12 17:01 UTCVendor advisory
  15. 2026-08-12 17:01 UTCGHSA enrichment
  16. 2026-08-12 13:51 UTCEPSS rescore
  17. 2026-08-11 16:01 UTCEG score recompute
  18. 2026-08-11 16:01 UTCVendor advisory
  19. 2026-08-11 16:00 UTCGHSA enrichment
  20. 2026-08-11 13:43 UTCEPSS rescore
  21. 2026-08-11 01:33 UTCVendor advisory
  22. 2026-08-11 01:33 UTCGHSA enrichment
  23. 2026-08-10 12:44 UTCVendor advisory
  24. 2026-08-10 12:44 UTCGHSA enrichment
  25. 2026-08-10 01:13 UTCVendor advisory
  26. 2026-08-10 01:13 UTCGHSA enrichment
  27. 2026-08-09 13:55 UTCEG score recompute
  28. 2026-08-09 13:55 UTCVendor advisory
  29. 2026-08-09 13:55 UTCGHSA enrichment
  30. 2026-08-09 13:46 UTCEPSS rescore
  31. 2026-08-09 02:36 UTCEG score recompute
  32. 2026-08-09 02:36 UTCVendor advisory
  33. 2026-08-09 02:36 UTCGHSA enrichment
  34. 2026-08-08 16:37 UTCEPSS rescore
  35. 2026-08-08 11:52 UTCVendor advisory
  36. 2026-08-08 11:52 UTCGHSA enrichment
  37. 2026-08-08 00:33 UTCEG score recompute
  38. 2026-08-08 00:33 UTCVendor advisory
  39. 2026-08-08 00:33 UTCGHSA enrichment
  40. 2026-08-07 13:15 UTCVendor advisory
  41. 2026-08-07 13:14 UTCGHSA enrichment
  42. 2026-08-07 01:55 UTCEG score recompute
  43. 2026-08-07 01:55 UTCVendor advisory
  44. 2026-08-07 01:54 UTCGHSA enrichment
  45. 2026-08-06 13:46 UTCEPSS rescore
  46. 2026-08-06 12:29 UTCVendor advisory
  47. 2026-08-06 12:29 UTCGHSA enrichment
  48. 2026-08-06 01:10 UTCEG score recompute
  49. 2026-08-06 01:10 UTCVendor advisory
  50. 2026-08-06 01:10 UTCGHSA enrichment
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-05 13:52 UTCEG score recompute
  53. 2026-08-05 13:52 UTCVendor advisory
  54. 2026-08-05 13:52 UTCGHSA enrichment
  55. 2026-08-04 15:10 UTCEPSS rescore
  56. 2026-08-04 10:38 UTCEPSS rescore
  57. 2026-08-03 19:53 UTCEG score recompute
  58. 2026-08-03 19:53 UTCVendor advisory
  59. 2026-08-03 19:53 UTCGHSA enrichment
  60. 2026-08-03 10:36 UTCEPSS rescore
  61. 2026-08-03 03:59 UTCVendor advisory
  62. 2026-08-03 03:59 UTCGHSA enrichment
  63. 2026-08-02 16:29 UTCVendor advisory
  64. 2026-08-02 16:29 UTCGHSA enrichment
  65. 2026-08-02 05:09 UTCEG score recompute
  66. 2026-08-02 05:09 UTCVendor advisory
  67. 2026-08-02 05:09 UTCGHSA enrichment
  68. 2026-08-02 02:27 UTCEPSS rescore
  69. 2026-08-01 04:16 UTCEPSS rescore
  70. 2026-07-30 16:28 UTCEPSS rescore
  71. 2026-07-30 01:30 UTCEPSS rescore
  72. 2026-07-28 15:36 UTCEPSS rescore
  73. 2026-07-27 14:13 UTCEPSS rescore
  74. 2026-07-26 14:54 UTCEPSS rescore
  75. 2026-07-26 14:54 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-43153?
CVE-2026-43153 is a high vulnerability published on May 6, 2026. In the Linux kernel, the following vulnerability has been resolved: xfs: remove xfsattrleaf_hasname The calling convention of xfsattrleaf_hasname() is problematic, because it returns a NULL buffer when xfsattr3leaf_read fails, a valid buffer when xfsattr3leaflookupint returns -ENOATTR or -EEXIST,…
When was CVE-2026-43153 disclosed?
CVE-2026-43153 was first published in the National Vulnerability Database on May 6, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43153 actively exploited?
CVE-2026-43153 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.5% of all scored CVEs.
What is the CVSS score of CVE-2026-43153?
CVE-2026-43153 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-43153?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43153, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-43153

Explore →

Is Your Infrastructure Affected by CVE-2026-43153?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.