---
id: CVE-2026-74733
title: |-
  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
summary: |-
  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 regm…
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= bfc6444b57dc7186b6acc964705d7516cbaf3904 <
    bf3f37c2d40b51deb79aea910f28999d7c8c6b5a
  - >-
    Linux >= bfc6444b57dc7186b6acc964705d7516cbaf3904 <
    e6a2f5f845f50b0c4299bace5111f56d3390a090
  - >-
    Linux >= bfc6444b57dc7186b6acc964705d7516cbaf3904 <
    9dc325327babe7f159e84cbe9380a45342da0585
  - Linux 58a5c93bd1a6e949267400080f07e57ffe05ec34
  - Linux e2ecdddca80dd845df42376e4b0197fe97018ba2
  - Linux de7cffa53149c7b48bd1bb29b02390c9f05b7f41
  - Linux >= 6.1.101 < 6.2
  - Linux >= 6.6.42 < 6.7
  - Linux >= 6.9.11 < 6.10
  - Linux 6.10
published: '2026-08-22'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T11:17:49.253'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-74733'
references:
  - url: 'https://git.kernel.org/stable/c/9dc325327babe7f159e84cbe9380a45342da0585'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/bf3f37c2d40b51deb79aea910f28999d7c8c6b5a'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/e6a2f5f845f50b0c4299bace5111f56d3390a090'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
tags:
  - nvd
  - cve.org
epss: 0.00165
epssPercentile: 0.0535
ingestedAt: '2026-10-14T13:30:58.551Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.