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, ghsa
Trending — 4 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 v2: —Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.5(low)
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
1%
KEV
Not listed

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 38× 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 107 total refreshes for this CVE.

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

Frequently asked(4)

What is CVE-2026-46156?
CVE-2026-46156 is a medium vulnerability 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 CVE-2026-46156 disclosed?
CVE-2026-46156 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46156 actively exploited?
CVE-2026-46156 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 99.2% of all scored CVEs.
How do I remediate CVE-2026-46156?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46156, 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs