From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74690: s390/ism: Fix UAF of sba and ieq during ism_dev_exit()
Date: Sat, 22 Aug 2026 17:32:54 +0200 [thread overview]
Message-ID: <2026082233-CVE-2026-74690-0118@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
s390/ism: Fix UAF of sba and ieq during ism_dev_exit()
A ism interrupt handler can be active in parallel with ism_dev_exit(),
accessing freed data structures.
No new interrupts will be generated after unregister_ieq(). Drain ongoing
interrupt handlers by free_irq(), before freeing ism data structures.
The Linux kernel CVE team has assigned CVE-2026-74690 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.19 with commit 684b89bc39ce4f204b1a2b180f39f2eb36a6b695 and fixed in 6.18.45 with commit fc3021284050ecb3bba8a7851340cedcb5037928
Issue introduced in 4.19 with commit 684b89bc39ce4f204b1a2b180f39f2eb36a6b695 and fixed in 7.1.9 with commit 774394d27930ec4cf4cb3eed8ab6a4d20cb2430a
Issue introduced in 4.19 with commit 684b89bc39ce4f204b1a2b180f39f2eb36a6b695 and fixed in 7.2 with commit b1896543ce59c4258625a35cf41e23a9a1f80ea2
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-74690
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/s390/net/ism_drv.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/fc3021284050ecb3bba8a7851340cedcb5037928
https://git.kernel.org/stable/c/774394d27930ec4cf4cb3eed8ab6a4d20cb2430a
https://git.kernel.org/stable/c/b1896543ce59c4258625a35cf41e23a9a1f80ea2
reply other threads:[~2026-08-22 15:40 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=2026082233-CVE-2026-74690-0118@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.