CVE-2026-46190

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 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:

mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show()

Sashiko noticed an out-of-bounds read [1].

In spi_nor_params_show(), the snor_f_names array is passed to spi_nor_print_flags() using sizeof(snor_f_names).

Since snor_f_names is an array of pointers, sizeof() returns the total number of bytes occupied by the pointers (element_count * sizeof(void *)) rather than the element count itself. On 64-bit systems, this makes the passed length 8x larger than intended.

Inside spi_nor_print_flags(), the 'names_len' argument is used to bounds-check the 'names' array access. An out-of-bounds read occurs if a flag bit is set that exceeds the array's actual element count but is within the inflated byte-size count.

Correct this by using ARRAY_SIZE() to pass the actual number of string pointers in the array.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
3.1%
KEV
Not listed

Published

May 28, 2026

Last Modified

June 19, 2026

Advisory Details (5)

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

mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show() - kernel/git/stable/linux.git - Linux kernel stable tree

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

mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a80c458320e0514e11945402dd6e48fcee05524
generic

mtd: spi-nor: debugfs: fix out-of-bounds read in spi_nor_params_show() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/34bdcfb496b29f9a52431194f94473b37fb8c162

Vendor Advisories for CVE-2026-46190(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 13× in last 7d / 91× 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 202 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-46190?
CVE-2026-46190 is a high vulnerability published on May 28, 2026. In the Linux kernel, the following vulnerability has been resolved: mtd: spi-nor: debugfs: fix out-of-bounds read in spinorparams_show() Sashiko noticed an out-of-bounds read [1]. In spinorparamsshow(), the snorf_names array is passed to spinorprintflags() using sizeof(snorf_names). Since…
When was CVE-2026-46190 disclosed?
CVE-2026-46190 was first published in the National Vulnerability Database on May 28, 2026, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46190 actively exploited?
CVE-2026-46190 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46190?
CVE-2026-46190 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-46190?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46190, 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-46190

Explore →

Is Your Infrastructure Affected by CVE-2026-46190?

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