CVE-2026-52906

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-06-09. the CNA's CVSS baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
Trending — 4 sources updated this week
7.7EG
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.7Exploit: None knownExposed: 0

A fix is available — apply it.

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

9p: fix access mode flags being ORed instead of replaced

Since commit 1f3e4142c0eb ("9p: convert to the new mount API"), v9fs_apply_options() applies parsed mount flags with |= onto flags already set by v9fs_session_init(). For 9P2000.L, session_init sets V9FS_ACCESS_CLIENT as the default, so when the user mounts with "access=user", both bits end up set. Access mode checks compare against exact values, so having both bits set matches neither mode.

This causes v9fs_fid_lookup() to fall through to the default switch case, using INVALID_UID (nobody/65534) instead of current_fsuid() for all fid lookups. Root is then unable to chown or perform other privileged operations.

Fix by clearing the access mask before applying the user's choice.

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

Published

June 9, 2026

Last Modified

August 5, 2026

Advisory Details (2)

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

9p: fix access mode flags being ORed instead of replaced - kernel/git/stable/linux.git - Linux kernel stable tree

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

9p: fix access mode flags being ORed instead of replaced - kernel/git/stable/linux.git - Linux kernel stable tree

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

Vendor Advisories for CVE-2026-52906(1)

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-09-14ubuntu

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (134 versions)7.0.4-1—

All Vendor Advisories

(6)

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 7× in last 7d / 47× 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 285 total refreshes for this CVE.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-52906?
CVE-2026-52906 is a high vulnerability published on June 9, 2026. In the Linux kernel, the following vulnerability has been resolved: 9p: fix access mode flags being ORed instead of replaced Since commit 1f3e4142c0eb ("9p: convert to the new mount API"), v9fsapplyoptions() applies parsed mount flags with |= onto flags already set by v9fssessioninit(). For…
When was CVE-2026-52906 disclosed?
CVE-2026-52906 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52906 actively exploited?
CVE-2026-52906 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.9% of all scored CVEs.
What is the CVSS score of CVE-2026-52906?
CVE-2026-52906 has a CVSS v4.0 base score of 7.7 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-52906?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52906, 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-52906

Explore →

Is Your Infrastructure Affected by CVE-2026-52906?

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

Start Free Scan →Browse All CVEs