9p/xen: fix refcount leak in p9_xen_response() on wrong tag
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f05c30653f6b25766f2e4c18bf015be9b873e18c, Kernel 4.20, Kernel 1767c02fb555a093b6584fc43f11f0ec1aa32d94 and 5 more.
In the Linux kernel, the following vulnerability has been resolved: 9p/xen: fix refcount leak in p9_xen_response() on wrong tag p9_xen_response() looks up the request for an incoming reply with p9_tag_lookup(), which takes a reference on the returned p9_req_t. When the tag does not resolve to a request in REQ_STATUS_SENT, the function warns and continues the loop without dropping that reference, permanently leaking the p9_req_t and its msize buffers. The reply header, including the tag, is supplied by the backend, so a malicious or buggy 9P backend can leak kernel memory on every crafted response. Drop the reference before continuing.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=728356dedeff8ef999cb436c71333ef4ac51a81c <f05c30653f6b25766f2e4c18bf015be9b873e18c, >=4.19.57 <4.20, >=728356dedeff8ef999cb436c71333ef4ac51a81c <1767c02fb555a093b6584fc43f11f0ec1aa32d94, >=728356dedeff8ef999cb436c71333ef4ac51a81c <3480ece36ed728c2ddda004bc3e2b99bb364765b, >=728356dedeff8ef999cb436c71333ef4ac51a81c <4d183e6f153245aca2534e372152583b868dd925, =3665a4d9dca1bd06bc34afb72e637fe01b2776ee, =4.20 | f05c30653f6b25766f2e4c18bf015be9b873e18c, 4.20, 1767c02fb555a093b6584fc43f11f0ec1aa32d94, 3480ece36ed728c2ddda004bc3e2b99bb364765b, 4d183e6f153245aca2534e372152583b868dd925 |
| linux-kernel: Kernel | >=4.20.0 <6.12.118, >=6.13.0 <6.18.64, >=6.19.0 <7.3.5, >=4.19.57 <4.20 | 6.12.118, 6.18.64, 7.3.5, 4.20 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket