Drivers: vmbus: Check for channel allocation before looking up relids
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 176c6b4889195fbe7016d9401175b48c5c9edf68, Kernel 1eb65c8687316c65140b48fad27133d583178e15, Kernel 8c3f0ae5435fd20bb1e3a8308488aa6ac33151ee and 2 more.
In the Linux kernel, the following vulnerability has been resolved: Drivers: vmbus: Check for channel allocation before looking up relids relid2channel() assumes vmbus channel array to be allocated when called. However, in cases such as kdump/kexec, not all relids will be reset by the host. When the second kernel boots and if the guest receives a vmbus interrupt during vmbus driver initialization before vmbus_connect() is called, before it finishes, or if it fails, the vmbus interrupt service routine is called which in turn calls relid2channel() and can cause a null pointer dereference. Print a warning and error out in relid2channel() for a channel id that's invalid in the second kernel.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =5.8, >=8b6a877c060ed6b86878fe66c7c6493a6054cf23 <176c6b4889195fbe7016d9401175b48c5c9edf68, >=8b6a877c060ed6b86878fe66c7c6493a6054cf23 <1eb65c8687316c65140b48fad27133d583178e15, >=8b6a877c060ed6b86878fe66c7c6493a6054cf23 <8c3f0ae5435fd20bb1e3a8308488aa6ac33151ee, >=8b6a877c060ed6b86878fe66c7c6493a6054cf23 <a5c44f3446a0565139b7d8abc78f58b86c398123, >=8b6a877c060ed6b86878fe66c7c6493a6054cf23 <c373e49fbb87aa177819866ed9194ebc5414dfd6 | 176c6b4889195fbe7016d9401175b48c5c9edf68, 1eb65c8687316c65140b48fad27133d583178e15, 8c3f0ae5435fd20bb1e3a8308488aa6ac33151ee, a5c44f3446a0565139b7d8abc78f58b86c398123, c373e49fbb87aa177819866ed9194ebc5414dfd6 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket