From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-80732: ata: pata_sl82c105: fix bridge revision use-after-free
Date: Thu, 3 Sep 2026 10:22:01 +0200 [thread overview]
Message-ID: <2026090358-CVE-2026-80732-21cc@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ata: pata_sl82c105: fix bridge revision use-after-free
pci_get_slot() returns a referenced PCI device. Commit 44c10138fd4b
("PCI: Change all drivers to use pci_device->revision") replaced a
configuration-space read with direct access to the cached revision field,
but left that access after pci_dev_put(). The bridge may therefore be freed
before its revision is read.
Read the revision before dropping the reference.
The Linux kernel CVE team has assigned CVE-2026-80732 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.23 with commit 44c10138fd4bbc4b6d6bff0873c24902f2a9da65 and fixed in 5.10.265 with commit 1268ca9418e2217f2b60705cf4a280b689b26678
Issue introduced in 2.6.23 with commit 44c10138fd4bbc4b6d6bff0873c24902f2a9da65 and fixed in 5.15.216 with commit a626dfca96041842053cf2d1efceb436c4cd8dcf
Issue introduced in 2.6.23 with commit 44c10138fd4bbc4b6d6bff0873c24902f2a9da65 and fixed in 6.1.183 with commit 5ef87b1b4656d675440ceab32a56e69ad958d3a1
Issue introduced in 2.6.23 with commit 44c10138fd4bbc4b6d6bff0873c24902f2a9da65 and fixed in 6.6.152 with commit fa0dca89b4fb0909ffda7b9ab6051af33270f95e
Issue introduced in 2.6.23 with commit 44c10138fd4bbc4b6d6bff0873c24902f2a9da65 and fixed in 6.12.104 with commit dc711fb137b33c12e6ca22b6a9c9b9f21d49e4de
Issue introduced in 2.6.23 with commit 44c10138fd4bbc4b6d6bff0873c24902f2a9da65 and fixed in 6.18.45 with commit a837deeaa37cc3f0e8c4e5c096787047f272c956
Issue introduced in 2.6.23 with commit 44c10138fd4bbc4b6d6bff0873c24902f2a9da65 and fixed in 7.1.9 with commit 56fd78c8c820f527f8003e379ab71004b2e79a44
Issue introduced in 2.6.23 with commit 44c10138fd4bbc4b6d6bff0873c24902f2a9da65 and fixed in 7.2 with commit 7700a31039cdc6715cb6cce7e7a664ee4e945f67
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-80732
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/ata/pata_sl82c105.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/1268ca9418e2217f2b60705cf4a280b689b26678
https://git.kernel.org/stable/c/a626dfca96041842053cf2d1efceb436c4cd8dcf
https://git.kernel.org/stable/c/5ef87b1b4656d675440ceab32a56e69ad958d3a1
https://git.kernel.org/stable/c/fa0dca89b4fb0909ffda7b9ab6051af33270f95e
https://git.kernel.org/stable/c/dc711fb137b33c12e6ca22b6a9c9b9f21d49e4de
https://git.kernel.org/stable/c/a837deeaa37cc3f0e8c4e5c096787047f272c956
https://git.kernel.org/stable/c/56fd78c8c820f527f8003e379ab71004b2e79a44
https://git.kernel.org/stable/c/7700a31039cdc6715cb6cce7e7a664ee4e945f67
reply other threads:[~2026-09-03 8:22 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=2026090358-CVE-2026-80732-21cc@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.