CVE-2026-74343

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this week
7.8EG
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.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

kernfs: fix xattr race condition with multiple superblocks

Multiple superblocks with different namespaces can share the same kernfs_node when kernfs_test_super() finds a matching root but different namespace. This means multiple inodes from different superblocks can reference the same kernfs_node->iattr->xattrs structure.

The VFS layer only holds per-inode locks during xattr operations, which is insufficient to serialize concurrent xattr modifications on the shared kernfs_node. This can lead to race conditions in simple_xattr_set() where the lookup->replace/remove sequence is not atomic with respect to operations from other superblocks.

Fix this by protecting xattr operations with the existing hashed kernfs_locks->open_file_mutex[] array, which is already used to protect per-node open file data. The hashed mutex array provides scalable per-node serialization (scaled by CPU count, up to 1024 locks on 32+ CPU systems) with zero memory overhead.

Changes:

  • Rename open_file_mutex[] to node_mutex[] to reflect dual purpose
  • Add kernfs_node_lock_ptr() and kernfs_node_lock() helpers
  • Protect simple_xattr_set() calls in kernfs_xattr_set() and
kernfs_vfs_user_xattr_set() with the hashed mutex
  • Update file.c to use new helpers via compatibility wrappers
  • Update documentation to explain the extended lock usage

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

Published

August 15, 2026

Last Modified

August 17, 2026

Advisory Details (2)

Auto-updated Aug 17, 2026
No patch confirmed yet.
generic

kernfs: fix xattr race condition with multiple superblocks - kernel/git/stable/linux.git - Linux kernel stable tree

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

kernfs: fix xattr race condition with multiple superblocks - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6a07814ff643b5c8e1353d8c6229f52fde205cde

Vendor Advisories for CVE-2026-74343(1)

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

Data Freshness Timeline

(refreshed 31× in last 7d / 31× 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-08-20 23:21 UTCEG score recompute
  2. 2026-08-20 23:21 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 12:15 UTCGHSA enrichment
  5. 2026-08-20 01:09 UTCEG score recompute
  6. 2026-08-20 01:09 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 14:02 UTCGHSA enrichment
  9. 2026-08-19 02:54 UTCGHSA enrichment
  10. 2026-08-18 15:47 UTCEG score recompute
  11. 2026-08-18 15:47 UTCGHSA enrichment
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 13:49 UTCEPSS rescore
  14. 2026-08-18 04:40 UTCGHSA enrichment
  15. 2026-08-17 17:33 UTCEG score recompute
  16. 2026-08-17 17:33 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 06:26 UTCEG score recompute
  19. 2026-08-17 06:26 UTCGHSA enrichment
  20. 2026-08-17 05:56 UTCEG score recompute▲ 7.80
  21. 2026-08-17 05:56 UTCGHSA enrichment
  22. 2026-08-17 05:54 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  23. 2026-08-17 05:26 UTCEG score recompute
  24. 2026-08-17 05:26 UTCGHSA enrichment
  25. 2026-08-17 05:25 UTCMITRE cvelistV5
Show 6 more
  1. 2026-08-16 14:56 UTCEPSS rescore
  2. 2026-08-16 14:56 UTCEPSS rescore
  3. 2026-08-16 02:15 UTCEPSS rescore
  4. 2026-08-15 06:23 UTCNVD update
  5. 2026-08-15 06:15 UTCEG score recompute
  6. 2026-08-15 06:12 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-74343?
CVE-2026-74343 is a high vulnerability published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: kernfs: fix xattr race condition with multiple superblocks Multiple superblocks with different namespaces can share the same kernfsnode when kernfstest_super() finds a matching root but different namespace. This means multiple…
When was CVE-2026-74343 disclosed?
CVE-2026-74343 was first published in the National Vulnerability Database 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-74343 actively exploited?
CVE-2026-74343 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-74343?
CVE-2026-74343 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-74343?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74343, 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-74343

Explore →

Is Your Infrastructure Affected by CVE-2026-74343?

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

Start Free Scan →Browse All CVEs