CVE-2026-74351

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ocfs2: rebase copied fsdlm LVB pointers in locking_state

The locking_state debugfs iterator snapshots struct ocfs2_lock_res by value under ocfs2_dlm_tracking_lock and later formats that copy in ocfs2_dlm_seq_show(). That is fine for the inline fields, but the userspace fsdlm stack stores the LVB through lksb_fsdlm.sb_lvbptr. Once the iterator drops the tracking lock, a copied non-NULL sb_lvbptr still points into the original lockres owner, so teardown can free that container before the debugfs dump walks the raw LVB bytes.

Rebase the copied sb_lvbptr to the copied l_lksb before dumping the raw LVB. The seq snapshot already carries the inline LVB storage reserved in struct ocfs2_dlm_lksb, so the debugfs reader can dump the copied bytes without borrowing the original lockres lifetime.

The buggy scenario involves two paths, with each column showing the order within that path:

locking_state reader: lockres teardown:

  • ocfs2_dlm_seq_start()/next() 1. file release or another owner
copies struct ocfs2_lock_res teardown reaches
  • ocfs2_dlm_seq_show() formats ocfs2_lock_res_free()
the copied row 2. the lockres is removed from the
  • ocfs2_dlm_lvb() follows the tracking list
copied sb_lvbptr 3. the owner frees the original lockres container

Validation reproduced this kernel report: KASAN slab-use-after-free in ocfs2_dlm_seq_show+0x1bd/0x430 RIP: 0033:0x7f8ec4b1e29d The buggy address belongs to the object at ffff88810a1e0800 which belongs to the cache kmalloc-1k of size 1024 The buggy address is located 368 bytes inside of freed 1024-byte region [ffff88810a1e0800, ffff88810a1e0c00) Read of size 1 Call trace: dump_stack_lvl+0x66/0xa0 print_report+0xce/0x630 ocfs2_dlm_seq_show+0x1bd/0x430 (fs/ocfs2/dlmglue.c:3137) srso_alias_return_thunk+0x5/0xfbef5 __virt_addr_valid+0x19f/0x330 kasan_report+0xe0/0x110 seq_read_iter+0x29d/0x790 seq_read+0x20a/0x280 find_held_lock+0x2b/0x80 rcu_read_unlock+0x18/0x70 full_proxy_read+0x9e/0xd0 vfs_read+0x12c/0x590 ksys_read+0xd2/0x170 do_user_addr_fault+0x65a/0x890 do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f Allocated by task stack: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 __kasan_kmalloc+0xaa/0xb0 ocfs2_file_open+0x13e/0x300 do_dentry_open+0x233/0x7f0 vfs_open+0x5a/0x1b0 path_openat+0x66d/0x1540 do_file_open+0x186/0x2b0 do_sys_openat2+0xce/0x150 __x64_sys_openat+0xd0/0x140 do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f Freed by task stack: kasan_save_stack+0x33/0x60 kasan_save_track+0x14/0x30 kasan_save_free_info+0x3b/0x60 __kasan_slab_free+0x5f/0x80 kfree+0x313/0x590 ocfs2_file_release+0x138/0x260 __fput+0x1df/0x4b0 fput_close_sync+0xd2/0x170 __x64_sys_close+0x55/0x90 do_syscall_64+0x115/0x6a0 (arch/x86/entry/syscall_64.c:87) entry_SYSCALL_64_after_hwframe+0x77/0x7f

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 15, 2026

Last Modified

August 17, 2026

References (8)

Vendor Advisories for CVE-2026-74351(1)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
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
—

Data Freshness Timeline

(refreshed 8× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 87 are merged into the row they repeat.

  1. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-18 03:14 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-12 15:40 UTCEG score recompute
  11. 2026-10-11 19:26 UTCEG score recompute
  12. 2026-10-11 16:41 UTCEG score recompute
  13. 2026-10-11 14:00 UTCEG score recompute
  14. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-10-04 13:45 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  23. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-10-01 10:01 UTCEG score recompute
Show 58 more
  1. 2026-10-01 10:01 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  2. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-09-28 06:17 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  5. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-09-25 02:33 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  9. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-09-21 20:37 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  13. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-09-18 16:51 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  16. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-09-15 11:56 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  19. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-09-12 07:53 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  22. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-09-09 03:57 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  25. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  26. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  27. 2026-09-05 05:41 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  28. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  29. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  30. 2026-09-02 01:56 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  31. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  32. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  33. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  34. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  35. 2026-08-29 22:12 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  36. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  37. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  38. 2026-08-26 18:28 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  39. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  40. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  41. 2026-08-24 14:18 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  42. 2026-08-23 13:54 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  43. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  44. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  45. 2026-08-20 10:10 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  46. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  47. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  48. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  49. 2026-08-17 06:26 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  50. 2026-08-17 06:22 UTCNVD update
  51. 2026-08-17 05:26 UTCEG score recompute
  52. 2026-08-17 05:26 UTCGHSA enrichmentGHSA-277m-9mg9-wh9q
  53. 2026-08-17 05:24 UTCMITRE cvelistV5
  54. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  55. 2026-08-16 02:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  56. 2026-08-15 06:23 UTCNVD update
  57. 2026-08-15 06:15 UTCEG score recompute
  58. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-74351?
CVE-2026-74351 is a vulnerability whose severity is not yet rated; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: ocfs2: rebase copied fsdlm LVB pointers in locking_state The lockingstate debugfs iterator snapshots struct ocfs2lock_res by value under ocfs2dlmtracking_lock and later formats that copy in ocfs2dlmseq_show(). That is fine for the…
When was the CVE record for CVE-2026-74351 published?
The CVE record for CVE-2026-74351 was published on August 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 17, 2026; the record at its source may have been updated since.
Is CVE-2026-74351 actively exploited?
CVE-2026-74351 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-74351?
A fix for CVE-2026-74351 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74351 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-74351

Explore →

Is Your Infrastructure Affected by CVE-2026-74351?

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

Book a Demo →Browse All CVEs