CVE-2026-46156

MEDIUMCVSS · not yet scored5.5
EchelonGraph scoreLOW confidence

Score 5.5 from GitHub Security Advisory published 2026-05-28.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory
5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

LoongArch: Fix potential ADE in loongson_gpu_fixup_dma_hang()

The switch case in loongson_gpu_fixup_dma_hang() may not DC2 or DC3, and readl(crtc_reg) will access with random address, because the "device" is from "base+PCI_DEVICE_ID", "base" is from "pdev->devfn+1". This is wrong when my platform inserts a discrete GPU:

lspci -tv -[0000:00]-+-00.0 Loongson Technology LLC Hyper Transport Bridge Controller ... +-06.0 Loongson Technology LLC LG100 GPU +-06.2 Loongson Technology LLC Device 7a37 ...

Add a default switch case to fix the panic as below:

Kernel ade access[#1]: CPU: 0 PID: 1 Comm: swapper/0 Not tainted 6.6.136-loong64-desktop-hwe+ #4 pc 90000000017e5534 ra 90000000017e54c0 tp 90000001002f8000 sp 90000001002fb6c0 a0 80000efe00003100 a1 0000000000003100 a2 0000000000000000 a3 0000000000000002 a4 90000001002fb6b4 a5 900000087cdb58fd a6 90000000027af000 a7 0000000000000001 t0 00000000000085b9 t1 000000000000ffff t2 0000000000000000 t3 0000000000000000 t4 fffffffffffffffd t5 00000000fffb6d9c t6 0000000000083b00 t7 00000000000070c0 t8 900000087cdb4d94 u0 900000087cdb58fd s9 90000001002fb826 s0 90000000031c12c8 s1 7fffffffffffff00 s2 90000000031c12d0 s3 0000000000002710 s4 0000000000000000 s5 0000000000000000 s6 9000000100053000 s7 7fffffffffffff00 s8 90000000030d4000 ra: 90000000017e54c0 loongson_gpu_fixup_dma_hang+0x40/0x210 ERA: 90000000017e5534 loongson_gpu_fixup_dma_hang+0xb4/0x210 CRMD: 000000b0 (PLV0 -IE -DA +PG DACF=CC DACM=CC -WE) PRMD: 00000004 (PPLV0 +PIE -PWE) EUEN: 00000000 (-FPE -SXE -ASXE -BTE) ECFG: 00071c1d (LIE=0,2-4,10-12 VS=7) ESTAT: 00480000 [ADEM] (IS= ECode=8 EsubCode=1) BADV: 7fffffffffffff00 PRID: 0014d000 (Loongson-64bit, Loongson-3A6000-HV) Modules linked in: Process swapper/0 (pid: 1, threadinfo=(____ptrval____), task=(____ptrval____)) Stack : 0000000000000006 90000001002fb778 90000001002fb704 0000000000000007 0000000016a65700 90000000017e5690 000000000000ffff ffffffffffffffff 900000000209f7c0 9000000100053000 900000000209f7a8 9000000000eebc08 0000000000000000 0000000000000000 0000000000000006 90000001002fb778 90000001000530b8 90000000027af000 0000000000000000 9000000100054000 9000000100053000 9000000000ebb70c 9000000100004c00 9000000004000001 90000001002fb7e4 bae765461f31cb12 0000000000000000 0000000000000000 0000000000000006 90000000027af000 0000000000000030 90000000027af000 900000087cd6f800 9000000100053000 0000000000000000 9000000000ebc560 7a2500147cdaf720 bae765461f31cb12 0000000000000001 0000000000000030 ... Call Trace: [<90000000017e5534>] loongson_gpu_fixup_dma_hang+0xb4/0x210 [<9000000000eebc08>] pci_fixup_device+0x108/0x280 [<9000000000ebb70c>] pci_setup_device+0x24c/0x690 [<9000000000ebc560>] pci_scan_single_device+0xe0/0x140 [<9000000000ebc684>] pci_scan_slot+0xc4/0x280 [<9000000000ebdd00>] pci_scan_child_bus_extend+0x60/0x3f0 [<9000000000f5bc94>] acpi_pci_root_create+0x2b4/0x420 [<90000000017e5e74>] pci_acpi_scan_root+0x2d4/0x440 [<9000000000f5b02c>] acpi_pci_root_add+0x21c/0x3a0 [<9000000000f4ee54>] acpi_bus_attach+0x1a4/0x3c0 [<90000000010e200c>] device_for_each_child+0x6c/0xe0 [<9000000000f4bbf4>] acpi_dev_for_each_child+0x44/0x70 [<9000000000f4ef40>] acpi_bus_attach+0x290/0x3c0 [<90000000010e200c>] device_for_each_child+0x6c/0xe0 [<9000000000f4bbf4>] acpi_dev_for_each_child+0x44/0x70 [<9000000000f4ef40>] acpi_bus_attach+0x290/0x3c0 [<9000000000f5211c>] acpi_bus_scan+0x6c/0x280 [<900000000189c028>] acpi_scan_init+0x194/0x310 [<900000000189bc6c>] acpi_init+0xcc/0x140 [<9000000000220cdc>] do_one_initcall+0x4c/0x310 [<90000000018618fc>] kernel_init_freeable+0x258/0x2d4 [<900000000184326c>] kernel_init+0x28/0x13c [<9000000000222008>] ret_from_kernel_thread+0xc/0xa4

CVSS v3
—
EG Score
5.5MEDIUMlow confidence
EG Risk
25
EG Risk 25/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)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.1%
EPSS %ILE
2nd
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 (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). 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; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

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

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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 28, 2026

Last Modified

June 14, 2026

References (6)

Vendor Advisories for CVE-2026-46156(2)

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

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-14ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-14ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-14ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-14ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-14ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-14ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-14ubuntu
linuxKernel @ 6.1.175 (fixes >=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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (358 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.88-1~bpo12+1 (21 versions)
  • every version up to 6.12.88-1: fixed in 6.12.88-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.7-1~bpo13+1 (137 versions)
  • every version up to 7.0.7-1: fixed in 7.0.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(9)

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 7× in last 7d / 27× 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 238 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 138 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2026-46156?
CVE-2026-46156 is a medium-severity vulnerability; its CVE record was published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: LoongArch: Fix potential ADE in loongsongpufixupdmahang() The switch case in loongsongpufixupdmahang() may not DC2 or DC3, and readl(crtc_reg) will access with random address, because the "device" is from "base+PCIDEVICEID", "base"…
When was the CVE record for CVE-2026-46156 published?
The CVE record for CVE-2026-46156 was published on May 28, 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 June 14, 2026; the record at its source may have been updated since.
Is CVE-2026-46156 actively exploited?
CVE-2026-46156 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-46156?
A fix for CVE-2026-46156 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46156 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-46156

Explore →

Is Your Infrastructure Affected by CVE-2026-46156?

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

Book a Demo →Browse All CVEs