CVE-2026-46247

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
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:

clk: qcom: gfx3d: add parent to parent request map

After commit d228ece36345 ("clk: divider: remove round_rate() in favor of determine_rate()") determining GFX3D clock rate crashes, because the passed parent map doesn't provide the expected best_parent_hw clock (with the roundd_rate path before the offending commit the best_parent_hw was ignored).

Set the field in parent_req in addition to setting it in the req, fixing the crash.

clk_hw_round_rate (drivers/clk/clk.c:1764) (P) clk_divider_bestdiv (drivers/clk/clk-divider.c:336) divider_determine_rate (drivers/clk/clk-divider.c:358) clk_alpha_pll_postdiv_determine_rate (drivers/clk/qcom/clk-alpha-pll.c:1275) clk_core_determine_round_nolock (drivers/clk/clk.c:1606) clk_core_round_rate_nolock (drivers/clk/clk.c:1701) __clk_determine_rate (drivers/clk/clk.c:1741) clk_gfx3d_determine_rate (drivers/clk/qcom/clk-rcg2.c:1268) clk_core_determine_round_nolock (drivers/clk/clk.c:1606) clk_core_round_rate_nolock (drivers/clk/clk.c:1701) clk_core_round_rate_nolock (drivers/clk/clk.c:1710) clk_round_rate (drivers/clk/clk.c:1804) dev_pm_opp_set_rate (drivers/opp/core.c:1440 (discriminator 1)) msm_devfreq_target (drivers/gpu/drm/msm/msm_gpu_devfreq.c:51) devfreq_set_target (drivers/devfreq/devfreq.c:360) devfreq_update_target (drivers/devfreq/devfreq.c:426) devfreq_monitor (drivers/devfreq/devfreq.c:458) process_one_work (arch/arm64/include/asm/jump_label.h:36 include/trace/events/workqueue.h:110 kernel/workqueue.c:3284) worker_thread (kernel/workqueue.c:3356 (discriminator 2) kernel/workqueue.c:3443 (discriminator 2)) kthread (kernel/kthread.c:467) ret_from_fork (arch/arm64/kernel/entry.S:861)

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

June 3, 2026

Last Modified

July 22, 2026

Advisory Details (6)

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

clk: qcom: gfx3d: add parent to parent request map - kernel/git/stable/linux.git - Linux kernel stable tree

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

clk: qcom: gfx3d: add parent to parent request map - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8aa972eba1f29068d13bec716d33abca30fb3f2a
generic

clk: qcom: gfx3d: add parent to parent request map - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/82cfe5292b11deb1dc33822f67f73cfbe8eafe25
generic

clk: qcom: gfx3d: add parent to parent request map - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/56360aa4ddd736fc19e6d0b0206c5e437e0d6ff8
generic

clk: qcom: gfx3d: add parent to parent request map - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/547ae2f17349c7586953af5ef50de43ef3f65e9e
generic

clk: qcom: gfx3d: add parent to parent request map - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2583cb925ca1ce450aa5d74a05a67448db970193

Vendor Advisories for CVE-2026-46247(1)

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

Patch Availability(13)

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)6.1.170-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (103 versions)6.18.14-1

All Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 9× in last 7d / 37× 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 212 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46247?
CVE-2026-46247 is a medium vulnerability published on June 3, 2026. In the Linux kernel, the following vulnerability has been resolved: clk: qcom: gfx3d: add parent to parent request map After commit d228ece36345 ("clk: divider: remove round_rate() in favor of determine_rate()") determining GFX3D clock rate crashes, because the passed parent map doesn't provide the…
When was CVE-2026-46247 disclosed?
CVE-2026-46247 was first published in the National Vulnerability Database on June 3, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46247 actively exploited?
CVE-2026-46247 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-46247?
CVE-2026-46247 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-46247?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46247, 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-46247

Explore →

Is Your Infrastructure Affected by CVE-2026-46247?

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