CVE-2026-74350

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ocfs2: validate fast symlink target during inode read

ocfs2_validate_inode_block() already rejects several inconsistent self-contained dinodes before they are exposed to the rest of the filesystem. Fast symlinks need the same treatment.

A zero-cluster symlink is treated as a fast symlink and later read through page_get_link() and ocfs2_fast_symlink_read_folio(). That path uses strnlen() on the inline payload and then copies len + 1 bytes into the folio. If a corrupt dinode stores an i_size that does not fit the inline area or omits the terminating NUL at i_size, that copy reads past the end of the inode block buffer.

Reject zero-cluster symlink dinodes whose i_size exceeds the inline fast-symlink capacity or whose inline payload is not NUL-terminated exactly at i_size when the inode block is validated. This keeps malformed fast symlinks from reaching the read path.

Validation reproduced this kernel report: KASAN use-after-free in ocfs2_fast_symlink_read_folio+0x12c/0x1f0 RIP: 0033:0x7f5c6d859aa7 Read of size 3905 Call trace: dump_stack_lvl+0x66/0xa0 (?:?) print_report+0xce/0x630 (?:?) ocfs2_fast_symlink_read_folio+0x12c/0x1f0 (fs/ocfs2/inode.c:?) srso_alias_return_thunk+0x5/0xfbef5 (?:?) __virt_addr_valid+0x19f/0x330 (?:?) kasan_report+0xe0/0x110 (?:?) kasan_check_range+0x105/0x1b0 (?:?) __asan_memcpy+0x23/0x60 (?:?) filemap_read_folio+0x27/0xe0 (?:?) filemap_read_folio+0x35/0xe0 (?:?) do_read_cache_folio+0x138/0x230 (?:?) __page_get_link+0x26/0x110 (?:?) page_get_link+0x2e/0x70 (?:?) vfs_readlink+0x15e/0x250 (?:?) touch_atime+0x4d/0x370 (?:?) do_readlinkat+0x186/0x200 (?:?) do_user_addr_fault+0x65a/0x890 (?:?) __x64_sys_readlink+0x46/0x60 (?:?) do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f (?:?)

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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
Severity98% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track* or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
44th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Oct 5, 2026
Patch available.
generic

ocfs2: validate fast symlink target during inode read - kernel/git/stable/linux.git - Linux kernel stable tree

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

ocfs2: validate fast symlink target during inode read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e234973f286ed2e8961a24561ec91594ec3e3ff8

Vendor Advisories for CVE-2026-74350(1)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-34.34) @ resolute2026-10-05ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1014.14) @ resolute2026-10-05ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1012.12~24.04.1) @ noble2026-10-05ubuntu
ubuntulinux-tools-gke-hwe-26.04 (7.0.0-1007.8) @ resolute2026-10-05ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-05ubuntu

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 rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (181 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(5)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 53× in last 7d / 247× 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 403 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-74350?
CVE-2026-74350 is a critical vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ocfs2: validate fast symlink target during inode read ocfs2validateinode_block() already rejects several inconsistent self-contained dinodes before they are exposed to the rest of the filesystem. Fast symlinks need the same…
When was CVE-2026-74350 disclosed?
CVE-2026-74350 was first published on August 15, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74350 actively exploited?
CVE-2026-74350 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74350?
CVE-2026-74350 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74350?
A fix for CVE-2026-74350 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74350 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-74350?

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

Book a Demo →Browse All CVEs