CVE-2026-46094

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

ext4: fix bounds check in check_xattrs() to prevent out-of-bounds access

The bounds check for the next xattr entry in check_xattrs() uses (void *)next >= end, which allows next to point within sizeof(u32) bytes of end. On the next loop iteration, IS_LAST_ENTRY() reads 4 bytes via *(__u32 *)(entry), which can overrun the valid xattr region.

For example, if next lands at end - 1, the check passes since next < end, but IS_LAST_ENTRY() reads 4 bytes starting at end - 1, accessing 3 bytes beyond the valid region.

Fix this by changing the check to (void *)next + sizeof(u32) > end, ensuring there is always enough space for the IS_LAST_ENTRY() read on the subsequent iteration.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
2.6%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 25, 2026

Advisory Details (5)

Auto-updated Jun 25, 2026
No patch confirmed yet.
generic

ext4: fix bounds check in check_xattrs() to prevent out-of-bounds access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/eceafc31ea7b42c984ece10d79d505c0bb6615d5
generic

ext4: fix bounds check in check_xattrs() to prevent out-of-bounds access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ab6da97bc310db35d4e4ef5354bc3ff626b0698c
generic

ext4: fix bounds check in check_xattrs() to prevent out-of-bounds access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a5314d2387633a272a04d1bd8727f99058e4e68
generic

ext4: fix bounds check in check_xattrs() to prevent out-of-bounds access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/537e065977022aa22f2c2503e8accaf16622e0fd
generic

ext4: fix bounds check in check_xattrs() to prevent out-of-bounds access - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/520986722dbf869c122252123fc161c7302eab7d

Vendor Advisories for CVE-2026-46094(2)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-07-11ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-07-11ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-11ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-11ubuntu

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.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 60× 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.

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

Frequently asked(5)

What is CVE-2026-46094?
CVE-2026-46094 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: ext4: fix bounds check in check_xattrs() to prevent out-of-bounds access The bounds check for the next xattr entry in check_xattrs() uses (void *)next >= end, which allows next to point within sizeof(u32) bytes of end. On the next…
When was CVE-2026-46094 disclosed?
CVE-2026-46094 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46094 actively exploited?
CVE-2026-46094 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46094?
CVE-2026-46094 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-46094?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46094, 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

Explore the affected products and dependency analysis for CVE-2026-46094

Explore →

Is Your Infrastructure Affected by CVE-2026-46094?

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

Start Free Scan →Browse All CVEs