CVE-2026-46052

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-32434 (ENISA EUVD) · GHSA-vjcv-x2xf-6m7h (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ceph: only d_add() negative dentries when they are unhashed

Ceph can call d_add(dentry, NULL) on a negative dentry that is already present in the primary dcache hash.

In the current VFS that is not safe. d_add() goes through __d_add() to __d_rehash(), which unconditionally reinserts dentry->d_hash into the hlist_bl bucket. If the dentry is already hashed, reinserting the same node can corrupt the bucket, including creating a self-loop. Once that happens, __d_lookup() can spin forever in the hlist_bl walk, typically looping only on the d_name.hash mismatch check and eventually triggering RCU stall reports like this one:

rcu: INFO: rcu_sched self-detected stall on CPU rcu: 87-....: (2100 ticks this GP) idle=3a4c/1/0x4000000000000000 softirq=25003319/25003319 fqs=829 rcu: (t=2101 jiffies g=79058445 q=698988 ncpus=192) CPU: 87 UID: 2952868916 PID: 3933303 Comm: php-cgi8.3 Not tainted 6.18.17-i1-amd #950 NONE Hardware name: Dell Inc. PowerEdge R7615/0G9DHV, BIOS 1.6.6 09/22/2023 RIP: 0010:__d_lookup+0x46/0xb0 Code: c1 e8 07 48 8d 04 c2 48 8b 00 49 89 fc 49 89 f5 48 89 c3 48 83 e3 fe 48 83 f8 01 77 0f eb 2d 0f 1f 44 00 00 48 8b 1b 48 85 db <74> 20 39 6b 18 75 f3 48 8d 7b 78 e8 ba 85 d0 00 4c 39 63 10 74 1f RSP: 0018:ff745a70c8253898 EFLAGS: 00000282 RAX: ff26e470054cb208 RBX: ff26e470054cb208 RCX: 000000006e958966 RDX: ff26e48267340000 RSI: ff745a70c82539b0 RDI: ff26e458f74655c0 RBP: 000000006e958966 R08: 0000000000000180 R09: 9cd08d909b919a89 R10: ff26e458f74655c0 R11: 0000000000000000 R12: ff26e458f74655c0 R13: ff745a70c82539b0 R14: d0d0d0d0d0d0d0d0 R15: 2f2f2f2f2f2f2f2f FS: 00007f5770896980(0000) GS:ff26e482c5d88000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f5764de50c0 CR3: 000000a72abb5001 CR4: 0000000000771ef0 PKRU: 55555554 Call Trace: lookup_fast+0x9f/0x100 walk_component+0x1f/0x150 link_path_walk+0x20e/0x3d0 path_lookupat+0x68/0x180 filename_lookup+0xdc/0x1e0 vfs_statx+0x6c/0x140 vfs_fstatat+0x67/0xa0 __do_sys_newfstatat+0x24/0x60 do_syscall_64+0x6a/0x230 entry_SYSCALL_64_after_hwframe+0x76/0x7e

This is reachable with reused cached negative dentries. A Ceph lookup or atomic_open can be handed a negative dentry that is already hashed, and fs/ceph/dir.c then hits one of two paths that incorrectly assume "negative" also means "unhashed":

  • ceph_finish_lookup():
MDS reply is -ENOENT with no trace -> d_add(dentry, NULL)
  • ceph_lookup():
local ENOENT fast path for a complete directory with shared caps -> d_add(dentry, NULL)

Both paths can therefore re-add an already-hashed negative dentry.

Ceph already uses the correct pattern elsewhere: ceph_fill_trace() only calls d_add(dn, NULL) for a negative null-dentry reply when d_unhashed(dn) is true.

Fix both fs/ceph/dir.c sites the same way: only call d_add() for a negative dentry when it is actually unhashed. If the negative dentry is already hashed, leave it in place and reuse it as-is.

This preserves the existing behavior for unhashed dentries while avoiding d_hash list corruption for reused hashed negatives.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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.5%
EPSS %ILE
42nd
KEV
Not listed

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

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; 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 (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

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

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

May 27, 2026

Last Modified

October 19, 2026

Advisory Details (5)

Auto-updated Jun 6, 2026
Patch available.
Web page

ceph: only d_add() negative dentries when they are unhashed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b91e535f208c48a5e7464f1aa38338a30e7912df
Web page

ceph: only d_add() negative dentries when they are unhashed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/83ce43a21bb7df8dd52228afdd918d2d058eefde
Web page

ceph: only d_add() negative dentries when they are unhashed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/803447f93d75ab6e40c85e6d12b5630d281d70d6
Web page

ceph: only d_add() negative dentries when they are unhashed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4179cc390dacebc87079419ec92f86f3dc46294d
Web page

ceph: only d_add() negative dentries when they are unhashed - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2010cb06b9df7d3c816c78358c566bdacbdf38ff

Vendor Advisories for CVE-2026-46052(2)

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

Patch Availability(27)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-10-27ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-10-27ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-27ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-10-27ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-10-27ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-27ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-27ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-10-27ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-10-27ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1122.131) @ jammy2026-10-27ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1063.71~22.04.1) @ jammy2026-10-27ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1112.112) @ jammy2026-10-27ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-27ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-10-27ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-10-27ubuntu
linuxKernel @ 5.10.259 (fixes >=2.6.34)—osv

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (54 versions)
  • every version up to 5.10.259-1: fixed in 5.10.259-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)
  • every version up to 6.1.176-1~deb11u1: fixed in 6.1.176-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)
  • every version up to 6.1.176-1: fixed in 6.1.176-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.86-1~bpo12+1 (19 versions)
  • every version up to 6.12.86-1: fixed in 6.12.86-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (135 versions)
  • every version up to 7.0.4-1: fixed in 7.0.4-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 49× 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.

Showing the most recent 100 of 346 refreshes on record for this CVE.

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. None are among the latest 100 rows. The 246 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)· as of October 29, 2026

Frequently asked(5)

What is CVE-2026-46052?
CVE-2026-46052 is a high-severity vulnerability; its CVE record was published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: ceph: only d_add() negative dentries when they are unhashed Ceph can call d_add(dentry, NULL) on a negative dentry that is already present in the primary dcache hash. In the current VFS that is not safe. dadd() goes through dadd()…
When was the CVE record for CVE-2026-46052 published?
The CVE record for CVE-2026-46052 was published on May 27, 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-46052 actively exploited?
CVE-2026-46052 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46052?
CVE-2026-46052 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46052?
A fix for CVE-2026-46052 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46052 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-46052

Explore →

Is Your Infrastructure Affected by CVE-2026-46052?

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

Book a Demo →Browse All CVEs