{"uuid": "35481490-6af6-4070-b7bd-8bc903ad9546", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2024-42253", "type": "seen", "source": "https://t.me/cvedetector/2763", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2024-42253 - NXP pca953x GPIO Interrupt Latching Protocol Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2024-42253 \nPublished : Aug. 8, 2024, 9:15 a.m. | 34\u00a0minutes ago \nDescription : In the Linux kernel, the following vulnerability has been resolved:  \n  \ngpio: pca953x: fix pca953x_irq_bus_sync_unlock race  \n  \nEnsure that `i2c_lock' is held when setting interrupt latch and mask in  \npca953x_irq_bus_sync_unlock() in order to avoid races.  \n  \nThe other (non-probe) call site pca953x_gpio_set_multiple() ensures the  \nlock is held before calling pca953x_write_regs().  \n  \nThe problem occurred when a request raced against irq_bus_sync_unlock()  \napproximately once per thousand reboots on an i.MX8MP based system.  \n  \n * Normal case  \n  \n   0-0022: write register AI|3a {03,02,00,00,01} Input latch P0  \n   0-0022: write register AI|49 {fc,fd,ff,ff,fe} Interrupt mask P0  \n   0-0022: write register AI|08 {ff,00,00,00,00} Output P3  \n   0-0022: write register AI|12 {fc,00,00,00,00} Config P3  \n  \n * Race case  \n  \n   0-0022: write register AI|08 {ff,00,00,00,00} Output P3  \n   0-0022: write register AI|08 {03,02,00,00,01} *** Wrong register ***  \n   0-0022: write register AI|12 {fc,00,00,00,00} Config P3  \n   0-0022: write register AI|49 {fc,fd,ff,ff,fe} Interrupt mask P0 \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"08 Aug 2024\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2024-08-08T12:12:50.000000Z"}