CVE-2026-46002

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-05-27. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

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

ext2: reject inodes with zero i_nlink and valid mode in ext2_iget()

ext2_iget() already rejects inodes with i_nlink == 0 when i_mode is zero or i_dtime is set, treating them as deleted. However, the case of i_nlink == 0 with a non-zero mode and zero dtime slips through. Since ext2 has no orphan list, such a combination can only result from filesystem corruption - a legitimate inode deletion always sets either i_dtime or clears i_mode before freeing the inode.

A crafted image can exploit this gap to present such an inode to the VFS, which then triggers WARN_ON inside drop_nlink() (fs/inode.c) via ext2_unlink(), ext2_rename() and ext2_rmdir():

WARNING: CPU: 3 PID: 609 at fs/inode.c:336 drop_nlink+0xad/0xd0 fs/inode.c:336 CPU: 3 UID: 0 PID: 609 Comm: syz-executor Not tainted 6.12.77+ #1 Call Trace: inode_dec_link_count include/linux/fs.h:2518 [inline] ext2_unlink+0x26c/0x300 fs/ext2/namei.c:295 vfs_unlink+0x2fc/0x9b0 fs/namei.c:4477 do_unlinkat+0x53e/0x730 fs/namei.c:4541 __x64_sys_unlink+0xc6/0x110 fs/namei.c:4587 do_syscall_64+0xf5/0x220 arch/x86/entry/common.c:78 entry_SYSCALL_64_after_hwframe+0x77/0x7f

WARNING: CPU: 0 PID: 646 at fs/inode.c:336 drop_nlink+0xad/0xd0 fs/inode.c:336 CPU: 0 UID: 0 PID: 646 Comm: syz.0.17 Not tainted 6.12.77+ #1 Call Trace: inode_dec_link_count include/linux/fs.h:2518 [inline] ext2_rename+0x35e/0x850 fs/ext2/namei.c:374 vfs_rename+0xf2f/0x2060 fs/namei.c:5021 do_renameat2+0xbe2/0xd50 fs/namei.c:5178 __x64_sys_rename+0x7e/0xa0 fs/namei.c:5223 do_syscall_64+0xf5/0x220 arch/x86/entry/common.c:78 entry_SYSCALL_64_after_hwframe+0x77/0x7f

WARNING: CPU: 0 PID: 634 at fs/inode.c:336 drop_nlink+0xad/0xd0 fs/inode.c:336 CPU: 0 UID: 0 PID: 634 Comm: syz-executor Not tainted 6.12.77+ #1 Call Trace: inode_dec_link_count include/linux/fs.h:2518 [inline] ext2_rmdir+0xca/0x110 fs/ext2/namei.c:311 vfs_rmdir+0x204/0x690 fs/namei.c:4348 do_rmdir+0x372/0x3e0 fs/namei.c:4407 __x64_sys_unlinkat+0xf0/0x130 fs/namei.c:4577 do_syscall_64+0xf5/0x220 arch/x86/entry/common.c:78 entry_SYSCALL_64_after_hwframe+0x77/0x7f

Extend the existing i_nlink == 0 check to also catch this case, reporting the corruption via ext2_error() and returning -EFSCORRUPTED. This rejects the inode at load time and prevents it from reaching any of the namei.c paths.

Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
2.4%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 16, 2026

Advisory Details (8)

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

ext2: reject inodes with zero i_nlink and valid mode in ext2_iget() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext2: reject inodes with zero i_nlink and valid mode in ext2_iget() - kernel/git/stable/linux.git - Linux kernel stable tree

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

ext2: reject inodes with zero i_nlink and valid mode in ext2_iget() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9e2d67fb2b73eeff8b601e26b332128eae8147bb
generic

ext2: reject inodes with zero i_nlink and valid mode in ext2_iget() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/470264bbec499e276a89a6431144ae58f411ea4d
generic

ext2: reject inodes with zero i_nlink and valid mode in ext2_iget() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/32e0b925572686399243834ec99e2a9d85c62eae
generic

ext2: reject inodes with zero i_nlink and valid mode in ext2_iget() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2dde6377ab2e46bb80cf066c659ef016f3ad7a9b
generic

ext2: reject inodes with zero i_nlink and valid mode in ext2_iget() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25947cc5b2374cd5bf627fe3141496444260d04f
generic

ext2: reject inodes with zero i_nlink and valid mode in ext2_iget() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b80cf48bcf0e1937af9cd6c7beb188762bbf7c5

Vendor Advisories for CVE-2026-46002(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-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-11ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-11ubuntu
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

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.

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 / 61× 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 103 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-46002?
CVE-2026-46002 is a medium vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: ext2: reject inodes with zero inlink and valid mode in ext2iget() ext2iget() already rejects inodes with inlink == 0 when i_mode is zero or i_dtime is set, treating them as deleted. However, the case of i_nlink == 0 with a non-zero…
When was CVE-2026-46002 disclosed?
CVE-2026-46002 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46002 actively exploited?
CVE-2026-46002 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46002?
CVE-2026-46002 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46002?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46002, 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-46002

Explore →

Is Your Infrastructure Affected by CVE-2026-46002?

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

Start Free Scan →Browse All CVEs