CVE-2026-74468

UNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

gpio: pch: use raw_spinlock_t for the register lock

pch_irq_type() is registered as the irq_chip .irq_set_type callback and takes chip->spinlock with spin_lock_irqsave(). This callback is reached from __setup_irq() -> __irq_set_trigger() -> chip->irq_set_type() while the caller holds desc->lock, a raw_spinlock_t, with hardirqs disabled. That context is not sleepable, but on PREEMPT_RT a regular spinlock_t is an rtmutex-backed sleeping lock, so acquiring it there is invalid.

This was confirmed on a PREEMPT_RT kernel with lockdep (PROVE_RAW_LOCK_NESTING and DEBUG_ATOMIC_SLEEP). A grounded PoC mirrored pch_irq_type()'s locking and drove it through the real genirq carrier irq_set_irq_type() -> __irq_set_trigger() -> chip->irq_set_type(), i.e. the same __irq_set_trigger() edge that __setup_irq() takes for a requested IRQ. With the original spin_lock_irqsave() edge lockdep reported an invalid wait context, immediately followed by:

BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48 in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 95, name: insmod hardirqs last disabled at (3784): _raw_spin_lock_irqsave+0x4f/0x60 rt_spin_lock+0x3a/0x1c0 repro_irq_set_type+0x64/0xa0 [pch_repro] __irq_set_trigger+0x69/0x140 irq_set_irq_type+0x78/0xd0

Switching the mirrored lock to raw_spinlock_t made both splats go away.

Convert the register lock to raw_spinlock_t. The same lock also serializes the GPIO direction/value callbacks and the suspend/resume register save/restore, but all of those critical sections only perform MMIO register accesses (ioread32()/iowrite32()) and irq_set_handler_locked(); none of them contain sleepable operations. Keeping this register lock non-sleeping is therefore appropriate for the irqchip callbacks and does not change the GPIO-side locking contract.

This is the same class of issue and fix as recently addressed for other GPIO controllers, e.g. commit 286533cb14a3 ("gpio: sch: use raw_spinlock_t in the irq startup path") and commit 90f0109019e6 ("gpio: eic-sprd: use raw_spinlock_t in the irq startup path").

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% 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
No SSVC decision: EchelonGraph has not assessed this CVECISA 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 BOD 26-04 block below.

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

August 15, 2026

Last Modified

August 19, 2026

Vendor Advisories for CVE-2026-74468(1)

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

Patch Availability(5)

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

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1
  • every version up to 6.12.107-1~deb12u1: fixed in 6.12.107-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (33 versions)
  • every version up to 6.12.105-1: fixed in 6.12.105-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (165 versions)
  • every version up to 7.1.8-1: fixed in 7.1.8-1
—

All Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 8× in last 7d / 40× 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.

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. 4 repeat rows among the latest 93 are merged into the row they repeat.

  1. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-18 03:14 UTCEG score recompute
  4. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-12 15:39 UTCEG score recompute
  11. 2026-10-11 19:25 UTCEG score recompute
  12. 2026-10-11 16:41 UTCEG score recompute
  13. 2026-10-11 14:00 UTCEG score recompute
  14. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  16. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  18. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  19. 2026-10-06 23:41 UTCVendor advisory
  20. 2026-10-06 23:40 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  21. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-10-03 22:42 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  25. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
Show 64 more
  1. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-09-30 20:57 UTCEG score recompute
  3. 2026-09-30 20:57 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  4. 2026-09-29 15:24 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-09-27 08:25 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  8. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  9. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-09-23 01:25 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  13. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-09-20 00:26 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  17. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-09-16 23:27 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  19. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-09-13 18:25 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  23. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-09-10 17:26 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  26. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  27. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  28. 2026-09-07 16:14 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  29. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  30. 2026-09-04 08:04 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  31. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  32. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  33. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  34. 2026-09-01 07:05 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  35. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  36. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  37. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  38. 2026-08-29 06:05 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  39. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  40. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  41. 2026-08-26 14:47 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  42. 2026-08-25 19:34 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  43. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  44. 2026-08-24 14:18 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  45. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  46. 2026-08-22 18:36 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  47. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  48. 2026-08-20 22:56 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  49. 2026-08-19 17:36 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  50. 2026-08-19 17:34 UTCNVD update
  51. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  52. 2026-08-19 16:45 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  53. 2026-08-19 16:43 UTCMITRE cvelistV5
  54. 2026-08-18 13:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  55. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  56. 2026-08-17 06:25 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  57. 2026-08-17 06:22 UTCNVD update
  58. 2026-08-17 05:25 UTCEG score recompute
  59. 2026-08-17 05:25 UTCGHSA enrichmentGHSA-2rc5-gh24-qjjx
  60. 2026-08-17 05:24 UTCMITRE cvelistV5
  61. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  62. 2026-08-15 13:27 UTCNVD update
  63. 2026-08-15 12:40 UTCEG score recompute
  64. 2026-08-15 12:37 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-74468?
CVE-2026-74468 is a vulnerability whose severity is not yet rated; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: gpio: pch: use rawspinlockt for the register lock pchirqtype() is registered as the irqchip .irqset_type callback and takes chip->spinlock with spinlockirqsave(). This callback is reached from setupirq() -> irqsettrigger() ->…
When was the CVE record for CVE-2026-74468 published?
The CVE record for CVE-2026-74468 was published on August 15, 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 August 19, 2026; the record at its source may have been updated since.
Is CVE-2026-74468 actively exploited?
CVE-2026-74468 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-74468?
A fix for CVE-2026-74468 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74468 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-74468

Explore →

Is Your Infrastructure Affected by CVE-2026-74468?

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