Answer in brief
CVE-2026-74733 records a Unknown severity vulnerability in gpio: pca953x: fix pca953x_irq_bus_sync_unlock regmap lock. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=bfc6444b57dc7186b6acc964705d7516cbaf3904 <e6a2f5f845f50b0c4299bace5111f56d3390a090 || >=bfc6444b57dc7186b6acc964705d7516cbaf3904 <9dc325327babe7f159e84cbe9380a45342da0585 || 58a5c93bd1a6e949267400080f07e57ffe05ec34 || e2ecdddca80dd845df42376e4b0197fe97018ba2 || de7cffa53149c7b48bd1bb29b02390c9f05b7f41 || >=6.1.101 <6.2 || >=6.6.42 <6.7 || >=6.9.11 <6.10 | e6a2f5f845f50b0c4299bace5111f56d3390a090, 9dc325327babe7f159e84cbe9380a45342da0585, 6.2, 6.7, 6.10 |
| Linux/Linuxgeneric | 6.10 | Not reported |
Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 22, 2026
In the Linux kernel, the following vulnerability has been resolved: gpio: pca953x: fix pca953x_irq_bus_sync_unlock regmap lock Locking is disabled in the regmap config as this driver uses its own lock. This means that all calls to regmap functions (read or write) must hold the i2c_lock. The function pca953x_irq_bus_sync_unlock() did not do this, and it was therefore possible that multiple threads could cause an incorrect register to be read/written. A previous patch partly fixed this, but only protected the write to the interrupt mask register, and not the read from the direction register.
Quoted source text, attributed separately from HOL analysis.