CVE-2026-46106

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

eventfs: Hold eventfs_mutex and SRCU when remount walks events

Commit 340f0c7067a9 ("eventfs: Update all the eventfs_inodes from the events descriptor") had eventfs_set_attrs() recurse through ei->children on remount. The walk only holds the rcu_read_lock() taken by tracefs_apply_options() over tracefs_inodes, which is wrong:

  • list_for_each_entry over ei->children races with the list_del_rcu()
in eventfs_remove_rec() -- LIST_POISON1 deref, same shape as d2603279c7d6.
  • eventfs_inodes are freed via call_srcu(&eventfs_srcu, ...).
rcu_read_lock() does not extend an SRCU grace period, so ti->private can be reclaimed under the walk.
  • The writes to ei->attr race with eventfs_set_attr(), which holds
eventfs_mutex.

Reproducer:

while :; do mount -o remount,uid=$((RANDOM%1000)) /sys/kernel/tracing; done & while :; do echo "p:kp submit_bio" > /sys/kernel/tracing/kprobe_events echo > /sys/kernel/tracing/kprobe_events done

Wrap the events portion of tracefs_apply_options() in eventfs_remount_lock()/_unlock() that take eventfs_mutex and srcu_read_lock(&eventfs_srcu). eventfs_set_attrs() doesn't sleep so the nested rcu_read_lock() is fine; lockdep_assert_held() pins the contract.

Comment in tracefs_drop_inode() said "RCU cycle" -- it is SRCU.

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

Published

May 28, 2026

Last Modified

June 25, 2026

Advisory Details (5)

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

eventfs: Hold eventfs_mutex and SRCU when remount walks events - kernel/git/stable/linux.git - Linux kernel stable tree

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

eventfs: Hold eventfs_mutex and SRCU when remount walks events - kernel/git/stable/linux.git - Linux kernel stable tree

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

eventfs: Hold eventfs_mutex and SRCU when remount walks events - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52b109f1b875b912d4ab2c5fdd8c322d47119d9b
generic

eventfs: Hold eventfs_mutex and SRCU when remount walks events - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/44e64d8a432837308f4dda3ffe819f1ec092a0ba
generic

eventfs: Hold eventfs_mutex and SRCU when remount walks events - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07004a8c4b572171934390148ee48c4175c77eed

Vendor Advisories for CVE-2026-46106(2)

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

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-136.136.2~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-25ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-25ubuntu

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.88-1~bpo12+1 (21 versions)6.12.88-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (133 versions)7.0.7-1

Additional Vendor Advisories

(22)

Data Freshness Timeline

(refreshed 4× in last 7d / 63× 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 194 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46106?
CVE-2026-46106 is a medium vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: eventfs: Hold eventfs_mutex and SRCU when remount walks events Commit 340f0c7067a9 ("eventfs: Update all the eventfs_inodes from the events descriptor") had eventfssetattrs() recurse through ei->children on remount. The walk only…
When was CVE-2026-46106 disclosed?
CVE-2026-46106 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46106 actively exploited?
CVE-2026-46106 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-46106?
CVE-2026-46106 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46106?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46106, 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-46106

Explore →

Is Your Infrastructure Affected by CVE-2026-46106?

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