Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-74733gpio: pca953x: fix pca953x_irq_bus_sync_unlock regmap lock

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 2 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-74733, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 58a5c93bd1a6e949267400080f07e57ffe05ec34 – < 58ed56c093a857c19f04cf3db1f02d2e793aec88
    • affected e2ecdddca80dd845df42376e4b0197fe97018ba2 – < 5d05c4252c09ce10624be2197853c80bf87424e4
    • affected bfc6444b57dc7186b6acc964705d7516cbaf3904 – < 41255e64eb9dd87b0b8675f4e47a9c67bcef6e39
    • affected bfc6444b57dc7186b6acc964705d7516cbaf3904 – < bf3f37c2d40b51deb79aea910f28999d7c8c6b5a
    • affected bfc6444b57dc7186b6acc964705d7516cbaf3904 – < e6a2f5f845f50b0c4299bace5111f56d3390a090
    • affected bfc6444b57dc7186b6acc964705d7516cbaf3904 – < 9dc325327babe7f159e84cbe9380a45342da0585
    • affected de7cffa53149c7b48bd1bb29b02390c9f05b7f41
    • affected 6.1.101 – < 6.1.191
    • affected 6.6.42 – < 6.6.160
    • affected 6.9.11 – < 6.10
  • Linux · Linux

    • affected 6.10
    • unaffected < 6.10
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.1.9 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74733 badge
[![CVE-2026-74733](https://cveledger.app/badge/CVE-2026-74733.svg)](https://cveledger.app/cve/CVE-2026-74733)

Record last updated .