In the Linux kernel, the following vulnerability has been resolved:
vfio/platform: Create persistent IRQ handlers The vfio-platform SET_IRQS
ioctl currently allows loopback triggering of an interrupt before a
signaling eventfd has been configured by the user, which thereby allows a
NULL pointer dereference. Rather than register the IRQ relative to a valid
trigger, register all IRQs in a disabled state in the device open path.
This allows mask operations on the IRQ to nest within the overall enable
state governed by a valid eventfd signal. This decouples @masked, protected
by the @locked spinlock from @trigger, protected via the @igate mutex. In
doing so, it’s guaranteed that changes to @trigger cannot race the IRQ
handlers because the IRQ handler is synchronously disabled before modifying
the trigger, and loopback triggering of the IRQ via ioctl is safe due to
serialization with trigger changes via igate. For compatibility,
request_irq() failures are maintained to be local to the SET_IRQS ioctl
rather than a fatal error in the open device path. This allows, for
example, a userspace driver with polling mode support to continue to work
regardless of moving the request_irq() call site. This necessarily blocks
all SET_IRQS access to the failed index.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
ubuntu | 20.04 | noarch | linux | < 5.4.0-189.209 | UNKNOWN |
ubuntu | 22.04 | noarch | linux | < 5.15.0-116.126 | UNKNOWN |
ubuntu | 24.04 | noarch | linux | < 6.8.0-35.35 | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws | < 5.4.0-1128.138 | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws | < 5.15.0-1065.71 | UNKNOWN |
ubuntu | 24.04 | noarch | linux-aws | < 6.8.0-1009.9 | UNKNOWN |
ubuntu | 20.04 | noarch | linux-aws-5.15 | < 5.15.0-1065.71~20.04.1 | UNKNOWN |
ubuntu | 18.04 | noarch | linux-aws-5.4 | < any | UNKNOWN |
ubuntu | 22.04 | noarch | linux-aws-6.5 | < any | UNKNOWN |
ubuntu | 20.04 | noarch | linux-azure | < 5.4.0-1133.140 | UNKNOWN |
git.kernel.org/stable/c/0f8d8f9c2173a541812dd750529f4a415117eb29
git.kernel.org/stable/c/62d4e43a569b67929eb3319780be5359694c8086
git.kernel.org/stable/c/675daf435e9f8e5a5eab140a9864dfad6668b375
git.kernel.org/stable/c/7932db06c82c5b2f42a4d1a849d97dba9ce4a362
git.kernel.org/stable/c/d6bedd6acc0bcb1e7e010bc046032e47f08d379f
launchpad.net/bugs/cve/CVE-2024-26813
nvd.nist.gov/vuln/detail/CVE-2024-26813
security-tracker.debian.org/tracker/CVE-2024-26813
ubuntu.com/security/notices/USN-6816-1
ubuntu.com/security/notices/USN-6817-1
ubuntu.com/security/notices/USN-6817-2
ubuntu.com/security/notices/USN-6817-3
ubuntu.com/security/notices/USN-6878-1
ubuntu.com/security/notices/USN-6896-1
ubuntu.com/security/notices/USN-6896-2
ubuntu.com/security/notices/USN-6896-3
ubuntu.com/security/notices/USN-6896-4
ubuntu.com/security/notices/USN-6896-5
ubuntu.com/security/notices/USN-6898-1
ubuntu.com/security/notices/USN-6898-2
ubuntu.com/security/notices/USN-6898-3
ubuntu.com/security/notices/USN-6898-4
ubuntu.com/security/notices/USN-6917-1
ubuntu.com/security/notices/USN-6919-1
www.cve.org/CVERecord?id=CVE-2024-26813