{"api_version":"1","generated_at":"2026-09-24T23:01:58+00:00","cve":"CVE-2026-97481","urls":{"html":"https://cve.report/CVE-2026-97481","api":"https://cve.report/api/cve/CVE-2026-97481.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-97481","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-97481"},"summary":{"title":"serial: 8250: fix possible ISR soft lockup","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nserial: 8250: fix possible ISR soft lockup\n\nThere are rare cases in which the host gets stuck in the ISR because it\nis flooded with messages during the startup phase.\n\nThe reason for the soft lockup in the ISR is the missing FIFO error IRQ\n(FIFOE) handling. Not handling it and reporting IRQ_HANDLED triggers\nthe IRQ immediately again.\n\nFix this by adding a check for the FIFOE status and clearing the FIFO\nif no data is ready (DR).\n\nThis behavior was observed on an AM62L device which uses the OMAP 8250\ndriver. Fix it for all 8250 drivers, since the OMAP driver's special\nIRQ setup handling may trigger this behavior more frequently, but it\nis not ensured that other 8250 drivers aren't affected.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-24 17:17:25","updated_at":"2026-09-24 17:17:25"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/2881b2e6da02daea1eb8254247ba8fd20c9d3348","name":"https://git.kernel.org/stable/c/2881b2e6da02daea1eb8254247ba8fd20c9d3348","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/4295c58990b7a84e8349a2226db692e252825b60","name":"https://git.kernel.org/stable/c/4295c58990b7a84e8349a2226db692e252825b60","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/0c6bf45e5a345cc3b9ffbeaf9083ecac3c2293eb","name":"https://git.kernel.org/stable/c/0c6bf45e5a345cc3b9ffbeaf9083ecac3c2293eb","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-97481","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-97481","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 2881b2e6da02daea1eb8254247ba8fd20c9d3348 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 4295c58990b7a84e8349a2226db692e252825b60 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 0c6bf45e5a345cc3b9ffbeaf9083ecac3c2293eb git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.12.111 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.18.53 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.111 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.53 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/tty/serial/8250/8250_port.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"2881b2e6da02daea1eb8254247ba8fd20c9d3348","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"4295c58990b7a84e8349a2226db692e252825b60","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"0c6bf45e5a345cc3b9ffbeaf9083ecac3c2293eb","status":"affected","version":"1da177e4c3f41524e886b7f1b8a0c1fc7321cac2","versionType":"git"},{"lessThan":"6.12.111","status":"affected","version":"0","versionType":"semver"},{"lessThan":"6.18.53","status":"affected","version":"0","versionType":"semver"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/tty/serial/8250/8250_port.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.111","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.53","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.2","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.111","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.53","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nserial: 8250: fix possible ISR soft lockup\n\nThere are rare cases in which the host gets stuck in the ISR because it\nis flooded with messages during the startup phase.\n\nThe reason for the soft lockup in the ISR is the missing FIFO error IRQ\n(FIFOE) handling. Not handling it and reporting IRQ_HANDLED triggers\nthe IRQ immediately again.\n\nFix this by adding a check for the FIFOE status and clearing the FIFO\nif no data is ready (DR).\n\nThis behavior was observed on an AM62L device which uses the OMAP 8250\ndriver. Fix it for all 8250 drivers, since the OMAP driver's special\nIRQ setup handling may trigger this behavior more frequently, but it\nis not ensured that other 8250 drivers aren't affected."}],"providerMetadata":{"dateUpdated":"2026-09-24T16:04:23.958Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/2881b2e6da02daea1eb8254247ba8fd20c9d3348"},{"url":"https://git.kernel.org/stable/c/4295c58990b7a84e8349a2226db692e252825b60"},{"url":"https://git.kernel.org/stable/c/0c6bf45e5a345cc3b9ffbeaf9083ecac3c2293eb"}],"title":"serial: 8250: fix possible ISR soft lockup","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-97481","datePublished":"2026-09-24T16:04:23.958Z","dateReserved":"2026-09-24T16:01:01.149Z","dateUpdated":"2026-09-24T16:04:23.958Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-24 17:17:25","lastModifiedDate":"2026-09-24 17:17:25","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"97481","Ordinal":"1","Title":"serial: 8250: fix possible ISR soft lockup","CVE":"CVE-2026-97481","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"97481","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nserial: 8250: fix possible ISR soft lockup\n\nThere are rare cases in which the host gets stuck in the ISR because it\nis flooded with messages during the startup phase.\n\nThe reason for the soft lockup in the ISR is the missing FIFO error IRQ\n(FIFOE) handling. Not handling it and reporting IRQ_HANDLED triggers\nthe IRQ immediately again.\n\nFix this by adding a check for the FIFOE status and clearing the FIFO\nif no data is ready (DR).\n\nThis behavior was observed on an AM62L device which uses the OMAP 8250\ndriver. Fix it for all 8250 drivers, since the OMAP driver's special\nIRQ setup handling may trigger this behavior more frequently, but it\nis not ensured that other 8250 drivers aren't affected.","Type":"Description","Title":"serial: 8250: fix possible ISR soft lockup"}]}}}