CVE-2024-35932

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-05-19. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-35650 (ENISA EUVD) · GHSA-mr27-h878-23c8 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

drm/vc4: don't check if plane->state->fb == state->fb

Currently, when using non-blocking commits, we can see the following kernel warning:

[ 110.908514] ------------[ cut here ]------------ [ 110.908529] refcount_t: underflow; use-after-free. [ 110.908620] WARNING: CPU: 0 PID: 1866 at lib/refcount.c:87 refcount_dec_not_one+0xb8/0xc0 [ 110.908664] Modules linked in: rfcomm snd_seq_dummy snd_hrtimer snd_seq snd_seq_device cmac algif_hash aes_arm64 aes_generic algif_skcipher af_alg bnep hid_logitech_hidpp vc4 brcmfmac hci_uart btbcm brcmutil bluetooth snd_soc_hdmi_codec cfg80211 cec drm_display_helper drm_dma_helper drm_kms_helper snd_soc_core snd_compress snd_pcm_dmaengine fb_sys_fops sysimgblt syscopyarea sysfillrect raspberrypi_hwmon ecdh_generic ecc rfkill libaes i2c_bcm2835 binfmt_misc joydev snd_bcm2835(C) bcm2835_codec(C) bcm2835_isp(C) v4l2_mem2mem videobuf2_dma_contig snd_pcm bcm2835_v4l2(C) raspberrypi_gpiomem bcm2835_mmal_vchiq(C) videobuf2_v4l2 snd_timer videobuf2_vmalloc videobuf2_memops videobuf2_common snd videodev vc_sm_cma(C) mc hid_logitech_dj uio_pdrv_genirq uio i2c_dev drm fuse dm_mod drm_panel_orientation_quirks backlight ip_tables x_tables ipv6 [ 110.909086] CPU: 0 PID: 1866 Comm: kodi.bin Tainted: G C 6.1.66-v8+ #32 [ 110.909104] Hardware name: Raspberry Pi 3 Model B Rev 1.2 (DT) [ 110.909114] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 110.909132] pc : refcount_dec_not_one+0xb8/0xc0 [ 110.909152] lr : refcount_dec_not_one+0xb4/0xc0 [ 110.909170] sp : ffffffc00913b9c0 [ 110.909177] x29: ffffffc00913b9c0 x28: 000000556969bbb0 x27: 000000556990df60 [ 110.909205] x26: 0000000000000002 x25: 0000000000000004 x24: ffffff8004448480 [ 110.909230] x23: ffffff800570b500 x22: ffffff802e03a7bc x21: ffffffecfca68c78 [ 110.909257] x20: ffffff8002b42000 x19: ffffff802e03a600 x18: 0000000000000000 [ 110.909283] x17: 0000000000000011 x16: ffffffffffffffff x15: 0000000000000004 [ 110.909308] x14: 0000000000000fff x13: ffffffed577e47e0 x12: 0000000000000003 [ 110.909333] x11: 0000000000000000 x10: 0000000000000027 x9 : c912d0d083728c00 [ 110.909359] x8 : c912d0d083728c00 x7 : 65646e75203a745f x6 : 746e756f63666572 [ 110.909384] x5 : ffffffed579f62ee x4 : ffffffed579eb01e x3 : 0000000000000000 [ 110.909409] x2 : 0000000000000000 x1 : ffffffc00913b750 x0 : 0000000000000001 [ 110.909434] Call trace: [ 110.909441] refcount_dec_not_one+0xb8/0xc0 [ 110.909461] vc4_bo_dec_usecnt+0x4c/0x1b0 [vc4] [ 110.909903] vc4_cleanup_fb+0x44/0x50 [vc4] [ 110.910315] drm_atomic_helper_cleanup_planes+0x88/0xa4 [drm_kms_helper] [ 110.910669] vc4_atomic_commit_tail+0x390/0x9dc [vc4] [ 110.911079] commit_tail+0xb0/0x164 [drm_kms_helper] [ 110.911397] drm_atomic_helper_commit+0x1d0/0x1f0 [drm_kms_helper] [ 110.911716] drm_atomic_commit+0xb0/0xdc [drm] [ 110.912569] drm_mode_atomic_ioctl+0x348/0x4b8 [drm] [ 110.913330] drm_ioctl_kernel+0xec/0x15c [drm] [ 110.914091] drm_ioctl+0x24c/0x3b0 [drm] [ 110.914850] __arm64_sys_ioctl+0x9c/0xd4 [ 110.914873] invoke_syscall+0x4c/0x114 [ 110.914897] el0_svc_common+0xd0/0x118 [ 110.914917] do_el0_svc+0x38/0xd0 [ 110.914936] el0_svc+0x30/0x8c [ 110.914958] el0t_64_sync_handler+0x84/0xf0 [ 110.914979] el0t_64_sync+0x18c/0x190 [ 110.914996] ---[ end trace 0000000000000000 ]---

This happens because, although prepare_fb and cleanup_fb are perfectly balanced, we cannot guarantee consistency in the check plane->state->fb == state->fb. This means that sometimes we can increase the refcount in prepare_fb and don't decrease it in cleanup_fb. The opposite can also be true.

In fact, the struct drm_plane .state shouldn't be accessed directly but instead, the drm_atomic_get_new_plane_state() helper function should be used. So, we could stick to this check, but using drm_atomic_get_new_plane_state(). But actually, this check is not re ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.2%
EPSS %ILE
11th
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.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% 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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 19, 2024

Last Modified

August 5, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
Patch available.
Web page

drm/vc4: don't check if plane->state->fb == state->fb - kernel/git/stable/linux.git - Linux kernel stable tree

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

drm/vc4: don't check if plane->state->fb == state->fb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5ee0d47dcf33efd8950b347dcf4d20bab12a3fa9
Web page

drm/vc4: don't check if plane->state->fb == state->fb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5343f724c912c77541029123f47ecd3d2ea63bdd
Web page

drm/vc4: don't check if plane->state->fb == state->fb - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/48bfb4b03c5ff6e1fa1dc73fb915e150b0968c40

Vendor Advisories for CVE-2024-35932(1)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-64k (6.8.0-1009.9) @ noble2026-10-28ubuntu
ubuntulinux-tools-aws (6.8.0-1011.12) @ noble2026-10-28ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1008.8) @ noble2026-10-28ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-38.38) @ noble2026-10-28ubuntu
linuxKernel @ 6.1.86 (fixes >=4.15.0)—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (498 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.90-1~bpo11+1 (21 versions)
  • every version up to 6.1.90-1: fixed in 6.1.90-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

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 10× in last 7d / 42× 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 96 of 221 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 125 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-35932?
CVE-2024-35932 is a high-severity vulnerability; its CVE record was published on May 19, 2024. In the Linux kernel, the following vulnerability has been resolved: drm/vc4: don't check if plane->state->fb == state->fb Currently, when using non-blocking commits, we can see the following kernel warning: [ 110.908514] ------------[ cut here ]------------ [ 110.908529] refcount_t: underflow;…
When was the CVE record for CVE-2024-35932 published?
The CVE record for CVE-2024-35932 was published on May 19, 2024. 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-35932 actively exploited?
CVE-2024-35932 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-35932?
CVE-2024-35932 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-35932?
A fix for CVE-2024-35932 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-35932 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-2024-35932

Explore →

Is Your Infrastructure Affected by CVE-2024-35932?

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

Book a Demo →Browse All CVEs