{"api_version":"1","generated_at":"2026-08-16T15:16:01+00:00","cve":"CVE-2026-74468","urls":{"html":"https://cve.report/CVE-2026-74468","api":"https://cve.report/api/cve/CVE-2026-74468.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-74468","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-74468"},"summary":{"title":"gpio: pch: use raw_spinlock_t for the register lock","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ngpio: pch: use raw_spinlock_t for the register lock\n\npch_irq_type() is registered as the irq_chip .irq_set_type callback and\ntakes chip->spinlock with spin_lock_irqsave().  This callback is reached\nfrom __setup_irq() -> __irq_set_trigger() -> chip->irq_set_type() while\nthe caller holds desc->lock, a raw_spinlock_t, with hardirqs disabled.\nThat context is not sleepable, but on PREEMPT_RT a regular spinlock_t is\nan rtmutex-backed sleeping lock, so acquiring it there is invalid.\n\nThis was confirmed on a PREEMPT_RT kernel with lockdep\n(PROVE_RAW_LOCK_NESTING and DEBUG_ATOMIC_SLEEP).  A grounded PoC mirrored\npch_irq_type()'s locking and drove it through the real genirq carrier\nirq_set_irq_type() -> __irq_set_trigger() -> chip->irq_set_type(), i.e.\nthe same __irq_set_trigger() edge that __setup_irq() takes for a\nrequested IRQ.  With the original spin_lock_irqsave() edge lockdep\nreported an invalid wait context, immediately followed by:\n\n  BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48\n  in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 95, name: insmod\n  hardirqs last disabled at (3784): _raw_spin_lock_irqsave+0x4f/0x60\n   rt_spin_lock+0x3a/0x1c0\n   repro_irq_set_type+0x64/0xa0 [pch_repro]\n   __irq_set_trigger+0x69/0x140\n   irq_set_irq_type+0x78/0xd0\n\nSwitching the mirrored lock to raw_spinlock_t made both splats go away.\n\nConvert the register lock to raw_spinlock_t.  The same lock also\nserializes the GPIO direction/value callbacks and the suspend/resume\nregister save/restore, but all of those critical sections only perform\nMMIO register accesses (ioread32()/iowrite32()) and\nirq_set_handler_locked(); none of them contain sleepable operations.\nKeeping this register lock non-sleeping is therefore appropriate for the\nirqchip callbacks and does not change the GPIO-side locking contract.\n\nThis is the same class of issue and fix as recently addressed for other\nGPIO controllers, e.g. commit 286533cb14a3 (\"gpio: sch: use raw_spinlock_t\nin the irq startup path\") and commit 90f0109019e6 (\"gpio: eic-sprd: use\nraw_spinlock_t in the irq startup path\").","state":"PUBLISHED","assigner":"Linux","published_at":"2026-08-15 13:17:51","updated_at":"2026-08-15 13:17:51"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/466ab0c41d5f54f71cee60619d07c4abd0ffd2cd","name":"https://git.kernel.org/stable/c/466ab0c41d5f54f71cee60619d07c4abd0ffd2cd","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c0a4ec89fc26e4b679b04f1002c503cb2529acdc","name":"https://git.kernel.org/stable/c/c0a4ec89fc26e4b679b04f1002c503cb2529acdc","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/16da33cb36e663b6967112185e11d00ce8ff957c","name":"https://git.kernel.org/stable/c/16da33cb36e663b6967112185e11d00ce8ff957c","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a02b8950d619123da64f69b70fe1dadef217dfe4","name":"https://git.kernel.org/stable/c/a02b8950d619123da64f69b70fe1dadef217dfe4","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/ff050589a21967883bb55f6dba42568f8367ad4a","name":"https://git.kernel.org/stable/c/ff050589a21967883bb55f6dba42568f8367ad4a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-74468","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-74468","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a 16da33cb36e663b6967112185e11d00ce8ff957c git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a ff050589a21967883bb55f6dba42568f8367ad4a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a 466ab0c41d5f54f71cee60619d07c4abd0ffd2cd git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a c0a4ec89fc26e4b679b04f1002c503cb2529acdc git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 38eb18a6f92da886fc1af509d25e8f7a49e23d9a a02b8950d619123da64f69b70fe1dadef217dfe4 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 3.2","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 3.2 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.6.151 6.6.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.103 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.44 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.8 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc6 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpio/gpio-pch.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"16da33cb36e663b6967112185e11d00ce8ff957c","status":"affected","version":"38eb18a6f92da886fc1af509d25e8f7a49e23d9a","versionType":"git"},{"lessThan":"ff050589a21967883bb55f6dba42568f8367ad4a","status":"affected","version":"38eb18a6f92da886fc1af509d25e8f7a49e23d9a","versionType":"git"},{"lessThan":"466ab0c41d5f54f71cee60619d07c4abd0ffd2cd","status":"affected","version":"38eb18a6f92da886fc1af509d25e8f7a49e23d9a","versionType":"git"},{"lessThan":"c0a4ec89fc26e4b679b04f1002c503cb2529acdc","status":"affected","version":"38eb18a6f92da886fc1af509d25e8f7a49e23d9a","versionType":"git"},{"lessThan":"a02b8950d619123da64f69b70fe1dadef217dfe4","status":"affected","version":"38eb18a6f92da886fc1af509d25e8f7a49e23d9a","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpio/gpio-pch.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"3.2"},{"lessThan":"3.2","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.6.*","status":"unaffected","version":"6.6.151","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.103","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.44","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.8","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc6","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.6.151","versionStartIncluding":"3.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.103","versionStartIncluding":"3.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.44","versionStartIncluding":"3.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.8","versionStartIncluding":"3.2","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc6","versionStartIncluding":"3.2","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ngpio: pch: use raw_spinlock_t for the register lock\n\npch_irq_type() is registered as the irq_chip .irq_set_type callback and\ntakes chip->spinlock with spin_lock_irqsave().  This callback is reached\nfrom __setup_irq() -> __irq_set_trigger() -> chip->irq_set_type() while\nthe caller holds desc->lock, a raw_spinlock_t, with hardirqs disabled.\nThat context is not sleepable, but on PREEMPT_RT a regular spinlock_t is\nan rtmutex-backed sleeping lock, so acquiring it there is invalid.\n\nThis was confirmed on a PREEMPT_RT kernel with lockdep\n(PROVE_RAW_LOCK_NESTING and DEBUG_ATOMIC_SLEEP).  A grounded PoC mirrored\npch_irq_type()'s locking and drove it through the real genirq carrier\nirq_set_irq_type() -> __irq_set_trigger() -> chip->irq_set_type(), i.e.\nthe same __irq_set_trigger() edge that __setup_irq() takes for a\nrequested IRQ.  With the original spin_lock_irqsave() edge lockdep\nreported an invalid wait context, immediately followed by:\n\n  BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48\n  in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 95, name: insmod\n  hardirqs last disabled at (3784): _raw_spin_lock_irqsave+0x4f/0x60\n   rt_spin_lock+0x3a/0x1c0\n   repro_irq_set_type+0x64/0xa0 [pch_repro]\n   __irq_set_trigger+0x69/0x140\n   irq_set_irq_type+0x78/0xd0\n\nSwitching the mirrored lock to raw_spinlock_t made both splats go away.\n\nConvert the register lock to raw_spinlock_t.  The same lock also\nserializes the GPIO direction/value callbacks and the suspend/resume\nregister save/restore, but all of those critical sections only perform\nMMIO register accesses (ioread32()/iowrite32()) and\nirq_set_handler_locked(); none of them contain sleepable operations.\nKeeping this register lock non-sleeping is therefore appropriate for the\nirqchip callbacks and does not change the GPIO-side locking contract.\n\nThis is the same class of issue and fix as recently addressed for other\nGPIO controllers, e.g. commit 286533cb14a3 (\"gpio: sch: use raw_spinlock_t\nin the irq startup path\") and commit 90f0109019e6 (\"gpio: eic-sprd: use\nraw_spinlock_t in the irq startup path\")."}],"providerMetadata":{"dateUpdated":"2026-08-15T12:27:06.250Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/16da33cb36e663b6967112185e11d00ce8ff957c"},{"url":"https://git.kernel.org/stable/c/ff050589a21967883bb55f6dba42568f8367ad4a"},{"url":"https://git.kernel.org/stable/c/466ab0c41d5f54f71cee60619d07c4abd0ffd2cd"},{"url":"https://git.kernel.org/stable/c/c0a4ec89fc26e4b679b04f1002c503cb2529acdc"},{"url":"https://git.kernel.org/stable/c/a02b8950d619123da64f69b70fe1dadef217dfe4"}],"title":"gpio: pch: use raw_spinlock_t for the register lock","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-74468","datePublished":"2026-08-15T12:27:06.250Z","dateReserved":"2026-08-15T05:44:03.902Z","dateUpdated":"2026-08-15T12:27:06.250Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-08-15 13:17:51","lastModifiedDate":"2026-08-15 13:17:51","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"74468","Ordinal":"1","Title":"gpio: pch: use raw_spinlock_t for the register lock","CVE":"CVE-2026-74468","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"74468","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ngpio: pch: use raw_spinlock_t for the register lock\n\npch_irq_type() is registered as the irq_chip .irq_set_type callback and\ntakes chip->spinlock with spin_lock_irqsave().  This callback is reached\nfrom __setup_irq() -> __irq_set_trigger() -> chip->irq_set_type() while\nthe caller holds desc->lock, a raw_spinlock_t, with hardirqs disabled.\nThat context is not sleepable, but on PREEMPT_RT a regular spinlock_t is\nan rtmutex-backed sleeping lock, so acquiring it there is invalid.\n\nThis was confirmed on a PREEMPT_RT kernel with lockdep\n(PROVE_RAW_LOCK_NESTING and DEBUG_ATOMIC_SLEEP).  A grounded PoC mirrored\npch_irq_type()'s locking and drove it through the real genirq carrier\nirq_set_irq_type() -> __irq_set_trigger() -> chip->irq_set_type(), i.e.\nthe same __irq_set_trigger() edge that __setup_irq() takes for a\nrequested IRQ.  With the original spin_lock_irqsave() edge lockdep\nreported an invalid wait context, immediately followed by:\n\n  BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:48\n  in_atomic(): 1, irqs_disabled(): 1, non_block: 0, pid: 95, name: insmod\n  hardirqs last disabled at (3784): _raw_spin_lock_irqsave+0x4f/0x60\n   rt_spin_lock+0x3a/0x1c0\n   repro_irq_set_type+0x64/0xa0 [pch_repro]\n   __irq_set_trigger+0x69/0x140\n   irq_set_irq_type+0x78/0xd0\n\nSwitching the mirrored lock to raw_spinlock_t made both splats go away.\n\nConvert the register lock to raw_spinlock_t.  The same lock also\nserializes the GPIO direction/value callbacks and the suspend/resume\nregister save/restore, but all of those critical sections only perform\nMMIO register accesses (ioread32()/iowrite32()) and\nirq_set_handler_locked(); none of them contain sleepable operations.\nKeeping this register lock non-sleeping is therefore appropriate for the\nirqchip callbacks and does not change the GPIO-side locking contract.\n\nThis is the same class of issue and fix as recently addressed for other\nGPIO controllers, e.g. commit 286533cb14a3 (\"gpio: sch: use raw_spinlock_t\nin the irq startup path\") and commit 90f0109019e6 (\"gpio: eic-sprd: use\nraw_spinlock_t in the irq startup path\").","Type":"Description","Title":"gpio: pch: use raw_spinlock_t for the register lock"}]}}}