CVE-2026-45943

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
7.1EG
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.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

erofs: fix inline data read failure for ztailpacking pclusters

Compressed folios for ztailpacking pclusters must be valid before adding these pclusters to I/O chains. Otherwise, z_erofs_decompress_pcluster() may assume they are already valid and then trigger a NULL pointer dereference.

It is somewhat hard to reproduce because the inline data is in the same block as the tail of the compressed indexes, which are usually read just before. However, it may still happen if a fatal signal arrives while read_mapping_folio() is running, as shown below:

erofs: (device dm-1): z_erofs_pcluster_begin: failed to get inline data -4 Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008

...

pc : z_erofs_decompress_queue+0x4c8/0xa14 lr : z_erofs_decompress_queue+0x160/0xa14 sp : ffffffc08b3eb3a0 x29: ffffffc08b3eb570 x28: ffffffc08b3eb418 x27: 0000000000001000 x26: ffffff8086ebdbb8 x25: ffffff8086ebdbb8 x24: 0000000000000001 x23: 0000000000000008 x22: 00000000fffffffb x21: dead000000000700 x20: 00000000000015e7 x19: ffffff808babb400 x18: ffffffc089edc098 x17: 00000000c006287d x16: 00000000c006287d x15: 0000000000000004 x14: ffffff80ba8f8000 x13: 0000000000000004 x12: 00000006589a77c9 x11: 0000000000000015 x10: 0000000000000000 x9 : 0000000000000000 x8 : 0000000000000000 x7 : 0000000000000000 x6 : 000000000000003f x5 : 0000000000000040 x4 : ffffffffffffffe0 x3 : 0000000000000020 x2 : 0000000000000008 x1 : 0000000000000000 x0 : 0000000000000000 Call trace: z_erofs_decompress_queue+0x4c8/0xa14 z_erofs_runqueue+0x908/0x97c z_erofs_read_folio+0x128/0x228 filemap_read_folio+0x68/0x128 filemap_get_pages+0x44c/0x8b4 filemap_read+0x12c/0x5b8 generic_file_read_iter+0x4c/0x15c do_iter_readv_writev+0x188/0x1e0 vfs_iter_read+0xac/0x1a4 backing_file_read_iter+0x170/0x34c ovl_read_iter+0xf0/0x140 vfs_read+0x28c/0x344 ksys_read+0x80/0xf0 __arm64_sys_read+0x24/0x34 invoke_syscall+0x60/0x114 el0_svc_common+0x88/0xe4 do_el0_svc+0x24/0x30 el0_svc+0x40/0xa8 el0t_64_sync_handler+0x70/0xbc el0t_64_sync+0x1bc/0x1c0

Fix this by reading the inline data before allocating and adding the pclusters to the I/O chains.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (4)

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

erofs: fix inline data read failure for ztailpacking pclusters - kernel/git/stable/linux.git - Linux kernel stable tree

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

erofs: fix inline data read failure for ztailpacking pclusters - kernel/git/stable/linux.git - Linux kernel stable tree

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

erofs: fix inline data read failure for ztailpacking pclusters - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92088bd9aa2a7246bba8b9648fbc64edd173cf17
generic

erofs: fix inline data read failure for ztailpacking pclusters - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5de1aa0bf3a5db0b3cbf61959da5ac61250833ed

Vendor Advisories for CVE-2026-45943(2)

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

Patch Availability(14)

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

(3 across 3 ecosystems)
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.18~rc7-1~exp1 (100 versions)6.18.14-1

Weakness Classification(1)

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

All Vendor Advisories

(14)

Data Freshness Timeline

(refreshed 5× in last 7d / 85× 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 219 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45943?
CVE-2026-45943 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: erofs: fix inline data read failure for ztailpacking pclusters Compressed folios for ztailpacking pclusters must be valid before adding these pclusters to I/O chains. Otherwise, zerofsdecompress_pcluster() may assume they are…
When was CVE-2026-45943 disclosed?
CVE-2026-45943 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45943 actively exploited?
CVE-2026-45943 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 97.5% of all scored CVEs.
What is the CVSS score of CVE-2026-45943?
CVE-2026-45943 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-45943?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45943, 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-45943

Explore →

Is Your Infrastructure Affected by CVE-2026-45943?

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