CVE-2026-53307

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-26. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
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: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

pinctrl: pinconf-generic: Fully validate 'pinmux' property

The pinconf_generic_parse_dt_pinmux() assumes that the 'pinmux' property is not empty when present. This might be not true. With that, the allocator will give a special value in return and not NULL which lead to the crash when trying to access that (invalid) memory. Fix that by fully validating 'pinmux' value, including its length.

CVSS v3
5.5
EG Score
5.5(medium)
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
2%
KEV
Not listed

Published

June 26, 2026

Last Modified

July 6, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

pinctrl: pinconf-generic: Fully validate 'pinmux' property - kernel/git/stable/linux.git - Linux kernel stable tree

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

pinctrl: pinconf-generic: Fully validate 'pinmux' property - kernel/git/stable/linux.git - Linux kernel stable tree

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

pinctrl: pinconf-generic: Fully validate 'pinmux' property - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6476aac13805721e16439bd71f0e1703a4154517

Vendor Advisories for CVE-2026-53307(1)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-09-06ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-09-06ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-09-06ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-09-06ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-09-06ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-09-06ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-09-06ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-09-06ubuntu

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1—

Weakness Classification(1)

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

All Vendor Advisories

(8)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 66× 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 181 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53307?
CVE-2026-53307 is a medium vulnerability published on June 26, 2026. In the Linux kernel, the following vulnerability has been resolved: pinctrl: pinconf-generic: Fully validate 'pinmux' property The pinconfgenericparsedtpinmux() assumes that the 'pinmux' property is not empty when present. This might be not true. With that, the allocator will give a special value…
When was CVE-2026-53307 disclosed?
CVE-2026-53307 was first published in the National Vulnerability Database on June 26, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53307 actively exploited?
CVE-2026-53307 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 98.4% of all scored CVEs.
What is the CVSS score of CVE-2026-53307?
CVE-2026-53307 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53307?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53307, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53307

Explore →

Is Your Infrastructure Affected by CVE-2026-53307?

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

Start Free Scan →Browse All CVEs