https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Tue, 29 Sep 2026 05:28:37 +0000 https://vulnerability.circl.lu/vuln/cve-2026-72282 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers</p> <p>kvm_io_bus_get_dev() returns a device that is only matched by the address, and nothing else. This can cause a lifetime issue if the matched device is not the expected type, as by the time the caller can introspect the object, it might be gone (the srcu lock having been dropped).</p> <p>Given that there is only a single user of this helper, the simplest option is to move the locking responsibility to the caller, which can keep the srcu lock held for as long as it wants.</p> <p>Note that this aligns with other kvm_io_bus*() helpers, which already require the srcu lock to be held by the callers.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: Move kvm_io_bus_get_dev() locking responsibilities to callers</p> <p>kvm_io_bus_get_dev() returns a device that is only matched by the address, and nothing else. This can cause a lifetime issue if the matched device is not the expected type, as by the time the caller can introspect the object, it might be gone (the srcu lock having been dropped).</p> <p>Given that there is only a single user of this helper, the simplest option is to move the locking responsibility to the caller, which can keep the srcu lock held for as long as it wants.</p> <p>Note that this aligns with other kvm_io_bus*() helpers, which already require the srcu lock to be held by the callers.</p> https://vulnerability.circl.lu/vuln/cve-2026-72282