From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-89964: parisc: eisa: Fix infinite loop when parsing invalid IRQ value
Date: Wed, 16 Sep 2026 11:31:34 +0100 [thread overview]
Message-ID: <2026091652-CVE-2026-89964-cb07@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
parisc: eisa: Fix infinite loop when parsing invalid IRQ value
When an invalid value is passed via the "eisa_irq_edge=" kernel
command line parameter (e.g. "eisa_irq_edge=16,5"), eisa_irq_setup()
prints an error message and continues without advancing the current
position. As a result the same invalid value is parsed again and
again, causing an infinite loop while the kernel boots.
Advance to the next comma-separated entry, or stop parsing when there
is no next entry, before continuing so that the remaining entries are
processed normally.
The Linux kernel CVE team has assigned CVE-2026-89964 to this issue.
Affected and fixed versions
===========================
Fixed in 5.10.270 with commit 68659b627770f3c8d8f578e8ddee78a07d5f1d0e
Fixed in 5.15.221 with commit 8640ade22369e248f77fbdd31a9d71b338499eef
Fixed in 6.1.188 with commit 21f063e3c2b11fb9078ccdfd3b23634313ce4f0c
Fixed in 6.6.157 with commit 62d88e93ef5e1e04041e347945f7d7510eba1797
Fixed in 6.12.110 with commit bb10d54b74845eb4547baa1b9e908ecd32aa64e1
Fixed in 6.18.51 with commit 3e2691eeee83a819125dba3f42c74e1b6730d5cd
Fixed in 7.2.5 with commit 16a62a3f2128b3d86fefc082d8f631becd02bff5
Fixed in 7.3-rc1 with commit 8b585431a16cfb9d8f2955a9fa0787ce3dceb3c2
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-89964
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/parisc/eisa.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/68659b627770f3c8d8f578e8ddee78a07d5f1d0e
https://git.kernel.org/stable/c/8640ade22369e248f77fbdd31a9d71b338499eef
https://git.kernel.org/stable/c/21f063e3c2b11fb9078ccdfd3b23634313ce4f0c
https://git.kernel.org/stable/c/62d88e93ef5e1e04041e347945f7d7510eba1797
https://git.kernel.org/stable/c/bb10d54b74845eb4547baa1b9e908ecd32aa64e1
https://git.kernel.org/stable/c/3e2691eeee83a819125dba3f42c74e1b6730d5cd
https://git.kernel.org/stable/c/16a62a3f2128b3d86fefc082d8f631becd02bff5
https://git.kernel.org/stable/c/8b585431a16cfb9d8f2955a9fa0787ce3dceb3c2
reply other threads:[~2026-09-16 10:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026091652-CVE-2026-89964-cb07@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.