In the Linux kernel, the following vulnerability has been resolved: gpio: pca953x: fix pca953x_irq_bus_sync_unlock regmap lock Locking is disabled… (CVE-2026-74733)
A vulnerability in the Linux kernel's gpio pca953x driver was resolved. The issue involved improper locking in the pca953x_irq_bus_sync_unlock function, which failed to hold the required i2c_lock during regmap read operations. This could lead to multiple threads concurrently accessing registers incorrectly. A prior patch addressed only the write operation to the interrupt mask register but did not protect the read from the direction register.
AI Analysis
Technical Summary
The Linux kernel gpio pca953x driver disables locking in the regmap configuration because it uses its own lock mechanism. All regmap read and write calls must hold the i2c_lock to ensure thread safety. The function pca953x_irq_bus_sync_unlock did not hold this lock during regmap reads, allowing potential concurrent access by multiple threads to incorrect registers. This flaw was partially fixed previously by protecting writes to the interrupt mask register but did not cover reads from the direction register. The vulnerability has now been resolved.
Potential Impact
Without proper locking, concurrent threads could read or write incorrect registers, potentially causing inconsistent or unintended behavior in the gpio pca953x driver. This could affect system stability or correctness of GPIO operations relying on this driver. No direct exploit or impact on confidentiality, integrity, or availability is described.
Mitigation Recommendations
A fix has been applied to the Linux kernel gpio pca953x driver to ensure that the i2c_lock is held during all regmap read and write operations, including in pca953x_irq_bus_sync_unlock. Users should update to the fixed kernel version once available. Patch status is not yet confirmed—check the vendor advisory or Linux kernel mailing lists for the specific patch and version details.
In the Linux kernel, the following vulnerability has been resolved: gpio: pca953x: fix pca953x_irq_bus_sync_unlock regmap lock Locking is disabled… (CVE-2026-74733)
Description
A vulnerability in the Linux kernel's gpio pca953x driver was resolved. The issue involved improper locking in the pca953x_irq_bus_sync_unlock function, which failed to hold the required i2c_lock during regmap read operations. This could lead to multiple threads concurrently accessing registers incorrectly. A prior patch addressed only the write operation to the interrupt mask register but did not protect the read from the direction register.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel gpio pca953x driver disables locking in the regmap configuration because it uses its own lock mechanism. All regmap read and write calls must hold the i2c_lock to ensure thread safety. The function pca953x_irq_bus_sync_unlock did not hold this lock during regmap reads, allowing potential concurrent access by multiple threads to incorrect registers. This flaw was partially fixed previously by protecting writes to the interrupt mask register but did not cover reads from the direction register. The vulnerability has now been resolved.
Potential Impact
Without proper locking, concurrent threads could read or write incorrect registers, potentially causing inconsistent or unintended behavior in the gpio pca953x driver. This could affect system stability or correctness of GPIO operations relying on this driver. No direct exploit or impact on confidentiality, integrity, or availability is described.
Mitigation Recommendations
A fix has been applied to the Linux kernel gpio pca953x driver to ensure that the i2c_lock is held during all regmap read and write operations, including in pca953x_irq_bus_sync_unlock. Users should update to the fixed kernel version once available. Patch status is not yet confirmed—check the vendor advisory or Linux kernel mailing lists for the specific patch and version details.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-p6rq-qpqh-5f25
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-74733"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a8a27f0acd9273b499bc6d1
Added to database: 08/22/2026, 22:51:28 UTC
Last enriched: 08/23/2026, 00:55:12 UTC
Last updated: 08/23/2026, 02:32:14 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.