LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42253: gpio: pca953x: fix pca953x_irq_bus_sync_unlock race

In the Linux kernel, the following vulnerability has been resolved: gpio: pca953x: fix pca953x_irq_bus_sync_unlock race Ensure that `i2c_lock' is held when setting interrupt latch and mask in pca953x_irq_bus_sync_unlock() in order to avoid races. The other (non-probe) call site pca953x_gpio_set_multiple() ensures the lock is held before calling pca953x_write_regs(). The problem occurred when a request raced against irq_bus_sync_unlock() approximately once per thousand reboots on an i.MX8MP based system. * Normal case 0-0022: write register AI|3a {03,02,00,00,01} Input latch P0 0-0022: write register AI|49 {fc,fd,ff,ff,fe} Interrupt mask P0 0-0022: write register AI|08 {ff,00,00,00,00} Output P3 0-0022: write register AI|12 {fc,00,00,00,00} Config P3 * Race case 0-0022: write register AI|08 {ff,00,00,00,00} Output P3 0-0022: write register AI|08 {03,02,00,00,01} *** Wrong register *** 0-0022: write register AI|12 {fc,00,00,00,00} Config P3 0-0022: write register AI|49 {fc,fd,ff,ff,fe} Interrupt mask P0

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A race condition in the Linux PCA953x GPIO expander driver can write interrupt configuration data to the wrong hardware register. The reported failure was intermittent—about once per thousand reboots on an i.MX8MP system—but incorrect GPIO behavior may affect confidentiality, integrity, or availability where these signals control sensitive hardware functions.

Executive priority

Treat as a high-priority maintenance issue for embedded, industrial, appliance, or edge systems using affected GPIO hardware, especially where GPIO outputs influence safety, access, power, or service availability. Broad enterprise Linux exposure is less likely without the relevant device. Patch during the next controlled maintenance window, accelerating for critical hardware roles.

Technical view

pca953x_irq_bus_sync_unlock() updated interrupt latch and mask registers without holding i2c_lock. A concurrent request could interfere with register selection, causing data intended for the input-latch register to reach an output register. The upstream correction holds the lock during these writes. The supplied CVSS v3.1 score is 7.8 with local, low-complexity, low-privilege access.

Likely exposure

Exposure is limited to Linux systems using the PCA953x GPIO expander driver in configurations where interrupt synchronization can race with concurrent GPIO operations. The source confirms occurrence on an i.MX8MP-based system. The supplied version data marks Linux 4.7 through several later release lines as affected, but exact distribution package boundaries require vendor confirmation.

Exploitation context

CISA KEV status is false, and the supplied sources provide no evidence of active exploitation or a public weaponized exploit. Evidence describes a rare operational race observed during reboot, not a demonstrated attack. The CVSS vector nevertheless indicates that a local, low-privileged attacker may be able to trigger high-impact consequences.

Researcher notes

The defect is a missing I2C lock around interrupt latch and mask writes in pca953x_irq_bus_sync_unlock(). The source shows register-pointer corruption during a concurrent request. Reproduction frequency and impact are hardware and workload dependent. The bundle does not establish exact vulnerable configurations, exploit reliability, or per-distribution fixed versions.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the referenced upstream locking fix.
  • Consult the operating-system or appliance vendor for the exact fixed package version.
  • Prioritize systems where PCA953x GPIO signals control security-sensitive or availability-critical hardware.
  • Limit local access and unnecessary privileged device interfaces until affected systems are updated.

Validation and detection

  • Inventory kernel versions and identify systems loading or incorporating the PCA953x GPIO driver.
  • Confirm whether affected hardware includes PCA953x-compatible GPIO expanders and interrupt handling.
  • Verify the installed kernel includes the applicable referenced stable commit or vendor backport.
  • Review vendor advisories and package changelogs for explicit CVE-2024-42253 remediation.
  • After updating, exercise reboot and GPIO-dependent health checks for device-specific regressions.
Prepared
Confidence
high
Sources
7

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-42253 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
6Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-42253Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux44896beae605b93f2232301befccb7ef42953198, 44896beae605b93f2232301befccb7ef42953198, 44896beae605b93f2232301befccb7ef42953198, 44896beae605b93f2232301befccb7ef42953198unaffected
LinuxLinux4.7, 0, 6.1.101, 6.6.42, 6.9.11, 6.10affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.