CVE-2026-43380

HIGHNVD 7.87.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-08. NVD baseline CVSS 7.8; sources differ by 0.7.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: 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:

hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read

The q54sj108a2_debugfs_read function suffers from a stack buffer overflow due to incorrect arguments passed to bin2hex(). The function currently passes 'data' as the destination and 'data_char' as the source.

Because bin2hex() converts each input byte into two hex characters, a 32-byte block read results in 64 bytes of output. Since 'data' is only 34 bytes (I2C_SMBUS_BLOCK_MAX + 2), this writes 30 bytes past the end of the buffer onto the stack.

Additionally, the arguments were swapped: it was reading from the zero-initialized 'data_char' and writing to 'data', resulting in all-zero output regardless of the actual I2C read.

Fix this by:

  • Expanding 'data_char' to 66 bytes to safely hold the hex output.
  • Correcting the bin2hex() argument order and using the actual read count.
  • Using a pointer to select the correct output buffer for the final
simple_read_from_buffer call.

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

Published

May 8, 2026

Last Modified

May 20, 2026

Advisory Details (7)

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

hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read - kernel/git/stable/linux.git - Linux kernel stable tree

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

hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/73a7a345816946d276ad2c46c8bb771de67cfc46
generic

hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/52db5ef163c96f916d424e472fb17aadc35a9f7a
generic

hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/25dd70a03b1f5f3aa71e1a5091ecd9cd2a13ee43
generic

hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/24a7b9daa103fa963b3fd37d8805b23e01621976

Vendor Advisories for CVE-2026-43380(1)

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 7× in last 7d / 40× 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 135 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-43380?
CVE-2026-43380 is a high vulnerability published on May 8, 2026. In the Linux kernel, the following vulnerability has been resolved: hwmon: (pmbus/q54sj108a2) fix stack overflow in debugfs read The q54sj108a2debugfsread function suffers from a stack buffer overflow due to incorrect arguments passed to bin2hex(). The function currently passes 'data' as the…
When was CVE-2026-43380 disclosed?
CVE-2026-43380 was first published in the National Vulnerability Database on May 8, 2026, with the most recent update on May 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43380 actively exploited?
CVE-2026-43380 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-43380?
CVE-2026-43380 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.1.
How do I remediate CVE-2026-43380?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43380, 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-43380

Explore →

Is Your Infrastructure Affected by CVE-2026-43380?

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