{"api_version":"1","generated_at":"2026-08-03T23:07:16+00:00","cve":"CVE-2026-64278","urls":{"html":"https://cve.report/CVE-2026-64278","api":"https://cve.report/api/cve/CVE-2026-64278.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-64278","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-64278"},"summary":{"title":"i2c: imx-lpi2c: mark I2C adapter when hardware is powered down","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: imx-lpi2c: mark I2C adapter when hardware is powered down\n\nOn some i.MX platforms, certain I2C client drivers keep a periodic\nworkqueue which continues to trigger I2C transfers.\n\nDuring system suspend/resume, there exists a time window between:\n  - suspend_noirq and the system entering suspend\n  - the system starting to resume and resume_noirq\n\nIn this window, the I2C controller resources such as clock and pinctrl\nmay already be disabled or not yet restored.\n\nIf a workqueue triggers an I2C transfer in this period, the driver\nattempts to access I2C registers while the hardware resources are\nunavailable, which may lead to system hang.\n\nMark the I2C adapter as suspended during noirq suspend and block new\ntransfers until resume, ensuring that I2C transfers are only issued\nwhen hardware resources are available.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-25 10:17:08","updated_at":"2026-07-30 15:00:27"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/218cfe364b55b2768221629bd4a69ad190b7fbbc","name":"https://git.kernel.org/stable/c/218cfe364b55b2768221629bd4a69ad190b7fbbc","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/5800647d19d3f1f747fda4dc67e55d6afa6ee119","name":"https://git.kernel.org/stable/c/5800647d19d3f1f747fda4dc67e55d6afa6ee119","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b2523f26979e0b5bd1422772176b2233fcd1f6d0","name":"https://git.kernel.org/stable/c/b2523f26979e0b5bd1422772176b2233fcd1f6d0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-64278","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64278","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1ee867e465c1b0216ec02d4c0d334c4e89919cec b2523f26979e0b5bd1422772176b2233fcd1f6d0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1ee867e465c1b0216ec02d4c0d334c4e89919cec 5800647d19d3f1f747fda4dc67e55d6afa6ee119 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1ee867e465c1b0216ec02d4c0d334c4e89919cec 218cfe364b55b2768221629bd4a69ad190b7fbbc git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.14","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.14 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.39 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1.4 7.1.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"64278","cve":"CVE-2026-64278","epss":"0.001980000","percentile":"0.098290000","score_date":"2026-08-02","updated_at":"2026-08-03 00:14:24"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/i2c/busses/i2c-imx-lpi2c.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"b2523f26979e0b5bd1422772176b2233fcd1f6d0","status":"affected","version":"1ee867e465c1b0216ec02d4c0d334c4e89919cec","versionType":"git"},{"lessThan":"5800647d19d3f1f747fda4dc67e55d6afa6ee119","status":"affected","version":"1ee867e465c1b0216ec02d4c0d334c4e89919cec","versionType":"git"},{"lessThan":"218cfe364b55b2768221629bd4a69ad190b7fbbc","status":"affected","version":"1ee867e465c1b0216ec02d4c0d334c4e89919cec","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/i2c/busses/i2c-imx-lpi2c.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.14"},{"lessThan":"6.14","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.39","versionType":"semver"},{"lessThanOrEqual":"7.1.*","status":"unaffected","version":"7.1.4","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.39","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1.4","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2-rc1","versionStartIncluding":"6.14","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: imx-lpi2c: mark I2C adapter when hardware is powered down\n\nOn some i.MX platforms, certain I2C client drivers keep a periodic\nworkqueue which continues to trigger I2C transfers.\n\nDuring system suspend/resume, there exists a time window between:\n  - suspend_noirq and the system entering suspend\n  - the system starting to resume and resume_noirq\n\nIn this window, the I2C controller resources such as clock and pinctrl\nmay already be disabled or not yet restored.\n\nIf a workqueue triggers an I2C transfer in this period, the driver\nattempts to access I2C registers while the hardware resources are\nunavailable, which may lead to system hang.\n\nMark the I2C adapter as suspended during noirq suspend and block new\ntransfers until resume, ensuring that I2C transfers are only issued\nwhen hardware resources are available."}],"providerMetadata":{"dateUpdated":"2026-07-25T08:49:22.535Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/b2523f26979e0b5bd1422772176b2233fcd1f6d0"},{"url":"https://git.kernel.org/stable/c/5800647d19d3f1f747fda4dc67e55d6afa6ee119"},{"url":"https://git.kernel.org/stable/c/218cfe364b55b2768221629bd4a69ad190b7fbbc"}],"title":"i2c: imx-lpi2c: mark I2C adapter when hardware is powered down","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-64278","datePublished":"2026-07-25T08:49:22.535Z","dateReserved":"2026-07-19T15:36:31.776Z","dateUpdated":"2026-07-25T08:49:22.535Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-25 10:17:08","lastModifiedDate":"2026-07-30 15:00:27","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"64278","Ordinal":"1","Title":"i2c: imx-lpi2c: mark I2C adapter when hardware is powered down","CVE":"CVE-2026-64278","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"64278","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ni2c: imx-lpi2c: mark I2C adapter when hardware is powered down\n\nOn some i.MX platforms, certain I2C client drivers keep a periodic\nworkqueue which continues to trigger I2C transfers.\n\nDuring system suspend/resume, there exists a time window between:\n  - suspend_noirq and the system entering suspend\n  - the system starting to resume and resume_noirq\n\nIn this window, the I2C controller resources such as clock and pinctrl\nmay already be disabled or not yet restored.\n\nIf a workqueue triggers an I2C transfer in this period, the driver\nattempts to access I2C registers while the hardware resources are\nunavailable, which may lead to system hang.\n\nMark the I2C adapter as suspended during noirq suspend and block new\ntransfers until resume, ensuring that I2C transfers are only issued\nwhen hardware resources are available.","Type":"Description","Title":"i2c: imx-lpi2c: mark I2C adapter when hardware is powered down"}]}}}